Comment 0 for bug 1323804
Revision history for this message
| Andreas Hasenack (ahasenack) wrote Server can't update the client if the client is running inside a container | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I'm still debugging this, but so far what I'm seeing is this:
- landscape-client is running on a container. That container is registered against LDS and working properly.
- on the server, schedule a package upgrade activity that upgrades landscape-client and landscape-common. In my case, 12.04.3 is being upgraded to 13.07.3.
The activity is delivered, and this happens:
- everything but package-changer is stopped
- package-changer remains running, but alone, and nothing works.
- landscape-client 12.04.3 is in state rc
- landscape-common is at 13.07.3 and in state ii:
rc landscape-client 12.04.3-0ubuntu1 The Landscape administration system client
ii landscape-common 13.07.3-
- activity on the server side remains "in progress"
- the landscape computer (this container) cannot be managed via landscape anymore, since the client isn't running properly
Attached debug logs from everything.