Description of problem: No Greenboot message when logging into a Fedora IoT machine Version-Release number of selected component (if applicable): Fedora-IoT 33 RC 20200521.0 IoT disk image, aarch64 on a pi3 How reproducible: Every time Steps to Reproduce: 1. Log in using SSH Actual results: No Greenboot message Expected results: A Greenboot status message, preferably "Boot Status is GREEN - Health Check SUCCESS" as described in the test case[0]. Additional info: The following IoT raw-xz image was used: https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-33-20200521.0/compose/IoT/aarch64/images/Fedora-IoT-33-20200521.0.aarch64.raw.xz 0 - https://fedoraproject.org/wiki/User:Pwhalen/QA/IoT_Tests/Greenboot
Can you re-test with 0526.0 ? the openQA test for this passed on x86_64: https://openqa.stg.fedoraproject.org/tests/865007#step/iot_greenboot/5
Just tested again using an aarch 64 image[0]. Still not seeing any Greenboot message after signing in with ssh. Digging into it a bit more, Greenboot does seem to be working, the "Boot Status is GREEN - Health Check SUCCESS" message does appear when I check 'systemctl status greenboot'. Perhaps it has something to do with the image as written by arm-image-installer? I did 'sudo arm-image-installer --image ~/Desktop/Fedora-IoT-33-20200526.0.aarch64.raw.xz --target=rpi3 --media=/dev/sdb --addkey=/home/nielsenb/.ssh/pi/id_ed25519.pub' 0 - https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-33-20200526.0/compose/IoT/aarch64/images/Fedora-IoT-33-20200526.0.aarch64.raw.xz (In reply to Adam Williamson from comment #1) > Can you re-test with 0526.0 ? the openQA test for this passed on x86_64: > > https://openqa.stg.fedoraproject.org/tests/865007#step/iot_greenboot/5
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.