I reran the Xenial verification process and found that this proposed package does not change the behavior; that is, with the proposed package, pro services are still enable on first boot. Upon further investigation, I found that the version of cloud-init in xenial is 21.1-19-gbad84ad4-0ubuntu1~16.04.4 which does not contain the logic to drive the pro auto-attach process (which is where this bug exists).
catred@pro-order-bug:~$ apt-cache policy ubuntu-pro-client
ubuntu-pro-client:
Installed: 31.2.3~16.04
Candidate: 31.2.3~16.04
Version table:
*** 31.2.3~16.04 100
100 /var/lib/dpkg/status
31.2.2~16.04 500
500 http://us-central1.gce.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
catred@pro-order-bug:~$ pro status
SERVICE ENTITLED STATUS DESCRIPTION
cc-eal yes disabled Common Criteria EAL2 Provisioning Packages
cis yes disabled Security compliance and audit tools
esm-apps yes enabled Expanded Security Maintenance for Applications
esm-infra yes enabled Expanded Security Maintenance for Infrastructure
livepatch yes warning Current kernel is not supported
NOTICES
The current kernel (4.15.0-1160-gcp, x86_64) is not supported by livepatch.
Supported kernels are listed here: https://ubuntu.com/security/livepatch/docs/kernels
Either switch to a supported kernel or `pro disable livepatch` to dismiss this warning.
For a list of all Ubuntu Pro services, run 'pro status --all'
Enable services with: pro enable <service>
I reran the Xenial verification process and found that this proposed package does not change the behavior; that is, with the proposed package, pro services are still enable on first boot. Upon further investigation, I found that the version of cloud-init in xenial is 21.1-19- gbad84ad4- 0ubuntu1~ 16.04.4 which does not contain the logic to drive the pro auto-attach process (which is where this bug exists).
The details of the testing I did are shown below:
$ gcloud compute instances create pro-order-bug --image testing- ubuntu- 1604-xenial- v20240417 --image-project ubuntu-catred --metadata- from-file= user-data= userdata. yaml --zone us-central1-a
catred@ pro-order- bug:~$ apt-cache policy ubuntu-pro-client dpkg/status us-central1. gce.archive. ubuntu. com/ubuntu xenial-updates/main amd64 Packages pro-order- bug:~$ pro status
ubuntu-pro-client:
Installed: 31.2.3~16.04
Candidate: 31.2.3~16.04
Version table:
*** 31.2.3~16.04 100
100 /var/lib/
31.2.2~16.04 500
500 http://
catred@
SERVICE ENTITLED STATUS DESCRIPTION
cc-eal yes disabled Common Criteria EAL2 Provisioning Packages
cis yes disabled Security compliance and audit tools
esm-apps yes enabled Expanded Security Maintenance for Applications
esm-infra yes enabled Expanded Security Maintenance for Infrastructure
livepatch yes warning Current kernel is not supported
NOTICES /ubuntu. com/security/ livepatch/ docs/kernels
The current kernel (4.15.0-1160-gcp, x86_64) is not supported by livepatch.
Supported kernels are listed here: https:/
Either switch to a supported kernel or `pro disable livepatch` to dismiss this warning.
For a list of all Ubuntu Pro services, run 'pro status --all'
Enable services with: pro enable <service>
Valid until: Fri Dec 31 00:00:00 9999 UTC
Technical support level: essential
catred@
cloud-init:
Installed: 21.1-19-
Candidate: 21.1-19-
Version table:
*** 21.1-19-
510 https:/
100 /var/lib/
21.
500 http://
0.
500 http://