"satnogs-setup Update" sometimes pulls wrong ansible repository
Sometimes, satnogs-setup Update
will start to pull the default satnogs-client-ansible repository again, despite configured to use a different one.
I did run into this issue multiple times in the past, but due to the nature of it not being reproducible by just re-running "satnogs-setup Update" I was not sure about the nature of this problem. Other users reported this issue as well.
aka "This is what I did":
-
Flash Raspberry Pi OS 32-bit Lite (aka raspbian 11/bullseye) (don't forget to enable SSH!)
-
Install SatNOGS via ansible following these steps: raspbian-bullseye-installation.log. You have a (partially configured: API Token & Co is missing) SatNOGS Station now.
-
Generate support report: 2022-08-04-01.json
-
Run "satnogs-setup Apply"
-
(!) Run "satnogs-setup Update"
💥 Boom. It starts pulling from the wrong repository: 2022-08-04-wrong-install-log-1.txt -
Dump the current state of some files: 2022-08-04-log-1.txt
-
Check that indeed "satnogs-setup Show" lists all settings as expected
-
Generate support report: 2022-08-04-02.json
-
Run "satngs-setup Apply" (no-op, since
is-applied
was true already as seen in the last support report) -
(!) Run "satnogs-setup Update"
😕 No boom. This time the correct repository is pulled.