Disable i586 scheduler
Hello, I am running local OBS instance at Leap 15.6, obs-api-2.10.23. Currently, I have three schedulers: armv7l, i586, x86_64. I would like to completely disable i586. To achieve this I do retrieve the server configuration obs --config ~/.obsadmin_osc.rc api /configuration > obs.config edit <schedulers> section accordingly and upload the configuration back. Then I restart everything. However, I see that i586 scheduler is marked dead at /monitor webui page while I expect that the scheduler will be hidden at that page. What do I do wrong?
Hi Matwey, Am 13.12.24 um 09:37 schrieb Matwey Kornilov:
Hello,
I am running local OBS instance at Leap 15.6, obs-api-2.10.23. Currently, I have three schedulers: armv7l, i586, x86_64. I would like to completely disable i586. To achieve this I do retrieve the server configuration
obs --config ~/.obsadmin_osc.rc api /configuration > obs.config
edit <schedulers> section accordingly and upload the configuration back. Then I restart everything.
However, I see that i586 scheduler is marked dead at /monitor webui page while I expect that the scheduler will be hidden at that page. What do I do wrong?
IIRC to get rid of the removed architecture, you need to remove all remains in the workerstatus files. Also IIRC, if this is not done, the obsolete architecture is "autodiscovered" and addded back to configuration and the database(?). This means: * remove the i586 from the configuration like you have done, then stop all obs services and apache * remove everything resembling i586 from /srv/obs/workers/*/ * start everything again * success! (Hopefully). -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
Thanks. I've found that the architecture is indeed added back automatically. I have not succeeded following your advice: removing the files doesn't help. Maybe you know which service is responsible for re-enabling the architecture? If so I could look into the sources and read exact triggers.
Hi Matwey, Am 18.12.24 um 13:29 schrieb Matwey Kornilov:
Thanks. I've found that the architecture is indeed added back automatically. I have not succeeded following your advice: removing the files doesn't help. Maybe you know which service is responsible for re-enabling the architecture? If so I could look into the sources and read exact triggers.
Oh dear, so it's some of the other state files... check for anything "i586" in: /srv/obs/events /srv/obs/info /srv/obs/jobs /srv/obs/run maybe (can't test this, my OBS has too many files in /srv/obs/) just do a "find /srv/obs -name '*i586*'" and remove everything *after* removing it from the config and stopping all services. I did do this already at least twice but never noted down the exact steps necessary. Maybe once you succeed, you could contribute this to the build service admin docs ;-) Good luck! seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
Also check /srv/obs/configuration.xml, and the architectures table in the api_production database. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
participants (3)
-
Andreas Schwab -
Matwey Kornilov -
Stefan Seyfried