Added by okurz about 2 years ago. Updated about 2 years ago.
0%
Description
Not strictly SUSE QE Tools but maintained originally by nsinger so needs to be done here.
nginx currently already shows "502 Bad Gateway" so I can try to upgrade as it's already broken :)
From nsinger: link shortener is back… uwsgi service was not starting (needs to be enabled) but also /var/run/uwsgi needs to be created before starting the service.
I wonder if we should just add the host to the salt controlled infrastructure of OSd as well. Or similar to how we do https://gitlab.suse.de/qa-sle/backup-server-salt maybe.
Setting due date based on mean cycle time of SUSE QE Tools
Fully upgraded to Leap 15.3 and working. I plan to salt it later.
I forgot to mention that upgrading caused a problem due to a missing magic coding comment in schort.py so I created https://github.com/sqozz/schort/pull/8 to fix that.
I have created a salt repo on https://gitlab.suse.de/qa-sle/s-salt.git with initial configuration from what I found in history and the files that likely are necessary.
I installed SUSE certificates with the help of http://ca.suse.de/gettingstarted/#system and have cloned the salt recipes initially with git -C /srv clone https://gitlab.suse.de/qa-sle/s-salt.git salt. Then I tested application of the salt state with salt-call --local -l error state.apply test=True and after that turned out to look good I applied the high state with salt-call --local -l error state.apply. From now on any changes to the salt repo will be automatically applied to the machine. Additionally we could add the machine to monitoring and auto-upgrade likely just by configuring the salt minion to connect to osd, same as we did on storage.qa and backup.qa. Should we do that?