You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we are attached to a trusty machine and we perform a do-release-upgrade operation we expect to be upgraded to xenial while keeping esm-infra, or any other service we have enabled, still enabled. We guarantee that by running the upgrade_lts_contract in the end of do-release-upgrade. This is script is run by adding the following configuration at /etc/update-manager/release-upgrades.d/
In our current testing infrastructure, we are updating the tusty packaging to the development version of uaclient and then performing the upgrade. This will guarantee that will we have that file in place before running do-release-upgrade. Now, since we will not release the new uaclient version into trusty, we will never have that configuration in place. This means that do-release-upgrade will not run the upgrade_lts_script in the end, which in turn, will make esm-infra to be disabled, as the apt sources will not be correctly updated.
The text was updated successfully, but these errors were encountered:
When we are attached to a trusty machine and we perform a
do-release-upgrade
operation we expect to be upgraded to xenial while keepingesm-infra
, or any other service we have enabled, still enabled. We guarantee that by running the upgrade_lts_contract in the end ofdo-release-upgrade
. This is script is run by adding the following configuration at/etc/update-manager/release-upgrades.d/
In our current testing infrastructure, we are updating the tusty packaging to the development version of uaclient and then performing the upgrade. This will guarantee that will we have that file in place before running
do-release-upgrade
. Now, since we will not release the new uaclient version into trusty, we will never have that configuration in place. This means thatdo-release-upgrade
will not run theupgrade_lts_script
in the end, which in turn, will makeesm-infra
to be disabled, as the apt sources will not be correctly updated.The text was updated successfully, but these errors were encountered: