Comment 7 for bug 1316822
Revision history for this message
| Marc Heckmann (marc-w-heckmann) wrote | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
No, they will not be put back online with reboot. The problem is that the host will come back up with all the VMs in the shutdown state and the problem arises when the operator uses "reboot" to bring the nodes back online.
In Icehouse, if the operator/user uses "start" instead of "reboot", things should be ok. I haven't tested it, but my quick review of the Icehouse code shows that the "start_instance" API call will call "power_on" in the driver. In Icehouse, "power_on" calls "_hard_reboot" which does the right thing in terms of setting up the security groups.
In Grizzly this is not the case.
The "reboot" call does a "_soft_reboot" and even in Icehouse, this does not setup the network security group rules.
In short, the problem is with the "reboot" call. It too should probably teardown and bring the rules back up. Like Andrew, I also question the validity of even allowing the use of "reboot" on a server in the shutdown state but that would be a behavioral change.