© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
It seems to me that there are 3 issues at play here:
a.) kernel: the device driver issue that stefan pointed to above.
clearly a broken network device driver can result in failure to find a network resource
b.) plymouth: many of our boot messages get "eaten".
Robie's paste there shows the issue as to many of mine. I'll also attach a good full console log. Note, that the "error: unexpectedly disconnected from boot status daemon" message occurs in both good and bad paths. In the bad path, we lose console output of the upstart jobs cloud-init and cloud-init-local. The 'cloud-init' job would normally output warnings to the console about inability to find the datasource. In some cases we see failed datasource access and still get this, but often we lose it.
c.) networking bringup race
It seems there must be something more to the issue, because 'b' shouldn't be fatal, and 'a' should not occur on kvm. However, as Robbie showed this also occurs on openstack nodes with kvm.