[Bug 1850699] Re: Please remove net-tools from bind9 Depends (replaced by iproute2)
** Changed in: bind9 (Ubuntu) Status: New => Triaged ** Changed in: bind9 (Ubuntu) Importance: Undecided => High ** Changed in: bind9 (Ubuntu) Assignee: (unassigned) => Andreas Hasenack (ahasenack) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1850699 Title: Please remove net-tools from bind9 Depends (replaced by iproute2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1850699/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1850672] Re: "precise esm -> trusty -> trusty new client" upgrade disables ESM
** Description changed: [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-daily:precise p1 lxc exec p1 ubuntu-advantage enable-esm $USER:$PASS - # confirm esm is enabled and working by downloading a package - lxc exec p1 -- apt-get install -d python-jinja2 - lxc exec p1 apt-get clean + # 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 + sudo do-release-upgrade + logout lxc exec p1 -- bash -c "echo deb http://archive.ubuntu.com/ubuntu trusty-proposed main > /etc/apt/sources.list.d/trusty-proposed.list" lxc exec p1 apt-get update lxc exec p1 -- apt-get install -y ubuntu-advantage-tools lxc exec p1 apt-get update + # confirm esm is enabled and shows a positive pinning value lxc exec p1 apt-cache policy|grep esm - # try to download a trusty esm package, it should work - lxc exec p1 -- apt-get install -d python-jinja2 - lxc exec p1 apt-get clean [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-esm-precise.list -> ubuntu-esm-infra-trusty.list do-release-upgrade will have renamed "precise" to "trusty" inside ubuntu-esm-precise.list. If someone is doing the upgrade manually via dist-upgrade, for example, then this person is expected to rename the precise repositories to trusty ones in all of /etc/apt/sources.list* [Other Info] As with the $1832757 SRU, this is being published only on trusty. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1850672 Title: "precise esm -> trusty -> trusty new client" upgrade disables ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1850672/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1850672] Re: "precise esm -> trusty -> trusty new client" upgrade disables ESM
** Description changed: [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-daily:precise p1 - lxc exec p1 ubuntu-advantage enable-esm $USER:$PASS + lxc exec p1 ubuntu-advantage enable-esm $USER:$PASS + # confirm esm is enabled and working by downloading a package + lxc exec p1 -- apt-get install -d python-jinja2 + lxc exec p1 apt-get clean lxc exec p1 do-release-upgrade lxc exec p1 -- bash -c "echo deb http://archive.ubuntu.com/ubuntu trusty-proposed main > /etc/apt/sources.list.d/trusty-proposed.list" lxc exec p1 apt-get update lxc exec p1 -- apt-get install -y ubuntu-advantage-tools lxc exec p1 apt-get update lxc exec p1 apt-cache policy|grep esm # try to download a trusty esm package, it should work lxc exec p1 -- apt-get install -d python-jinja2 - + lxc exec p1 apt-get clean [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-esm-precise.list -> ubuntu-esm-infra-trusty.list do-release-upgrade will have renamed "precise" to "trusty" inside ubuntu-esm-precise.list. If someone is doing the upgrade manually via dist-upgrade, for example, then this person is expected to rename the precise repositories to trusty ones in all of /etc/apt/sources.list* [Other Info] As with the $1832757 SRU, this is being published only on trusty. ** Description changed: [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-daily:precise p1 - lxc exec p1 ubuntu-advantage enable-esm $USER:$PASS + lxc exec p1 ubuntu-advantage enable-esm $USER:$PASS # confirm esm is enabled and working by downloading a package lxc exec p1 -- apt-get install -d python-jinja2 lxc exec p1 apt-get clean - lxc exec p1 do-release-upgrade + # 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://archive.ubuntu.com/ubuntu trusty-proposed main > /etc/apt/sources.list.d/trusty-proposed.list" lxc exec p1 apt-get update lxc exec p1 -- apt-get install -y ubuntu-advantage-tools lxc exec p1 apt-get update lxc exec p1 apt-cache policy|grep esm # try to download a trusty esm package, it should work lxc exec p1 -- apt-get install -d python-jinja2 lxc exec p1 apt-get clean [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-esm-precise.list -> ubuntu-esm-infra-trusty.list do-release-upgrade will have renamed "precise" to "trusty" inside ubuntu-esm-precise.list. If someone is doing the upgrade manually via dist-upgrade, for example, then this person is expected to rename the precise repositories to trusty ones in all of /etc/apt/sources.list* [Other Info] As with the $1832757 SRU, this is being published only on trusty. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1850672 Title: "precise esm -> trusty -> trusty new client" upgrade disables ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1850672/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1850672] Re: "precise esm -> trusty -> trusty new client" upgrade disables ESM
** Description changed: [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] - * detailed instructions how to reproduce the bug + lxc launch ubuntu-daily:precise p1 + lxc exec p1 ubuntu-advantage enable-esm $USER:$PASS + lxc exec p1 do-release-upgrade + lxc exec p1 -- bash -c "echo deb http://archive.ubuntu.com/ubuntu trusty-proposed main > /etc/apt/sources.list.d/trusty-proposed.list" + lxc exec p1 apt-get update + lxc exec p1 -- apt-get install -y ubuntu-advantage-tools + lxc exec p1 apt-get update + lxc exec p1 apt-cache policy|grep esm + # try to download a trusty esm package, it should work + lxc exec p1 -- apt-get install -d python-jinja2 - * these should allow someone who is not familiar with the affected - package to reproduce the bug and verify that the updated package fixes - the problem. [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: - * discussion of how regressions are most likely to manifest as a result - of this change. + ubuntu-esm-precise.list -> ubuntu-esm-infra-trusty.list - * It is assumed that any SRU candidate patch is well-tested before - upload and has a low overall risk of regression, but it's important - to make the effort to think about what ''could'' happen in the - event of a regression. - - * This both shows the SRU team that the risks have been considered, - and provides guidance to testers in regression-testing the SRU. + do-release-upgrade will have renamed "precise" to "trusty" inside + ubuntu-esm-precise.list. If someone is doing the upgrade manually via + dist-upgrade, for example, then this person is expected to rename the + precise repositories to trusty ones in all of /etc/apt/sources.list* [Other Info] - - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance + As with the $1832757 SRU, this is being published only on trusty. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1850672 Title: "precise esm -> trusty -> trusty new client" upgrade disables ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1850672/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1850672] Re: "precise esm -> trusty -> trusty new client" upgrade disables ESM
** Description changed: + [Impact] + + * An explanation of the effects of the bug on users and + + * justification for backporting the fix to the stable release. + + * In addition, it is helpful, but not required, to include an +explanation of how the upload fixes this bug. + + [Test Case] + + * detailed instructions how to reproduce the bug + + * these should allow someone who is not familiar with the affected +package to reproduce the bug and verify that the updated package fixes +the problem. + + [Regression Potential] + + * discussion of how regressions are most likely to manifest as a result + of this change. + + * It is assumed that any SRU candidate patch is well-tested before +upload and has a low overall risk of regression, but it's important +to make the effort to think about what ''could'' happen in the +event of a regression. + + * This both shows the SRU team that the risks have been considered, +and provides guidance to testers in regression-testing the SRU. + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + 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. Upstream bug: https://github.com/CanonicalLtd/ubuntu-advantage- client/issues/899 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. ** Description changed: [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. - * An explanation of the effects of the bug on users and - - * justification for backporting the fix to the stable release. - - * In addition, it is helpful, but not required, to include an -explanation of how the upload fixes this bug. - - [Test Case] - - * detailed instructions how to reproduce the bug - - * these should allow someone who is not familiar with the affected -package to reproduce the bug and verify that the updated package fixes -the problem. - - [Regression Potential] - - * discussion of how regressions are most likely to manifest as a result - of this change. - - * It is assumed that any SRU candidate patch is well-tested before -upload and has a low overall risk of regression, but it's important -to make the effort to think about what ''could'' happen in the -event of a regression. - - * This both shows the SRU team that the risks have been considered, -and provides guidance to testers in regression-testing the SRU. - - [Other Info] - - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance - - 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. - - Upstream bug: https://github.com/CanonicalLtd/ubuntu-advantage- - client/issues/899 + 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] + + * detailed instructions how to reproduce the bug + + * these should allow someone who is not familiar with the affected + package to reproduce the bug and verify that the updated package fixes + the problem. + + [Regression Potential] + + * discussion of how regressions are most likely to manifest as a result + of this change. + + * It is assumed that any SRU candidate patch is well-tested before + upload and has a low overall risk of regression, but it's important + to make the effort to think about what ''could'' happen in the + event of a regression. + + * This both shows the SRU team that the risks have been considered, + and provides guidance to testers in regression-testing the SRU. + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance -- You received this bug notification because you are a member of Ubuntu Server,
[Bug 1850672] Re: "precise esm -> trusty -> trusty new client" upgrade disables ESM
** Also affects: ubuntu-advantage-tools (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: ubuntu-advantage-tools (Ubuntu Trusty) Importance: Undecided => High ** Changed in: ubuntu-advantage-tools (Ubuntu Trusty) Status: New => In Progress ** Changed in: ubuntu-advantage-tools (Ubuntu Trusty) Assignee: (unassigned) => Andreas Hasenack (ahasenack) ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: In Progress => Triaged ** Changed in: ubuntu-advantage-tools (Ubuntu) Importance: High => Low ** Changed in: ubuntu-advantage-tools (Ubuntu) Assignee: Andreas Hasenack (ahasenack) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1850672 Title: "precise esm -> trusty -> trusty new client" upgrade disables ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1850672/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1850672] [NEW] "precise esm -> trusty -> trusty new client" upgrade disables ESM
Public bug reported: 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. Upstream bug: https://github.com/CanonicalLtd/ubuntu-advantage- client/issues/899 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. ** Affects: ubuntu-advantage-script Importance: Unknown Status: Unknown ** Affects: ubuntu-advantage-tools (Ubuntu) Importance: High Assignee: Andreas Hasenack (ahasenack) Status: In Progress ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: New => In Progress ** Bug watch added: github.com/CanonicalLtd/ubuntu-advantage-client/issues #899 https://github.com/CanonicalLtd/ubuntu-advantage-client/issues/899 ** Also affects: ubuntu-advantage-script via https://github.com/CanonicalLtd/ubuntu-advantage-client/issues/899 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1850672 Title: "precise esm -> trusty -> trusty new client" upgrade disables ESM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1850672/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1832757] Re: Update ubuntu-advantage-client
An 19.6~ubuntu14.04.3 upload with the fix will be done shortly. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832757 Title: Update ubuntu-advantage-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1832757/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1832757] Re: Update ubuntu-advantage-client
Test (5a) failed. The scenario is an upgrade from precise with esm enabled to trusty, and then to trusty-proposed. What happened is that after installing the trusty proposed package in this sequence, ESM became disabled. Upstream bug: https://github.com/CanonicalLtd/ubuntu-advantage- client/issues/899 ** Bug watch added: github.com/CanonicalLtd/ubuntu-advantage-client/issues #899 https://github.com/CanonicalLtd/ubuntu-advantage-client/issues/899 ** Tags removed: verification-needed-trusty ** Tags added: verification-failed-trusty -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to ubuntu-advantage-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832757 Title: Update ubuntu-advantage-client To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1832757/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
