[SRU] Rename ua status call on apt_check script
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-notifier (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Kinetic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
There is an update on how we will output ua commands on the messages delivered by update-notifier.
This will just instruct the user to use that new command instead
[Test Case]
To test this change, use the following script:
-------
#!/bin/bash
set -e
series=$1
token=$2
name=$series-dev
function cleanup {
lxc delete $name --force
}
function on_err {
echo -e "Test Failed"
cleanup
exit 1
}
trap on_err ERR
lxc launch ubuntu-
sleep 10
# Update update-notifier package
lxc exec $name -- sh -c "echo \"deb http://
lxc exec $name -- sudo apt-get update > /dev/null
lxc exec $name -- sudo apt-get install update-
lxc exec $name -- apt-cache policy update-
# Running update-motd for machine without an ua subscription
echo -e "\n* Updated update-notifier message"
echo "######
lxc exec $name -- /usr/lib/
echo -e "######
# Attaching machine to a UA subscription
echo "Attaching to a UA subscription"
lxc exec $name -- ua attach $token > /dev/null
lxc exec $name -- ua status
# Running update-motd for attached machine
echo -e "\n* Updated update-notifier message with system attached to UA"
echo -e "######
lxc exec $name -- /usr/lib/
echo -e "######
# Installing all esm-infra packages
lxc exec $name -- sudo apt-get upgrade -y > /dev/null
# Disabling esm-infra
lxc exec $name -- sudo pro disable esm-infra > /dev/null
echo "* Updated update-notifier message with esm-infra disabled"
echo "######
lxc exec $name -- /usr/lib/
echo -e "######
cleanup
-------
Notice that you need a UA token to run this script.
Additionally, most messages will appear on the xenial machine due to it being ESM already
[Regression Potential]
We are just providing message changes, so the regression potential is really low. User might notice the changes, but they are not that different from the original ones.
Like in bug 1980368, translatable strings are affected, but we accept them for the same reason as we did in that bug.
I merged https:/ /code.launchpad .net/~lamoura/ update- notifier/ +git/update- notifier/ +merge/ 430596 into update-notifier upstream, added a changelog, but did not upload to kinetic due to the beta freeze.