[opensuse-buildservice] obs-worker - restarting services in chroot env at build time
Hi, we have an private OBS installation here (now seperated in an obs-server and one worker, both running in seperated VMs on a vSphere Server). Some of our RPMs restart services like apache or mysql in the %post directive. The problem here is that the obs-worker starts the specified services in its chroot environment but doesn't stop them after the build has completed. So all further builds fail, because the services are still running. I would expect that the worker cleans up his build environment inclusive the started services etc. But maybe I´m a bit puzzled with the underlying 'principles'. It would be nice if someone could push me in the right direction or give some best practices for a solution to this scenario. Would be a 'KVM build envorinment' be a appropriate solution for this (like build.opensuse.org does it? - As long as I interpreted the build logs correctly...) ? But I think this is probably not possible, because the appliances are already running as VMs with no HW virtualization available. Greetings Florian -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Freitag, 13. Juli 2012, 12:33:14 schrieb Florian Kabus:
Hi,
we have an private OBS installation here (now seperated in an obs-server and one worker, both running in seperated VMs on a vSphere Server).
Some of our RPMs restart services like apache or mysql in the %post directive. The problem here is that the obs-worker starts the specified services in its chroot environment but doesn't stop them after the build has completed.
At least the opensuse and SLE builds do deinstall packages at the end of the build. If that happens and it is still running there is a packaging bug in first place. Or broken base system.
So all further builds fail, because the services are still running. I would expect that the worker cleans up his build environment inclusive the started services etc.
But maybe I´m a bit puzzled with the underlying 'principles'. It would be nice if someone could push me in the right direction or give some best practices for a solution to this scenario. Would be a 'KVM build envorinment' be a appropriate solution for this
KVM (or XEN) build be a solution for that. chroot are known not to be secure neither 100% clean.
(like build.opensuse.org does it? - As long as I interpreted the build logs correctly...) ? But I think this is probably not possible, because the appliances are already running as VMs with no HW virtualization available.
yes, can be a problem. However, there is some newer hardware supporting VM inside VM. I haven't played with that so.
Greetings Florian
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Thank you for your quick response. Your help was very much appreciated and clarified some things. On 13.07.2012 13:18, Adrian Schröter wrote:
At least the opensuse and SLE builds do deinstall packages at the end of the build. If that happens and it is still running there is a packaging bug in first place. Or broken base system.
We have some corner cases, where we only want to restart some other services and don't want them to be stopped at deinstallation of the package. But we can control this via Specfile as a workaround ...
KVM (or XEN) build be a solution for that. chroot are known not to be secure neither 100% clean.
Alright, so I would everyone recommend to configure a clean KVM build environment (like build.opensuse.org) in large scale OBS installations.
participants (2)
-
Adrian Schröter -
Florian Kabus