Re: F34 Cloud Amazon AMIs unbootable after updates

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



What appears to be our nightly AMI build for F34 with updates
(125523088429/Fedora-Cloud-Base-34-20211006.0.x86_64-hvm-us-east-1-gp2-0)
won't even start once (no updating required; it's immediately broken).
The attachment won't go through on this list, but I
captured the last lines from the system log on first boot. It looks
like more lines like what was in the screenshot I previously shared.

On Thu, Oct 7, 2021 at 12:46 AM Christopher <ctubbsii@xxxxxxxxxxxxxxxxx> wrote:
>
> Running on EC2, it's kinda hard to get good information from a system
> that won't boot. The machine won't boot to the point of being able to
> capture the system log, and the screenshot of the instance doesn't
> appear to be super helpful: https://imgur.com/a/4PWcRSg
>
> On Wed, Oct 6, 2021 at 4:42 PM Joe Doss <joe@xxxxxxxxxxxxxx> wrote:
> >
> > On 10/6/21 3:18 PM, Christopher wrote:
> > > Hi,
> > >
> > > Has anybody else noticed that the Amazon Public Cloud images for F34
> > > (https://alt.fedoraproject.org/cloud/) no longer boot after the latest
> > > updates?
> > >
> > > I had an instance that I've been keeping up-to-date with dnf system
> > > upgrades and is now on F34, which is now unbootable after recent
> > > updates within the last week. So I tried to create a new instance
> > > using a newer base image at https://alt.fedoraproject.org/cloud/, and
> > > that one is also now unbootable after doing a routine dnf update.
> > >
> > > Has anybody else seen this?
> > >
> > > Does anybody know which package update caused it? (I saw some
> > > grub-related updates, but not sure if they are to blame)
> > >
> > > Does anybody know how to fix a currently broken instance and can share
> > > their solution?
> >
> > Is there anything on the console log when you reboot it after the
> > updates? If you can share the log that would be helpful.
> >
> > Joe
> >
> >
> >
> >
> > --
> > Joe Doss
> > joe@xxxxxxxxxxxxxx
> > _______________________________________________
> > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
> > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
> > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
> > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux