"precise esm -> trusty -> trusty new client" upgrade disables ESM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-advantage-script |
Fix Released
|
Unknown
|
|||
ubuntu-advantage-tools (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Trusty |
Fix Released
|
High
|
Andreas Hasenack |
Bug Description
[Impact]
When enabling ESM on precise, then upgrading that to current trusty, and from there to the proposed new trusty client (see #1832757), ESM gets disabled.
This was found when executing test case (5) in the original SRU bug #1832757.
The reason is that d/postinst, when dealing with this upgrade path, was conditioning a file rename on the package upgrade coming from version 1, which is the precise one. The fix is to drop that conditional, since the filename we intend to rename is the precise one (it has "precise" in its name) and there is no need to check for the version.
[Test Case]
lxc launch ubuntu-
lxc exec p1 ubuntu-advantage enable-esm $USER:$PASS
# confirm esm is enabled and shows a positive pinning value
lxc exec p1 apt-cache policy|grep esm
# ssh into p1 and call do-release-upgrade (doesn't work via lxc exec)
ssh p1
sudo do-release-upgrade
logout
lxc exec p1 -- bash -c "echo deb http://
lxc exec p1 apt-get update
lxc exec p1 -- apt-get install -y ubuntu-
lxc exec p1 apt-get update
# confirm esm is enabled and shows a positive pinning value
lxc exec p1 apt-cache policy|grep esm
[Regression Potential]
Before we were pinning this upgrade path on having come from the exact precise package version, which is "1". Now we are dropping that requirement, and only checking if the precise esm sources.list file exists, then we rename it to the trusty name:
ubuntu-
do-release-upgrade will have renamed "precise" to "trusty" inside ubuntu-
[Other Info]
As with the $1832757 SRU, this is being published only on trusty.
Changed in ubuntu-advantage-tools (Ubuntu): | |
status: | New → In Progress |
Changed in ubuntu-advantage-tools (Ubuntu Trusty): | |
importance: | Undecided → High |
status: | New → In Progress |
assignee: | nobody → Andreas Hasenack (ahasenack) |
Changed in ubuntu-advantage-tools (Ubuntu): | |
status: | In Progress → Triaged |
importance: | High → Low |
assignee: | Andreas Hasenack (ahasenack) → nobody |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in ubuntu-advantage-script: | |
status: | Unknown → Fix Released |
Changed in ubuntu-advantage-tools (Ubuntu): | |
status: | Triaged → Fix Released |
Hello Andreas, or anyone else affected,
Accepted ubuntu- advantage- tools into trusty-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ ubuntu- advantage- tools/19. 6~ubuntu14. 04.3 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification- needed- trusty to verification- done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed- trusty. In either case, without details of your testing we will not be able to proceed.
Further information regarding the verification process can be found at https:/ /wiki.ubuntu. com/QATeam/ PerformingSRUVe rification . Thank you in advance for helping!
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.