[opensuse-buildservice] Getting rid of i586 on an updated installation
Hi all, I have an OBS installation 2.7.2 which got installed as 2.3(?) and updated over the years. I'm building SLES11-SP{1,2,3,4}, SLES12{-SP1,-SP2}, CentOS-7 against local SMT / mrepo mirrors. It is connected to openSUSE.org OBS via OBS interconnect. Some projects are also building against openSUSE.org:CentOS:CentOS-6/standard My "problem" now is: I cannot get rid of the unneeded i586 architecture. No matter what I do with the web frontend or "osc api -e /configuration", it keeps coming back. Also stopping everyhting, editing configuration.xml and then restarting the services does not get rid of it reliably. Does it hide somewhere in the database? How to get rid of it? The problem with it is, that it is cluttering web interfaces (the statistics on the status monitor page are always for i586 default...) and that just adding a repository to a project actually adds the repo as x86_64 and i586. My playground obs instance at home, just building for Leap42.1 to prove bugs for mls is running without i586 just fine, so I know it must be possible. Thanks for any hints, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mittwoch, 14. Dezember 2016, 14:32:08 CET wrote Stefan Seyfried:
Hi all,
I have an OBS installation 2.7.2 which got installed as 2.3(?) and updated over the years. I'm building SLES11-SP{1,2,3,4}, SLES12{-SP1,-SP2}, CentOS-7 against local SMT / mrepo mirrors. It is connected to openSUSE.org OBS via OBS interconnect. Some projects are also building against openSUSE.org:CentOS:CentOS-6/standard
My "problem" now is: I cannot get rid of the unneeded i586 architecture. No matter what I do with the web frontend or "osc api -e /configuration", it keeps coming back. Also stopping everyhting, editing configuration.xml and then restarting the services does not get rid of it reliably.
Does it hide somewhere in the database?
Architecture table, "available" row.
How to get rid of it?
Is it away directly after editing it?
The problem with it is, that it is cluttering web interfaces (the statistics on the status monitor page are always for i586 default...) and that just adding a repository to a project actually adds the repo as x86_64 and i586.
My playground obs instance at home, just building for Leap42.1 to prove bugs for mls is running without i586 just fine, so I know it must be possible.
Thanks for any hints,
seife
-- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 15.12.2016 14:10, Adrian Schröter wrote:
On Mittwoch, 14. Dezember 2016, 14:32:08 CET wrote Stefan Seyfried:
Hi all,
I have an OBS installation 2.7.2 which got installed as 2.3(?) and updated over the years. I'm building SLES11-SP{1,2,3,4}, SLES12{-SP1,-SP2}, CentOS-7 against local SMT / mrepo mirrors. It is connected to openSUSE.org OBS via OBS interconnect. Some projects are also building against openSUSE.org:CentOS:CentOS-6/standard
My "problem" now is: I cannot get rid of the unneeded i586 architecture. No matter what I do with the web frontend or "osc api -e /configuration", it keeps coming back. Also stopping everyhting, editing configuration.xml and then restarting the services does not get rid of it reliably.
Does it hide somewhere in the database?
Architecture table, "available" row.
How to get rid of it?
Is it away directly after editing it?
If I do "osc api -e /configuration", remove the i586 scheduler arch and do an "osc api /configuration" directly afterwards, it stays. If I go to the Configuration -> Architectures tab and uncheck "i586", "Update", then "obs_admin --show-scheduler-architectures" shows only x86_64. Now I do "osc api /configuration", "<schedulers><arch>i586..." is there, --show-scheduler-architectures still does only show x86_64. "osc api -e /configuration", remove i586, then --show-scheduler-architectures shows both i586 and x86_64 again. /srv/obs/configuration.xml does only contain <schedulers> <arch>x86_64</arch> </schedulers> But still, somehow i586 always returns from the dead :-) -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi Adrian, all On 20.12.2016 10:09, Stefan Seyfried wrote:
On 15.12.2016 14:10, Adrian Schröter wrote:
On Mittwoch, 14. Dezember 2016, 14:32:08 CET wrote Stefan Seyfried:
Hi all,
I have an OBS installation 2.7.2 which got installed as 2.3(?) and updated over the years. I'm building SLES11-SP{1,2,3,4}, SLES12{-SP1,-SP2}, CentOS-7 against local SMT / mrepo mirrors. It is connected to openSUSE.org OBS via OBS interconnect. Some projects are also building against openSUSE.org:CentOS:CentOS-6/standard
My "problem" now is: I cannot get rid of the unneeded i586 architecture. No matter what I do with the web frontend or "osc api -e /configuration", it keeps coming back. Also stopping everyhting, editing configuration.xml and then restarting the services does not get rid of it reliably.
But still, somehow i586 always returns from the dead :-)
In a desperate attempt to get rid of i586, I decided to simply patch all the places in the code where the architecture is set, to hardcode if arch.name == "i586" arch.available =0 else ... end This succeeded (no matter if i check the i586 box in the /architectures tab or not, it is always unchecked after submitting the page). However, reloading the page a few times always brought the checkmark back after a few seconds. Looking at the logs, I found the delayed jobs thingy to cause this. So I shut down obsapidelayed, disabled i586 and it stayed disabled. Started obsapidelayed and after a few moments, i586 was back enabled. My solution for now was this hacky patch: --- models/worker_status.rb.orig 2016-08-25 14:27:19.000000000 +0000 +++ models/worker_status.rb 2016-12-23 10:17:53.000000000 +0000 @@ -64,7 +64,11 @@ # to the backend config. a=Architecture.find_by_name(arch) if a - a.available=true + if arch == "i586" + a.available = false + else + a.available=true + end a.save end queue = daemon.get('queue') I think it has to do with the monitor page also always showing a red i586 scheduler. Once I get rid of this, wherever it is hiding, this might also alleviate the need for this hack. Have fun, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Just to resolve the confusion: On 23.12.2016 12:31, Stefan Seyfried wrote:
I think it has to do with the monitor page also always showing a red i586 scheduler. Once I get rid of this, wherever it is hiding, this might also alleviate the need for this hack.
I think, this rmdir /srv/obs/jobs/i586/ rm /srv/obs/info/schedulerinfo.i586 rm /srv/obs/run/bs_sched.i586.* rcobsrepserver restart (a few other services also restarted during the investigation :-) Got rid of the "i586 zombie-apocalypse". The red i586 scheduler is gone. I unpatched the code and i586 has not yet reappeared :-) Have fun, seife -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (2)
-
Adrian Schröter -
Stefan Seyfried