[Bug 575096] New: system locks are not handled in chroot
http://bugzilla.novell.com/show_bug.cgi?id=575096 http://bugzilla.novell.com/show_bug.cgi?id=575096#c0 Summary: system locks are not handled in chroot Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers@forge.provo.novell.com ReportedBy: ug@novell.com QAContact: qa@suse.de Found By: Development Blocker: --- I call: zypper --root /tmp/YaST2-09485-IZ7pT1 --gpg-auto-import-keys --non-interactive ar http://taylor/SLES11_x86_64/DVD1/ main-source and I get: System management is locked by the application with pid 9485 (/usr/lib/YaST2/bin/y2base) because there is a yast running in parallel. Since I work with zypper in a chroot environment, the "outside" lock done by yast should not block my chroot zypper call. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=575096 http://bugzilla.novell.com/show_bug.cgi?id=575096#c1 --- Comment #1 from Uwe Gansert <ug@novell.com> 2010-01-29 10:42:39 UTC --- looks like I can help myself with ZYPP_READONLY_HACK=1 zypper --root .... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=575096 http://bugzilla.novell.com/show_bug.cgi?id=575096#c2 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium --- Comment #2 from Ján Kupec <jkupec@novell.com> 2010-01-29 11:45:14 UTC --- I can easily improve this by applying the read-only hack automatically if --root is present. But that's not an ideal solution. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=575096 http://bugzilla.novell.com/show_bug.cgi?id=575096#c3 Michael Andres <ma@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma@novell.com --- Comment #3 from Michael Andres <ma@novell.com> 2010-02-02 14:52:09 UTC --- No. Either --root can be applied to all the zypp components you create (e.g. ZyppFactory), or applications can announce the --root at the very beginning, so zypp is able to create default components with the right paths per default. For Uwe's usecase I added $ZYPP_LOCKFILE_ROOT, so he's able to pass zyppers --root via the environment to libzypp. So we did not need to change zypper now. For the future I'd like to further enhance zypp::misc::defaultLoadSystem to provide easy startup procedures and access to the zypp components. Something similar is already available in the test/tools environment, where we can more or less transparently operate on either a real system or a solver testcase. Would be nice if at the end you can run e.g. 'zypper dup' on a solver testcase. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=575096 https://bugzilla.novell.com/show_bug.cgi?id=575096#c4 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #4 from Michael Andres <ma@suse.com> 2012-03-30 17:09:47 CEST --- With zypper-1.7.1 / libzypp-11.3.1 ZYPP_LOCKFILE_ROOT is no longer needed. Zypper will propagate --root to libzypp, so the lockfile will be created chroot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=575096 https://bugzilla.novell.com/show_bug.cgi?id=575096#c5 Stefan Brüns <stefan.bruens@rwth-aachen.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |stefan.bruens@rwth-aachen.d | |e Component|libzypp |libzypp Version|Factory |Final Resolution|FIXED | Product|openSUSE 11.3 |openSUSE 12.3 --- Comment #5 from Stefan Brüns <stefan.bruens@rwth-aachen.de> 2013-09-15 20:13:09 UTC --- Seems to be regressed on oS 12.3: $> rpm -q libzypp zypper libzypp-12.15.0-1.17.1.x86_64 zypper-1.8.16-1.10.1.x86_64 ZYPP_LOCKFILE_ROOT can be used to workaround. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=575096 https://bugzilla.novell.com/show_bug.cgi?id=575096#c6 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |stefan.bruens@rwth-aachen.d | |e --- Comment #6 from Michael Andres <ma@suse.com> 2013-09-16 14:44:49 CEST --- # zypper ll 2>&1 Locks.cc(read):124 read locks from /etc/zypp/locks # zypper --root /tmp/r ll Locks.cc(read):124 read locks from /tmp/r/etc/zypp/locks This is as expected. What did not work for you? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=575096 https://bugzilla.novell.com/show_bug.cgi?id=575096#c7 Stefan Brüns <stefan.bruens@rwth-aachen.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|stefan.bruens@rwth-aachen.d | |e | --- Comment #7 from Stefan Brüns <stefan.bruens@rwth-aachen.de> 2013-09-16 15:36:31 UTC --- This is not about /etc/zypp/locks, but /var/run/zypp.pid. At least "zypper --root /tmp/r sh" fails. There seem to be some cases when "--root" is not applied correctly. sbruens-linux:~ # strace -efile -o "| grep pid" zypper --root /tmp/r ll open("/tmp/r/var/run/zypp.pid", O_RDWR|O_CREAT|O_APPEND, 0666) = 4 open("/tmp/r/var/run/zypp.pid", O_RDWR) = 5 There are no package locks defined. open("/tmp/r/var/run/zypp.pid", O_RDWR|O_CREAT|O_APPEND, 0666) = 4 open("/tmp/r/var/run/zypp.pid", O_RDWR) = 5 sbruens-linux:~ # strace -efile -o "| grep pid" zypper --root /tmp/r sh open("/var/run/zypp.pid", O_RDWR|O_CREAT|O_APPEND, 0666) = 4 open("/var/run/zypp.pid", O_RDWR) = 5 terminate called after throwing an instance of 'zypp::ZYppFactoryException' what(): System management is locked by the application with pid 13171 (zypper). Close this application before trying again. --- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=13498, si_uid=0} --- Aborted ZYPP_LOCKFILE_ROOT=/tmp/r strace -efile -o "| grep pid" zypper --root /tmp/r sh open("/tmp/r/var/run/zypp.pid", O_RDWR|O_CREAT|O_APPEND, 0666) = 4 open("/tmp/r/var/run/zypp.pid", O_RDWR) = 5 zypper> open("/tmp/r/var/run/zypp.pid", O_RDWR|O_CREAT|O_APPEND, 0666) = 4 open("/tmp/r/var/run/zypp.pid", O_RDWR) = 5 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=575096 https://bugzilla.novell.com/show_bug.cgi?id=575096#c8 --- Comment #8 from Michael Andres <ma@suse.com> 2013-09-16 17:46:23 CEST ---
This is not about /etc/zypp/locks, but /var/run/zypp.pid. Sorry, 'urlaubsreif'.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=575096 https://bugzilla.novell.com/show_bug.cgi?id=575096#c9 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #9 from Michael Andres <ma@suse.com> 2013-09-16 18:39:10 CEST --- 'zypper sh' is treated differently and failed to redirect the lock file location. Fixed in git for zypper-1.8.17. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=575096 https://bugzilla.novell.com/show_bug.cgi?id=575096#c10 --- Comment #10 from Swamp Workflow Management <swamp@suse.de> 2013-11-11 12:04:37 UTC --- openSUSE-RU-2013:1653-1: An update that has 5 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 575096,834376,844373,845619,846565 CVE References: Sources used: openSUSE 12.3 (src): libsolv-0.3.2-2.14.1, libzypp-12.16.1-1.21.2, zypper-1.8.18-1.14.2 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=575096 https://bugzilla.novell.com/show_bug.cgi?id=575096#c11 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:running:58341:moderat | |e --- Comment #11 from Swamp Workflow Management <swamp@suse.de> 2014-07-17 17:11:06 UTC --- An update workflow for this issue was started. This issue was rated as moderate. Please submit fixed packages until 2014-07-31. https://swamp.suse.de/webswamp/wf/58341 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=575096 https://bugzilla.novell.com/show_bug.cgi?id=575096#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:58341:moderat |maint:running:58341:moderat |e |e | |maint:released:sle11-sp3:58 | |493 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=575096 https://bugzilla.novell.com/show_bug.cgi?id=575096#c12 --- Comment #12 from Swamp Workflow Management <swamp@suse.de> 2014-08-14 17:04:26 UTC --- SUSE-YU-2014:1021-1: An update that has 5 YOU fixes can now be installed. Category: YOU (moderate) Bug References: 575096,862471,876297,883411,885254 CVE References: Sources used: SUSE Linux Enterprise Software Development Kit 11 SP3 (src): libsatsolver-0.17.8-0.5.1, libzypp-9.37.8-0.7.10, satsolver-bindings-0.44.5-0.5.148 SUSE Linux Enterprise Server 11 SP3 for VMware (src): libsatsolver-0.17.8-0.5.1, libzypp-9.37.8-0.7.10, satsolver-bindings-0.44.5-0.5.148, zypper-1.6.315-0.7.15 SUSE Linux Enterprise Server 11 SP3 (src): libsatsolver-0.17.8-0.5.1, libzypp-9.37.8-0.7.10, satsolver-bindings-0.44.5-0.5.148, zypper-1.6.315-0.7.15 SUSE Linux Enterprise Desktop 11 SP3 (src): libsatsolver-0.17.8-0.5.1, libzypp-9.37.8-0.7.10, satsolver-bindings-0.44.5-0.5.148, zypper-1.6.315-0.7.15 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=575096 https://bugzilla.novell.com/show_bug.cgi?id=575096#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:running:58341:moderat |maint:released:sle11-sp3:58 |e |493 |maint:released:sle11-sp3:58 | |493 | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com