Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Claim Unowned Devices does not show my newly installed Fedora IoT #139

Open
adelton opened this issue Jan 4, 2024 · 4 comments
Open

Claim Unowned Devices does not show my newly installed Fedora IoT #139

adelton opened this issue Jan 4, 2024 · 4 comments

Comments

@adelton
Copy link

adelton commented Jan 4, 2024

This is a copy of https://pagure.io/fedora-infrastructure/issue/11706.

I have provisioned a new Raspberry Pi with Fedora IoT, https://download.fedoraproject.org/pub/alt/iot/39/IoT/aarch64/images/Fedora-IoT-39.20231103.1-20231103.1.aarch64.raw.xz from https://fedoraproject.org/iot/download. Per https://docs.fedoraproject.org/en-US/iot/ignition/ the device should have registered with Zezere and its MAC address should show up at https://provision.fedoraproject.org/portal/claim/. But it is not there, the page says just

Unowned devices from this IP address:
© 2020 Copyright Information Goes Here

On my DHCP server I see that the device is up and got an IP address, I know its MAC address, and SSH connection to it works (but obviously I cannot log in as I don't have password / SSH key on it yet), there is no restriction on the device accessing Internet, and on console it says

... unit=zezere_ignition ... res=success

so it seems to suggest it has registered.

On the other hand, https://docs.fedoraproject.org/en-US/iot/ignition/ shows that it should have said

Browse to https://provision.fedoraproject.org/ to claim this device ...

on the console and I did not get this message. So I really don't know if the device has registered and Zezere page is broken, or if for some reason the registration failed.

Can you please check if Zezere recently got some systems registered recently and if some users managed to claim their devices recently?

@adelton
Copy link
Author

adelton commented Jan 4, 2024

In the end I've put the SSH key to the device (eMMC) manually to be able to log in. I can see

Jan 04 20:22:54 localhost.localdomain zezere-ignition[1622]: CRITICAL : files: op(2): [failed]   relabeling 1 patterns: exit st
atus 255: Cmd: "setfiles" "-vF0" "-r" "/" "/etc/selinux/targeted/contexts/files/file_contexts" "-f" "-" Stdout: "" Stderr: "set
files:  invalid alt_rootpath: /\n"

so chances are that this critical error caused zezere-ignition to exit, never to get to register to the provision.fedoraproject.org.

Should I report this in bugzilla or is this issue enough for tracking the problem?

@pcdubs
Copy link
Member

pcdubs commented Jan 4, 2024

on the console and I did not get this message. So I really don't know if the device has registered and Zezere page is broken, or if for some reason the registration failed.

We've had reports of Zezere having issues with some network configurations and does not yet support IPv6.

Should I report this in bugzilla or is this issue enough for tracking the problem?

This is fine, thank you.

@adelton
Copy link
Author

adelton commented Jan 4, 2024

The setfiles failure is already reported as #85.

But in my case the registration to provision.fedoraproject.org does not seem to happen.

My network has both IPv4 and IPv6 working (at least judging by other Fedora (non-IoT) machines on the same switch).

@BreiteSeite
Copy link

BreiteSeite commented Apr 3, 2024

We've had reports of Zezere having issues with some network configurations and does not yet support IPv6.

I remember facing this issue with my dual stack setup as well - but that was already ~2-3 years ago.

Are there any pointers what the exact problem is or whats needed to support dual-stack/IPv6? Are contributions welcomed? I might take a look if there are helpful pointers for both questions.

Additionally i would suggest that at least showing a warning if IPv6 on the interface is detected (won't help headless systems but at least people with a display attached (or people that attach a display for debugging)) know whats up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants