action #116794
closed
Bring back grenache.qa.suse.de + grenache-1.qa.suse.de
Added by okurz over 2 years ago.
Updated over 2 years ago.
Description
Motivation¶
After the situation within SUSE Maxtorhof SRV2 was mitigated we can use grenache again.
Acceptance criteria¶
- AC1: grenache-1 is up, fully reachable and is executing openQA jobs
Suggestions¶
- Project changed from 175 to openQA Infrastructure (public)
- Status changed from New to In Progress
- Assignee set to nicksinger
grenache was already running. LPAR was stuck and I had to reboot it with pvmctl lpar power-off --restart --hard -i id=3. I accepted the salt-key of grenache-1 again on OSD and had to reinstall salt-minion on grenache-1 (it was missing there). Afterwards a quick salt 'grenache-1.qa.suse.de' test.ping worked. Currently running a state.highstate to apply all config changes from the past.
- Status changed from In Progress to Feedback
- Assignee changed from nicksinger to rainerkoenig
Had to manually unmask and enable openqa-worker-auto-restart@{21..28}.service, hopefully I didn't overlook something why it was masked in the past.
@rainerkoenig I quickly checked that jobs are capable of running at all with https://openqa.suse.de/tests/9518325. Could you please check if everything works as you expect it?
Looks good to me. Thanks.
- Status changed from Feedback to In Progress
- Assignee changed from rainerkoenig to nicksinger
- Related to action #113701: [tools] Move workers back to grenache added
- Due date set to 2022-10-05
Setting due date based on mean cycle time of SUSE QE Tools
- Status changed from In Progress to Resolved
The machine seems to work perfect again and moving workers back onto it is covered by another ticket so we can close it here :)
Also available in: Atom
PDF