<fifofonix>
uny: thanks, just rolled back using grub and hopefully i'll be able to look at journal to gather more details.
jpn has quit [Ping timeout: 255 seconds]
jpn has joined #fedora-coreos
jcajka has quit [Quit: Leaving]
ravanelli has quit [Remote host closed the connection]
Betal has joined #fedora-coreos
ravanelli has joined #fedora-coreos
ravanelli has quit [Remote host closed the connection]
ravanelli has joined #fedora-coreos
bgilbert has joined #fedora-coreos
jpn has quit [Ping timeout: 260 seconds]
<dustymabe>
fifofonix: ouch.. any more info?
<fifofonix>
not yet. validated that newly provisioned 6.2.8 with same ign template is fine.
<fifofonix>
also, that if I downgrade I can login again, but that If I do another rpm-ostree upgrade that the same thing happens again...
<fifofonix>
I couldn't see anything in the serial console logs (but I'm no expert).
<dustymabe>
what is `6.2.8` if you don't mind me asking?
<dustymabe>
version of ssh?
<fifofonix>
Sorry I mean next 38.20230402.1.0
<dustymabe>
+1
<fifofonix>
I may go dark on this as I'm heading on vacation soon.
<dustymabe>
fifofonix: can you let me know what version you are staring on?
<fifofonix>
37.20230303.1.1
<dustymabe>
ok thanks
<dustymabe>
fifofonix: x86_64 ?
<fifofonix>
Yes
<dustymabe>
can you share any logs from sshd?
<dustymabe>
fifofonix: I just ran a vanilla upgrade test `37.20230303.1.1->38.20230402.1.0` and it passed
ravanelli has quit [Remote host closed the connection]
jpn has joined #fedora-coreos
<fifofonix>
dustymabe: thanks for that, re logs I'm a baby bear here.
jpn has quit [Ping timeout: 268 seconds]
<fifofonix>
dustymabe: i was thinking *maybe* my journal logs post rollback would have shown outcome of f38 upgrade (but as you all know they don't)
<fifofonix>
what is a good mechanism for upgrading, and capturing journals if you can't login?
<fifofonix>
or, maybe it is that the journal version written by f38 is incompatible with f37 journald because I'm getting an unsupported feature warning when i try to view in f37 and that isn't typical.
<jlebon>
dustymabe: i'd get it in 4.14 and built so it's easier for them to test. if this needs to go to 4.13, i'd say confirm first to save on the paperwork if more commits will need to be part of the same backport PR.
<dustymabe>
jlebon: i.e. rerun the bots to update https://github.com/openshift/os/pull/1227 and then bring out my baseball bat to try to get CI to allow it through?