Centos Stream 9 shutdown issue

[TrevorH]

For those affected by this, if you post the info here, nothing will happen as no-one who cares reads this forum. You need to raise a bug to get Red Hat to take any notice and they probably won't care anyway since this is Stream.

[jlehtone]

... they probably won't care anyway since this is Stream.

They should care if it affects where RHEL evolves, but that does not have to show up in Stream, Presto.


Edit:
These fora are, and have always been primarily peer support. "We all" use/have used CentOS and share experiences and observations here.
When CentOS was rebuilt from RHEL sources, there was possibility that the build process had a glitch. Those were "genuine CentOS bugs".
All other bugs are from Red Hat. If you find one, then you report it.

[verbal_666]

This is a problem once again. I have to go back two kernels to be able to shutdown my VM's again. Below is a screenshot of the kernel that works. I get the error below.
Screenshot 2023-09-06 at 1.59.49 AM.png

Same problem to me after last kernel update.
Can't init 0 / shutdown now the system, dracut screen also to me.
With previous kernels all fine.

[leonchik1976]

Same issue with KVM. Downgrading kernel to 5.14.0-354 solves the issue of shutdown

[TrevorH]

Again, if you want this fixed then you need to report it to Red Hat via the links I posted earlier.

Telling the forum does not do any good at all. No-one from RH reads this forum sop you might as well spray paint it on your nearest whitewashed wall for all the good it will do reporting it here.

[thisisqasim]

I have created an issue for it but it got deleted apparently
https://issues.redhat.com/browse/RHEL-3403

[TrevorH]

On bugzilla, all bug entries raised against the 'kernel' component were automatically made private to avoid disclosure of private information in any attached files. I would suspect the same is true of the new JIRA so permission denied is not impossible though I would expect the issue creator to be able to read their own bug.

[verbal_666]

Last kernel update solved the problem

[jlehtone]

Last kernel update solved the problem

Is that kernel-5.14.0-364.el9?

[verbal_666]

Last kernel update solved the problem

Is that kernel-5.14.0-364.el9?

Yes, it is