Project

General

Profile

action #89398

OSD deployment stopped prematurely due to "System management is locked by the application with pid 29165 (zypper)"

Added by okurz 5 months ago.

Status:
New
Priority:
Low
Assignee:
-
Target version:
Start date:
2021-03-03
Due date:
% Done:

0%

Estimated time:

Description

Observation

From https://gitlab.suse.de/openqa/osd-deployment/-/jobs/351668

++ echo '$ ssh $TARGET \ # collapsed multi-line command'
++ ssh openqa.suse.de 'set -x; cd /tmp &&      sudo zypper --no-refresh -n dup --force-resolution --replacefiles &&      sudo salt -C '\''G@roles:worker'\'' cmd.run '\''zypper --no-refresh -n dup --force-resolution --replacefiles'\'' &&      sudo salt -C '\''openqaworker2*'\'' cmd.run '\''rpm -q --changelog os-autoinst'\'' | sed '\''s/^    //'\'' > os-autoinst-after_changelog &&      rpm -q --changelog openQA > after_changelog &&      (echo -e "Hi all,
You can find the details on https://gitlab.suse.de/openqa/osd-deployment/-/jobs/351668
As always, if you encounter problems, please file tickets on https://progress.opensuse.org.
Have fun, your QA tools team
" && echo -e '\''\n\n'\'' &&        diff {before,after}_changelog | sed -n '\''s/^>//p'\'' &&        echo -e '\''\n\nos-autoinst changes:\n'\'' &&        diff os-autoinst-{before,after}_changelog | sed -n '\''s/>//p'\'' )      | mail -r root@openqa.suse.de -s "Update of openqa.suse.de" openqa@suse.de'
$ export MAIL=${MAIL:-"osd-admins@suse.de"}
$ ( # collapsed multi-line command
$ ssh $TARGET \ # collapsed multi-line command
Warning: Permanently added the ECDSA host key for IP address '10.160.0.207' to the list of known hosts.
+ cd /tmp
+ sudo zypper --no-refresh -n dup --force-resolution --replacefiles
System management is locked by the application with pid 29165 (zypper).
Close this application before trying again.

So zypper was running, not sure what triggered that.

Expected result

  • Unless something is really stuck on the machine then deployment should wait and try again

Suggestion

  • Try to find out if the process is still there, check in logs what the PID was for or if zypper was called by another process around the same time or if it's maybe from deployment itself
  • Wait for the other zypper process to stop and retry within the deployment

Workaround

As I checked and found no zypper process on osd at ticket creation time anymore a retrigger of the failed pipeline step should work

Also available in: Atom PDF