Created attachment 1772084 [details] screenshot Description of problem: following this page[1] to create a VM with Fedora-IoT-34-20210410.0.x86_64.qcow2,but as shown in the attached screenshot,"device ID not yet known" is shown,but not mac address. following this page[2],add a ssh pub key,then click "Claim unknown device"but found nothing is shown [1]https://docs.fedoraproject.org/en-US/iot/virtual-machine-setup/ [2]https://docs.fedoraproject.org/en-US/iot/ignition/ Try 6 times,only get mac address shown once Version-Release number of selected component (if applicable): Fedora-IoT-34-20210413.0.x86_64.qcow2 How reproducible: occasionally Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I only get mac address shown(be able to add the ssh pub key) once.Do we have other method to add ssh pubkey?
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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. Thank you for reporting this bug and we are sorry it could not be fixed.