See https://bugzilla.redhat.com/show_bug.cgi?id=1147998
This may be related to the automatic partition resizing, but I'm not sure.
PVM-based booting, as in EC2 (uh, except for HVM in EC2, obviously) is unaffected.
We should probably add "reboots properly in HMV environment; and reboots properly in PVM environment" to our validation tests and release criteria.
2014-09-30 16:09 GMT+02:00 Matthew Miller mattdm@fedoraproject.org:
See https://bugzilla.redhat.com/show_bug.cgi?id=1147998
This may be related to the automatic partition resizing, but I'm not sure.
PVM-based booting, as in EC2 (uh, except for HVM in EC2, obviously) is unaffected.
We should probably add "reboots properly in HMV environment; and reboots properly in PVM environment" to our validation tests and release criteria.
EC2 was untested -I don't have anymore access to a partner account-, If you send me the credentials, I could take care of it for our next test days.
Regards, H.
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Tue, Sep 30, 2014 at 10:09:36AM -0400, Matthew Miller wrote:
See https://bugzilla.redhat.com/show_bug.cgi?id=1147998
This may be related to the automatic partition resizing, but I'm not sure.
PVM-based booting, as in EC2 (uh, except for HVM in EC2, obviously) is unaffected.
We should probably add "reboots properly in HMV environment; and reboots properly in PVM environment" to our validation tests and release criteria.
I noticed something similar to this a while back [1] but I assumed it was either because I was using pre-alpha grade images or it was because I was using virt-install to do the image build process.
Basically what I noticed is that doing the image "build" using the same tree/etc from koji yielded me with a VM that would boot once (so anaconda install and first boot work fine). However, subsequent boots would fail. I would then have to dd the syslinux mbr.bin to vda and everything would work fine.
After looking at [2] I assumed this was a conscious decision we had made to not install the mbr by default (although reading through the comments now shows that you are only affected by this if the disk was not blank prior to build) and for some reason I assumed that it just worked on cloud platforms (although at the time I didn't have an image to test).
Long story to say that I agree it looks like something on boot is affecting the mbr.
Dusty
[1] - https://lists.fedoraproject.org/pipermail/cloud/2014-August/004166.html [2] - https://bugzilla.redhat.com/show_bug.cgi?id=1015931
On Tue, Sep 30, 2014 at 10:37:40AM -0400, Dusty Mabe wrote:
After looking at [2] I assumed this was a conscious decision we had made to not install the mbr by default (although reading through the comments now shows that you are only affected by this if the disk was not blank prior to build) and for some
It may indeed be that the current problem is new because the disk is no longer blank in the same way in the new image production process.
----- Original Message -----
See https://bugzilla.redhat.com/show_bug.cgi?id=1147998
This may be related to the automatic partition resizing, but I'm not sure.
PVM-based booting, as in EC2 (uh, except for HVM in EC2, obviously) is unaffected.
We should probably add "reboots properly in HMV environment; and reboots properly in PVM environment" to our validation tests and release criteria.
Reboot is in Beta criteria, although written for all release blocking desktops. Should be all blocking products and desktops.
"Shutdown, reboot, logout
Shutting down, logging out and rebooting must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops."
https://fedoraproject.org/wiki/Fedora_21_Beta_Release_Criteria
Alpha states shutdown only.
Jaroslav
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Tue, Sep 30, 2014 at 10:47:32AM -0400, Jaroslav Reznik wrote:
Reboot is in Beta criteria, although written for all release blocking desktops. Should be all blocking products and desktops.
"Shutdown, reboot, logout
Shutting down, logging out and rebooting must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops."
https://fedoraproject.org/wiki/Fedora_21_Beta_Release_Criteria
Alpha states shutdown only.
We should probably change this. I think the assumption here is that the reboot command initiates a clean shutdown and reboot, but on failure, eh, you can just hold the power button (or virtual equivalent) and boot whichever other way.
Here, the situation isn't really reboot -- it's any _second_ boot.
On Tue, Sep 30, 2014 at 11:16:20AM -0400, Matthew Miller wrote:
On Tue, Sep 30, 2014 at 10:47:32AM -0400, Jaroslav Reznik wrote:
Reboot is in Beta criteria, although written for all release blocking desktops. Should be all blocking products and desktops.
"Shutdown, reboot, logout
Shutting down, logging out and rebooting must work using standard console commands and the mechanisms offered (if any) by all release-blocking desktops."
https://fedoraproject.org/wiki/Fedora_21_Beta_Release_Criteria
Alpha states shutdown only.
We should probably change this. I think the assumption here is that the reboot command initiates a clean shutdown and reboot, but on failure, eh, you can just hold the power button (or virtual equivalent) and boot whichever other way.
Here, the situation isn't really reboot -- it's any _second_ boot.
-- Matthew Miller mattdm@fedoraproject.org Fedora Project Leader
I'm going to do some work today drafting out cloud specific criteria and noting anything else (non-cloud specific) that could use generalizing. Once I have a draft, I'll send it here as well as the test@ list to get some feedback. The criteria Jaroslav referenced was the one I added to the bug, but we for sure should have a criteria that covers this.
On 09/30/2014 09:09 AM, Matthew Miller wrote:
See https://bugzilla.redhat.com/show_bug.cgi?id=1147998
This may be related to the automatic partition resizing, but I'm not sure.
PVM-based booting, as in EC2 (uh, except for HVM in EC2, obviously) is unaffected.
We should probably add "reboots properly in HMV environment; and reboots properly in PVM environment" to our validation tests and release criteria.
Between this issue and lack of a bash update, should we hold off on the "state of" piece I wrote until we have at least a TC for the beta that solves these issues?
Best,
jzb
On Wed, Oct 01, 2014 at 07:24:28AM -0500, Joe Brockmeier wrote:
We should probably add "reboots properly in HMV environment; and reboots properly in PVM environment" to our validation tests and release criteria.
Between this issue and lack of a bash update, should we hold off on the "state of" piece I wrote until we have at least a TC for the beta that solves these issues?
I'm thinkin' yes. Let's run it with the beta release?
On 10/01/2014 07:29 AM, Matthew Miller wrote:
I'm thinkin' yes. Let's run it with the beta release?
Sounds good to me. Editing ticket.
Best,
jzb
-
Dusty Mabe -
Haïkel -
Jaroslav Reznik -
Joe Brockmeier -
Matthew Miller -
Mike Ruckman