landscape-client is dying when being upgraded by itself via landscape, only package-changer remains running
Bug #927620 reported by
Andreas Hasenack
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Fix Released
|
High
|
Andreas Hasenack |
Bug Description
I used landscape to upgrade landscape-client in 4 machines that were using landscape-client with APT instead of smart.
Out of those 4, 3 had problems in that all landscape client processes except the package-changer died:
root@li36-158:~# ps fxaw|grep landscape
14506 ? Ss 0:12 /usr/bin/python /usr/bin/
root@li36-158:~#
The activity is stuck in the "In progress" state on the server.
The upgrade was from landscape-client r448 to r449.
Attached are the logs (dates and times in UTC) that include the upgrade. Details of the activity:
Created at: Today 12:37 UTC
Delivered at: Today 12:39
Changed in landscape-client: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
package- reporter. log was empty.