I can confirm that as of now it runs fine against
- impish
- impish + UA from proposed
- imposh proposed
The test installs all users of update-motd
It does not list ubuntu-advantage-tools but since they are in the image one would think that it still would be there.
The test intention is:
1. run update-motd while ALL motd scripts installed
2. ensure all are installed
---
To do so for #1 it has the above mentioned dependencies and then runs "update-motd".
This works fine.
---
#2 is checked via "apt-file" to deliver ALL that exist in the archive
And then followed by a check if all those are present on the current system.
The former advantage-tools 26.2 had no motd scripts.
The new 27.0.1 has two:
root@h:~# dpkg -L ubuntu-advantage-tools | grep motd
/etc/update-motd.d
/etc/update-motd.d/88-esm-announce
/etc/update-motd.d/91-contract-ua-esm-status
Those two are correctly reported in the "apt-file" output of impish.
This is how the broken testbed looks like:
ubuntu@autopkgtest:~$ apt-cache policy ubuntu-advantage-tools
ubuntu-advantage-tools:
Installed: 26.2
Candidate: 27.0.1
Version table:
27.0.1 995
500 http://archive.ubuntu.com/ubuntu impish-proposed/main amd64 Packages
*** 26.2 990
990 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status
Options that come to mind
a) change update-motd d/t/control to install ubuntu-advantage-tools which will update it
=> does not work, it is considered already there and not upgraded
What is left is
b) wait until an image is re-spun (not this will also affect all SRUed releases at some point)
c) change update-motd d/t/update-motd to call a full "apt upgrade -y" before the test
(c) does not seems super charming to SRU as test-only fix :-/
I wonder if it would be painful but better to get the images respinned fast as - after all - it is a false positive that will go away.
I can confirm that as of now it runs fine against
- impish
- impish + UA from proposed
- imposh proposed
The test installs all users of update-motd
It does not list ubuntu- advantage- tools but since they are in the image one would think that it still would be there.
The test intention is:
1. run update-motd while ALL motd scripts installed
2. ensure all are installed
---
To do so for #1 it has the above mentioned dependencies and then runs "update-motd".
This works fine.
---
#2 is checked via "apt-file" to deliver ALL that exist in the archive
And then followed by a check if all those are present on the current system.
The former advantage-tools 26.2 had no motd scripts. advantage- tools | grep motd motd.d/ 88-esm- announce motd.d/ 91-contract- ua-esm- status
The new 27.0.1 has two:
root@h:~# dpkg -L ubuntu-
/etc/update-motd.d
/etc/update-
/etc/update-
Those two are correctly reported in the "apt-file" output of impish.
root@h:~# apt-file search /etc/update-motd.d | grep adv advantage- tools: /etc/update- motd.d/ 88-esm- announce advantage- tools: /etc/update- motd.d/ 91-contract- ua-esm- status
ubuntu-
ubuntu-
But, since the test runs on "autopkgtest image + new package install" but NOT "apt upgrade" it isn't really testing with 27.0.1.
Most of us usually run autopkgtest with -U|--apt-upgrade and therefore we couldn't reproduce.
But with the following it does show up in a local test:
$ sudo ~/work/ autopkgtest/ autopkgtest/ runner/ autopkgtest --no-built-binaries --apt-pocket= proposed= src:ubuntu- advantage- tools --shell-fail update-motd_3.7.dsc -- qemu --ram-size=1536 --cpus 2 ~/work/ autopkgtest- impish- amd64.img advantage- tools: /etc/update- motd.d/ 88-esm- announce: /etc/update- motd.d/ 88-esm- announce advantage- tools: /etc/update- motd.d/ 91-contract- ua-esm- status: /etc/update- motd.d/ 91-contract- ua-esm- status
...
ERROR: Untested update-motd snippet: ubuntu-
ERROR: Untested update-motd snippet: ubuntu-
This is how the broken testbed looks like: autopkgtest: ~$ apt-cache policy ubuntu- advantage- tools advantage- tools: archive. ubuntu. com/ubuntu impish- proposed/ main amd64 Packages archive. ubuntu. com/ubuntu impish/main amd64 Packages dpkg/status
ubuntu@
ubuntu-
Installed: 26.2
Candidate: 27.0.1
Version table:
27.0.1 995
500 http://
*** 26.2 990
990 http://
100 /var/lib/
Options that come to mind advantage- tools which will update it
a) change update-motd d/t/control to install ubuntu-
=> does not work, it is considered already there and not upgraded
What is left is
b) wait until an image is re-spun (not this will also affect all SRUed releases at some point)
c) change update-motd d/t/update-motd to call a full "apt upgrade -y" before the test
(c) does not seems super charming to SRU as test-only fix :-/
I wonder if it would be painful but better to get the images respinned fast as - after all - it is a false positive that will go away.