Release upgrades ignores configuration on machine
Bug #794686 reported by
Kevin McDermott
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Invalid
|
Low
|
Unassigned |
Bug Description
Machines that are configured to ignore non-LTS upgrades are still flagged as having release upgrades available.
Changed in landscape: | |
importance: | Undecided → Low |
milestone: | none → backlog |
affects: | landscape → landscape-client |
Changed in landscape-client: | |
milestone: | backlog → none |
visibility: | private → public |
Changed in landscape-client: | |
milestone: | none → backlog |
To post a comment you must log in.
Output of root@iapps:~# cat /etc/update- manager/ release- upgrades
# Default behavior for the release upgrader.
[DEFAULT]
# Default prompting behavior, valid options:
#
# never - Never check for a new release.
# normal - Check to see if a new release is available. If more than one new
# release is found, the release upgrader will attempt to upgrade to
# the release that immediately succeeds the currently-running
# release.
# lts - Check to see if a new LTS release is available. The upgrader
# will attempt to upgrade to the first LTS release available after
# the currently-running one. Note that this option should not be
# used if the currently-running release is not itself an LTS
# release, since in that case the upgrader won't be able to
# determine if a newer release is available.
Prompt=lts
Output of root@iapps:~# cat /etc/issue
Ubuntu 10.04.2 LTS \n \l
the Prompt value should be sent to the server.