| 2014-05-27 19:17:38 |
Andreas Hasenack |
bug |
|
|
added bug |
| 2014-05-27 19:17:38 |
Andreas Hasenack |
attachment added |
|
ps-output.txt https://bugs.launchpad.net/bugs/1323804/+attachment/4120849/+files/ps-output.txt |
|
| 2014-05-27 19:17:51 |
Andreas Hasenack |
attachment added |
|
broker.log https://bugs.launchpad.net/landscape-client/+bug/1323804/+attachment/4120850/+files/broker.log |
|
| 2014-05-27 19:18:03 |
Andreas Hasenack |
attachment added |
|
manager.log https://bugs.launchpad.net/landscape-client/+bug/1323804/+attachment/4120851/+files/manager.log |
|
| 2014-05-27 19:18:15 |
Andreas Hasenack |
attachment added |
|
monitor.log https://bugs.launchpad.net/landscape-client/+bug/1323804/+attachment/4120852/+files/monitor.log |
|
| 2014-05-27 19:18:26 |
Andreas Hasenack |
attachment added |
|
package-changer.log https://bugs.launchpad.net/landscape-client/+bug/1323804/+attachment/4120853/+files/package-changer.log |
|
| 2014-05-27 19:18:44 |
Andreas Hasenack |
attachment added |
|
package-reporter.log https://bugs.launchpad.net/landscape-client/+bug/1323804/+attachment/4120854/+files/package-reporter.log |
|
| 2014-05-27 19:19:49 |
Andreas Hasenack |
attachment added |
|
watchdog.log https://bugs.launchpad.net/landscape-client/+bug/1323804/+attachment/4120856/+files/watchdog.log |
|
| 2014-05-27 22:05:01 |
Andreas Hasenack |
summary |
Server can't update the client if the client is running inside a container |
Server can't update the client |
|
| 2014-05-27 22:05:14 |
Andreas Hasenack |
description |
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-0ubuntu0.12.04 The Landscape administration system client - Common files
- 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. |
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. UPDATE: also happens when running on bare metal.
- 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-0ubuntu0.12.04 The Landscape administration system client - Common files
- 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. |
|
| 2014-05-27 22:05:27 |
Andreas Hasenack |
landscape-client: importance |
Undecided |
High |
|
| 2014-05-27 22:05:38 |
Andreas Hasenack |
tags |
|
kanban |
|
| 2014-05-27 22:07:36 |
🤖 Landscape Builder |
tags |
kanban |
|
|
| 2014-05-28 18:45:29 |
Andreas Hasenack |
description |
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. UPDATE: also happens when running on bare metal.
- 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-0ubuntu0.12.04 The Landscape administration system client - Common files
- 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. |
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. UPDATE: also happens when running on bare metal.
- 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-0ubuntu0.12.04 The Landscape administration system client - Common files
- 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.
More updates:
- the "task" table from the package/database sqlite DB is empty, meaning (I believe) that the client thinks there is nothing else for it to do. Looks like it's losing information during restart. |
|
| 2014-05-28 18:47:50 |
Andreas Hasenack |
description |
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. UPDATE: also happens when running on bare metal.
- 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-0ubuntu0.12.04 The Landscape administration system client - Common files
- 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.
More updates:
- the "task" table from the package/database sqlite DB is empty, meaning (I believe) that the client thinks there is nothing else for it to do. Looks like it's losing information during restart. |
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. UPDATE: also happens when running on bare metal.
- 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-0ubuntu0.12.04 The Landscape administration system client - Common files
- 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.
More updates:
- the "task" table from the package/database sqlite DB is empty, meaning (I believe) that the client thinks there is nothing else for it to do. Looks like it's losing information during restart.
- I'm also seeing cases where the upgrade worked correctly (both packages were upgraded) and the new version is running and exchanging normally, but the activity result is never sent to the server. I can even create new package activities and they work. Just the one that upgraded landscape-c{lient,ommon} remains in progress. |
|
| 2014-05-28 20:29:22 |
Andreas Hasenack |
description |
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. UPDATE: also happens when running on bare metal.
- 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-0ubuntu0.12.04 The Landscape administration system client - Common files
- 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.
More updates:
- the "task" table from the package/database sqlite DB is empty, meaning (I believe) that the client thinks there is nothing else for it to do. Looks like it's losing information during restart.
- I'm also seeing cases where the upgrade worked correctly (both packages were upgraded) and the new version is running and exchanging normally, but the activity result is never sent to the server. I can even create new package activities and they work. Just the one that upgraded landscape-c{lient,ommon} remains in progress. |
I'm still debugging this, but so far what I'm seeing is this:
- landscape-client is running and exchanging 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-0ubuntu0.12.04 The Landscape administration system client - Common files
- 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.
More updates:
- the "task" table from the package/database sqlite DB is empty, meaning (I believe) that the client thinks there is nothing else for it to do. Looks like it's losing information during restart.
- I'm also seeing cases where the upgrade worked correctly (both packages were upgraded) and the new version is running and exchanging normally, but the activity result is never sent to the server. I can even create new package activities and they work. Just the one that upgraded landscape-c{lient,ommon} remains in progress. |
|
| 2014-11-05 23:28:37 |
Dean Henrichsmeyer |
marked as duplicate |
|
1389686 |
|
