Landscape doesn't update all packages?
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I'm running a personal Landscape server (latest from the 16.04 LTS repo) to monitor and deploy updates to a set of Ubuntu servers. The Landscape server itself and all the servers to monitor are all 16.04 LTS LXC containers on top of a Proxmox hypervisor.
I've noticed that Landscape seems to miss packages when it notifies about updates (both regular and security updates). I can for example get a notification about 5 available updates in landscape and apply them.
If I then ssh in to the machine once Landscape reports that all packages have been updated and do a manual apt update It can sometimes still report 5 available updates that gets deployed if I do an apt upgrade.
This happens regularly across all containers. Could this some kind of sync problem or something else?
Has anybody seen anything similar?
landscape
edited Feb 21 at 9:19
galoget
2,1062820
asked Feb 21 at 7:37
Stefan
11
add a comment |Â
up vote
0
down vote
favorite
I'm running a personal Landscape server (latest from the 16.04 LTS repo) to monitor and deploy updates to a set of Ubuntu servers. The Landscape server itself and all the servers to monitor are all 16.04 LTS LXC containers on top of a Proxmox hypervisor.
I've noticed that Landscape seems to miss packages when it notifies about updates (both regular and security updates). I can for example get a notification about 5 available updates in landscape and apply them.
If I then ssh in to the machine once Landscape reports that all packages have been updated and do a manual apt update It can sometimes still report 5 available updates that gets deployed if I do an apt upgrade.
This happens regularly across all containers. Could this some kind of sync problem or something else?
Has anybody seen anything similar?
landscape
edited Feb 21 at 9:19
galoget
2,1062820
asked Feb 21 at 7:37
Stefan
11
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm running a personal Landscape server (latest from the 16.04 LTS repo) to monitor and deploy updates to a set of Ubuntu servers. The Landscape server itself and all the servers to monitor are all 16.04 LTS LXC containers on top of a Proxmox hypervisor.
I've noticed that Landscape seems to miss packages when it notifies about updates (both regular and security updates). I can for example get a notification about 5 available updates in landscape and apply them.
If I then ssh in to the machine once Landscape reports that all packages have been updated and do a manual apt update It can sometimes still report 5 available updates that gets deployed if I do an apt upgrade.
This happens regularly across all containers. Could this some kind of sync problem or something else?
Has anybody seen anything similar?
landscape
edited Feb 21 at 9:19
galoget
2,1062820
asked Feb 21 at 7:37
Stefan
11
I'm running a personal Landscape server (latest from the 16.04 LTS repo) to monitor and deploy updates to a set of Ubuntu servers. The Landscape server itself and all the servers to monitor are all 16.04 LTS LXC containers on top of a Proxmox hypervisor.
I've noticed that Landscape seems to miss packages when it notifies about updates (both regular and security updates). I can for example get a notification about 5 available updates in landscape and apply them.
If I then ssh in to the machine once Landscape reports that all packages have been updated and do a manual apt update It can sometimes still report 5 available updates that gets deployed if I do an apt upgrade.
This happens regularly across all containers. Could this some kind of sync problem or something else?
Has anybody seen anything similar?
landscape
landscape
edited Feb 21 at 9:19
galoget
2,1062820
asked Feb 21 at 7:37
Stefan
11
edited Feb 21 at 9:19
galoget
2,1062820
asked Feb 21 at 7:37
Stefan
11
edited Feb 21 at 9:19
galoget
2,1062820
edited Feb 21 at 9:19
galoget
2,1062820
edited Feb 21 at 9:19
galoget
2,1062820
2,1062820
asked Feb 21 at 7:37
Stefan
11
asked Feb 21 at 7:37
Stefan
11
asked Feb 21 at 7:37
Stefan
11
11
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
This could be normal behavior, let me walk through a couple things.
- Landscape clients only update package caches (
apt-get update) 4 times per day. - Landscape servers only instruct clients to upgrade a named selection of packages. Even if you click the "upgrade all packages" button. It never runs
apt get [dist-]upgradeor similar. A specific set of upgrades are requested of the clients.
Combine these two things together, and there are certainly many timing windows available for you to ssh to a system after an upgrade job is finished and see more things to upgrade.
Next time you see this, hopefully these two bits of information would help explain things. To dig deeper, you would need to collect.
- What packages did landscape claim to upgrade (names and versions)
- What packages were available to upgrade via ssh (names and versions)
- What times did each of these events happen.
Between that, and the publishing history of packages in the ubuntu archives (which is tracked on launchpad), you usually have enough data to explain these kinds of discrepancies.
See for example: Publishing history of gcc-4.8
answered Feb 26 at 2:52
dpb
4,90911545
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
This could be normal behavior, let me walk through a couple things.
- Landscape clients only update package caches (
apt-get update) 4 times per day. - Landscape servers only instruct clients to upgrade a named selection of packages. Even if you click the "upgrade all packages" button. It never runs
apt get [dist-]upgradeor similar. A specific set of upgrades are requested of the clients.
Combine these two things together, and there are certainly many timing windows available for you to ssh to a system after an upgrade job is finished and see more things to upgrade.
Next time you see this, hopefully these two bits of information would help explain things. To dig deeper, you would need to collect.
- What packages did landscape claim to upgrade (names and versions)
- What packages were available to upgrade via ssh (names and versions)
- What times did each of these events happen.
Between that, and the publishing history of packages in the ubuntu archives (which is tracked on launchpad), you usually have enough data to explain these kinds of discrepancies.
See for example: Publishing history of gcc-4.8
answered Feb 26 at 2:52
dpb
4,90911545
add a comment |Â
up vote
0
down vote
This could be normal behavior, let me walk through a couple things.
- Landscape clients only update package caches (
apt-get update) 4 times per day. - Landscape servers only instruct clients to upgrade a named selection of packages. Even if you click the "upgrade all packages" button. It never runs
apt get [dist-]upgradeor similar. A specific set of upgrades are requested of the clients.
Combine these two things together, and there are certainly many timing windows available for you to ssh to a system after an upgrade job is finished and see more things to upgrade.
Next time you see this, hopefully these two bits of information would help explain things. To dig deeper, you would need to collect.
- What packages did landscape claim to upgrade (names and versions)
- What packages were available to upgrade via ssh (names and versions)
- What times did each of these events happen.
Between that, and the publishing history of packages in the ubuntu archives (which is tracked on launchpad), you usually have enough data to explain these kinds of discrepancies.
See for example: Publishing history of gcc-4.8
answered Feb 26 at 2:52
dpb
4,90911545
add a comment |Â
up vote
0
down vote
up vote
0
down vote
This could be normal behavior, let me walk through a couple things.
- Landscape clients only update package caches (
apt-get update) 4 times per day. - Landscape servers only instruct clients to upgrade a named selection of packages. Even if you click the "upgrade all packages" button. It never runs
apt get [dist-]upgradeor similar. A specific set of upgrades are requested of the clients.
Combine these two things together, and there are certainly many timing windows available for you to ssh to a system after an upgrade job is finished and see more things to upgrade.
Next time you see this, hopefully these two bits of information would help explain things. To dig deeper, you would need to collect.
- What packages did landscape claim to upgrade (names and versions)
- What packages were available to upgrade via ssh (names and versions)
- What times did each of these events happen.
Between that, and the publishing history of packages in the ubuntu archives (which is tracked on launchpad), you usually have enough data to explain these kinds of discrepancies.
See for example: Publishing history of gcc-4.8
answered Feb 26 at 2:52
dpb
4,90911545
This could be normal behavior, let me walk through a couple things.
- Landscape clients only update package caches (
apt-get update) 4 times per day. - Landscape servers only instruct clients to upgrade a named selection of packages. Even if you click the "upgrade all packages" button. It never runs
apt get [dist-]upgradeor similar. A specific set of upgrades are requested of the clients.
Combine these two things together, and there are certainly many timing windows available for you to ssh to a system after an upgrade job is finished and see more things to upgrade.
Next time you see this, hopefully these two bits of information would help explain things. To dig deeper, you would need to collect.
- What packages did landscape claim to upgrade (names and versions)
- What packages were available to upgrade via ssh (names and versions)
- What times did each of these events happen.
Between that, and the publishing history of packages in the ubuntu archives (which is tracked on launchpad), you usually have enough data to explain these kinds of discrepancies.
See for example: Publishing history of gcc-4.8
answered Feb 26 at 2:52
dpb
4,90911545
edited Feb 26 at 3:00
answered Feb 26 at 2:52
dpb
4,90911545
answered Feb 26 at 2:52
dpb
4,90911545
answered Feb 26 at 2:52
dpb
4,90911545
4,90911545
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1008280%2flandscape-doesnt-update-all-packages%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password