zezere auto provisioning failing

[millerthegorilla]

fyi
Created a new raspberry pi install, and booted up with monitor and keyboard attached. Went to https://provision.fedoraproject.org/ claimed the device and tried to install my ssh public key, but zezere halts indefinitely with 'cancel run request' on the 'actions' button.
Am going to manually install my ssh key instead

[millerthegorilla]

checking /ostree/deploy/fedora-iot/var/roothome/.ssh/authorized_keys I find the ssh key has been installed.
Why am I required to use the legacy ssl algorithm diffie-hellman? Surely that's unsafe?

[millerthegorilla]

and ssh ing into the machine is prompting for a password, that I don't know.

[millerthegorilla]

so, back to fedora arm server edition. bummer, I was hoping to use containers with the impermeability of ostree.

[millerthegorilla]

my mistake, at least I hope so. I can opt to remove the root during the setup of the card, using fedora-arm-image-installer. I shall try again.

[RobertDeRose]

@millerthegorilla did you ever get this to work? I'm in a similar situation. I claimed the device, pushed the ssh keys, but I am unable to log in via ssh using the ssh keys I pushed. I pulled out the sd card, checked the location you mentioned and did find that the authorized keys were added

[TechnoFred]

I'm having this issue now while attempting to provision Fedora IoT on Raspberry Pi 3 Model B v 1.2. I'm able to boot Fedora IoT, claim it on the website, and then submit the provisioning request. However, the device sits forever without ever being provisioned. My SSH keys are never copied into place and I'm entirely unable to complete the provisioning process for SSH keys using zezere in this manner. While I'm able to see the device and claim it from the website at provision.fedoraproject.org, the device itself seems to be unable to identify its host name or network address and this could be part of the problem. The device indicates the following lines of output after booting:

Browse to https://provision.fedoraproject.org to claim this device (device ID not yet known) and configure SSH keys deployed

localhost login:

audit: type=1130 audit (1686248893.596:102): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=zezere_ignition comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

audit: type=1131...

The previous two audits are repeated over and over again forever, alternating between type 1130 and 1131. Although the provisioning request has been sent from the website, zezere on the device does not seem to be aware of the request. I'm unable to proceed with provisioning with zezere. Please let me know if you have any thoughts. Thank you.

[rdotjain]

Hi @TechnoFred after submitting runrequest, did you try to ssh as root into your device?

[TechnoFred]

yes, but because my keys were not present, it failed

…

On Thu, Jun 29, 2023, 4:06 AM Rupanshi Jain ***@***.***> wrote: Hi @TechnoFred <https://github.com/TechnoFred> after submitting runrequest, did you try to ssh as root into your device? — Reply to this email directly, view it on GitHub <#98 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJK2AMMU4QDFPO2QJOIFPXDXNUZPRANCNFSM4UF2TBUQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>