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.


** Attachment added: "good console log for reference"
   
https://bugs.launchpad.net/ubuntu/+bug/1078926/+attachment/3445276/+files/console-good.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078926

Title:
  raring instance failed to find EC2 datasource

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1078926/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to