Unable to run probert because 'NameError: name '_rtnetlink' is not defined"

[Brett Bergquist]

Environment is Ubuntu 22.04 on a Dell Precision 7780.

Freshly cloned `subiquity` with no changes.
Ran `make install_deps` with no issues.
Tried `PYTHONPATH=probert ./probert/bin/probert --all >mymachine.json`

Note that I touched `snapcraft.yaml` and then did `make probert` to rebuild and now I can run `probert`.

[Dan Bungert (dbungert)]

Interesting. `make install_deps` will do the `gitdeps` step. If you remove the probert checkout and run `make gitdeps` again, you should see _rtnetlink and related things being built.

Would you post the build log that results from a fresh run of `make gitdeps` after removing the probert directory?

[Brett Bergquist (bbergquist0930)]

This morning I deleted the repository and cloned fresh and followed the instructions with no issues.

Yesterday, I did try running `make dryrun` once before I had run `make install_deps`. That off course failed and then I spotted the `make install_deps` step that I missed. `make dryrun` worked but then I tried generating for my machine with `probert`` and had this issue.

Today of course `make install_depds` does not do the same as yesterday as the Python dependencies are already installed (from yesterday).

I spent about a half hour this morning trying to recreate the issue but cannot, so it can be written off as a some sort of user error.

I do have a question however if you will indulge me.

I have a question on launching `subiquity --bootloader=none` but from an Ubuntu Server ISO installer and have no idea where the proper forum would be to discuss this. I am going through the sources of Subiquity and can see what it is doing with the option, but I cannot see how to feed Subiquity that option in the ISO installer environment even if I have to rebuild the ISO.

I am not looking for an answer here, but the proper place to ask the question.

[Dan Bungert (dbungert)]

Hi Brett,

If you think your questions are more developer-ish, which they do kind of look like, you can drop by #curtin on libera.chat. If you think it's more end-userish then #ubuntu-server would be a better spot - I guess it depends where you are going with this.

To the bootloader question, this is an interesting one. Mostly we detect the correct bootloader from the underlying system and the "none" bootloader is part of how ppc64el works. The command line arguments are admittedly a challenge to actually supply to the server process - we mostly use them for internal testing purposes where we have complete control of how the server process is being created.

[Launchpad Janitor (janitor)]

[Expired for subiquity because there has been no activity for 60 days.]