yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #03101
[Bug 1035279] Re: instance hangs at grub prompt after reboot followed by euca-reboot-instances
Marking fix-released in oneiric based on my comment 15, and the fact
that oneiric is now EOL.
** Changed in: Ubuntu Oneiric
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1035279
Title:
instance hangs at grub prompt after reboot followed by euca-reboot-
instances
Status in OpenStack Compute (Nova):
Invalid
Status in Ubuntu:
Fix Released
Status in The Oneiric Ocelot:
Fix Released
Status in The Precise Pangolin:
Fix Released
Bug description:
This issue has been reproduced on Diablo and Essex so far.
When doing "sudo reboot" in an instance shortly followed by "euca-
reboot-instances {instanceID}", once the instaces comes back up, it is
no longer accessible interactively. The kernel is still executing
commands but it stucked in the early boot phases
If only "sudo reboot" from within the instance or "euca-reboot-
instances" is used, network connectivity comes back as expected.
This can be reproduced by using the following steps :
# On the compute node
sudo -s
source creds/novarc
# start instance
instanceid=`euca-run-instances -k novaadmin -t m1.tiny ami-00000006 | grep INSTANCE | awk '{print $2}'`
# wait for instance to start
sleep 60
# reboot the instance with reboot command
ssh -i creds/novaadmin_.key ubuntu@`euca-describe-instances $instanceid | grep INSTANCE | awk '{print $4}'` 'sudo reboot'
# wait 20 seconds
sleep 20
# reboot instance with euca-reboot-instance command
euca-reboot-instances $instanceid
Now euca-describe-instances will show the instance as running, but it
is is unreachable via ssh. The kvm process for the instance is still
visible and running.
Related bugs:
* bug 872244: grub2 recordfail logic prevents headless system from rebooting after power outage
* bug 669481: Timeout should not be -1 if $recordfail
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1035279/+subscriptions