[Canonical-ubuntu-qa] [Bug 2061365] Re: ubuntu_kvm_smoke_test failed with "fips: mandatory checksum data missing - aborting" on X-fips
** Merge proposal linked:
https://code.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/+merge/464307
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2061365
Title:
ubuntu_kvm_smoke_test failed with "fips: mandatory checksum data
missing - aborting" on X-fips
Status in ubuntu-kernel-tests:
In Progress
Bug description:
Issue found with X-fips 4.4.0-1100.107
Test failed with:
fips: mandatory checksum data missing - aborting
Test log:
Running 'sudo -u ubuntu
/home/ubuntu/autotest/client/tests/ubuntu_kvm_smoke_test/the-test amd64'
+ SUT=bjf-test
+ SSH_KEY=/home/ubuntu/.ssh/id_rsa
+ SSH_OPTIONS='-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
-o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
++ awk '{print$2}'
++ lsb_release -c
+ DISTRO=xenial
+ ARCHITECTURE=amd64
+ trap cleanup EXIT
+ '[' -z amd64 ']'
+ kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used
+ '[' 0 '!=' 0 ']'
+ set -e
+ '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
+ ssh-keygen -f /home/ubuntu/.ssh/id_rsa -t rsa -N ''
Generating public/private rsa key pair.
Your identification has been saved in /home/ubuntu/.ssh/id_rsa.
Your public key has been saved in /home/ubuntu/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:gQ81DpOj3eU6BHHn8f8g9en8yXAoFRXU/bJU7H0c6Q0
ubuntu@kt-x-lfps-fps-s2-bc2r4d20-u-kvm-smk-test-amd64
The key's randomart image is:
+---[RSA 2048]+
| +o+ o .==|
| +B +.o Eo=|
| oo+oo. ..o==|
|. .oo.. o+oO|
| .S. .oo+o|
|o ..=o |
| . . o +.|
|. + o|
| o.|
+[SHA256]-+
+ '[' amd64 = ppc64el ']'
++ uvt-simplestreams-libvirt query
++ grep -P 'xenial.*amd64'
++ true
+ image=
+ '[' -z '' ']'
+ uvt-simplestreams-libvirt sync --source
http://cloud-images.ubuntu.com/daily release=xenial arch=amd64
+ uvt-kvm create bjf-test release=xenial arch=amd64
+ uvt-kvm wait bjf-test --insecure --ssh-private-key-file
/home/ubuntu/.ssh/id_rsa
fips: mandatory checksum data missing - aborting
Traceback (most recent call last):
File "/usr/bin/uvt-kvm", line 35, in
uvtool.libvirt.kvm.main_cli_wrapper(sys.argv[1:])
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 717,
in main_cli_wrapper
main(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 712,
in main
args.func(parser, args)
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 645,
in main_wait
main_wait_remote(parser, args)
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 613,
in main_wait_remote
private_key_file=args.ssh_private_key_file,
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 497,
in ssh
ssh_call, preexec_fn=subprocess_setup, close_fds=True, stdin=stdin
File "/usr/lib/python2.7/subprocess.py", line 541, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '[u'ssh', u'-o',
u'UserKnownHostsFile=/dev/null', u'-o', u'StrictHostKeyChecking=no', u'-o',
u'CheckHostIP=no', u'-l', u'ubuntu', u'-i', '/home/ubuntu/.ssh/id_rsa',
u'192.168.122.40', u'env', u'UVTOOL_WAIT_INTERVAL=8.0',
u'UVTOOL_WAIT_TIMEOUT=120.0', u'sh', u'-']' returned non-zero exit status 255
+ cleanup
+ uvt-kvm destroy bjf-test
+ '[' amd64 = ppc64el ']'
This issue does not exist in X-fips 4.4.0-1099.106 from the previous
cycle (s2024.02.05). But it's earlier than the recent fipsdevppa
change was implemented.
This affects just X-fips, other releases appears to have the dependency
configure properly.
We just need to install openssh-client-hmac for this test.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2061365/+subscriptions
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2061107] Re: shiftfs-lxd.sh in ubuntu_overlayfs_smoke_test failed with "Required tool 'zpool' is missing"
Comment from Simon Déziel: 5.21 and later require ZFS 2.1 or later. This means if you are using Ubuntu 20.04, you need the HWE kernel. So this failure is expected. We should either hint it or skip it from the test. ** Changed in: lxd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. https://bugs.launchpad.net/bugs/2061107 Title: shiftfs-lxd.sh in ubuntu_overlayfs_smoke_test failed with "Required tool 'zpool' is missing" Status in ubuntu-kernel-tests: New Status in lxd package in Ubuntu: Invalid Bug description: Issue found in cycle 2024.04.01 with F-gkeop (5.4.0-1091.95), F-oracle (5.4.0-1123.132) Test log Running 'sudo -iu ubuntu /home/ubuntu/autotest/client/tmp/ubuntu_overlayfs_smoke_test/src/overlay-shiftfs-tests/tests/shiftfs-lxd.sh' Error: Required tool 'zpool' is missing Creating c1 Error: Failed loading storage pool "zfs": Storage pool not found Error: Failed to fetch instance "c1" in project "default": Instance not found FAIL Error: Failed to fetch instance "c1" in project "default": Instance not found Error: Failed checking instance exists "local:c1": Failed to fetch instance "c1" in project "default": Instance not found Error: Storage pool not found This is the failing command in shiftfs-lxd.sh: $ sudo lxc storage create zfs zfs size=2GiB Error: Required tool 'zpool' is missing $ snap list lxd Name Version RevTracking Publisher Notes lxd 5.21.1-43998c6 28155 latest/stable canonical✓ - This issue does not exist in 2024.03.04 cycle for these two kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2061107/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:worker-upstream-percentage into autopkgtest-cloud:master
The proposal to merge ~andersson123/autopkgtest-cloud:worker-upstream-percentage into autopkgtest-cloud:master has been updated. Status: Needs review => Work in progress For more details, see: https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/464318 -- Your team Canonical's Ubuntu QA is requested to review the proposed merge of ~andersson123/autopkgtest-cloud:worker-upstream-percentage into autopkgtest-cloud:master. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:worker-upstream-percentage into autopkgtest-cloud:master
Tim Andersson has proposed merging
~andersson123/autopkgtest-cloud:worker-upstream-percentage into
autopkgtest-cloud:master.
Requested reviews:
Canonical's Ubuntu QA (canonical-ubuntu-qa)
For more details, see:
https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/464318
--
Your team Canonical's Ubuntu QA is requested to review the proposed merge of
~andersson123/autopkgtest-cloud:worker-upstream-percentage into
autopkgtest-cloud:master.
diff --git a/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker b/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker
index 5689302..9ca51ab 100755
--- a/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker
+++ b/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker
@@ -1487,9 +1487,10 @@ def amqp_connect(cfg, callback):
contexts = ["", "huge-", "ppa-"]
+worker_upstream_percentage = int(cfg.get("autopkgtest", "worker_upstream_percentage"))
# crude way to not allow upstream tests to monopolise resources - only 50%
# of workers will take them
-if random.randint(1, 100) < 50:
+if random.randint(1, 100) < worker_upstream_percentage:
contexts += ["upstream-"]
for release in cfg.get("autopkgtest", "releases").split():
diff --git a/charms/focal/autopkgtest-cloud-worker/config.yaml b/charms/focal/autopkgtest-cloud-worker/config.yaml
index e7bbfba..8780bbe 100644
--- a/charms/focal/autopkgtest-cloud-worker/config.yaml
+++ b/charms/focal/autopkgtest-cloud-worker/config.yaml
@@ -114,3 +114,8 @@ options:
default: ""
description: config for periodic cleanup of /tmp directory
type: string
+ worker-upstream-percentage:
+default: 50
+description: Percentage of workers that'll accept upstream tests.
+ This is useful to prioritise certain tests.
+type: int
diff --git a/charms/focal/autopkgtest-cloud-worker/reactive/autopkgtest_cloud_worker.py b/charms/focal/autopkgtest-cloud-worker/reactive/autopkgtest_cloud_worker.py
index 38b6c7a..d48baff 100644
--- a/charms/focal/autopkgtest-cloud-worker/reactive/autopkgtest_cloud_worker.py
+++ b/charms/focal/autopkgtest-cloud-worker/reactive/autopkgtest_cloud_worker.py
@@ -500,6 +500,7 @@ def write_swift_config():
"config.changed.lxd-remotes",
"config.changed.mirror",
"config.changed.net-name",
+"config.changed.worker-upstream-percentage",
)
@when_any("config.set.nova-rcs", "config.set.lxd-remotes")
def write_worker_config():
@@ -524,6 +525,7 @@ def write_worker_config():
"setup_command": config().get("worker-setup-command"),
"setup_command2": config().get("worker-setup-command2"),
"per_package_config_dir": AUTOPKGTEST_PER_PACKAGE_LOCATION,
+"worker_upstream_percentage": config().get("worker-upstream-percentage"),
},
"virt": {
"package_size_default": config().get("worker-default-flavor"),
@@ -543,7 +545,8 @@ def write_worker_config():
for k in replacements: # pylint: disable=consider-using-dict-items
if replacements[k]:
-s = s.replace(k, replacements[k])
+if isinstance(s, str):
+s = s.replace(k, replacements[k])
return s
diff --git a/mojo/service-bundle b/mojo/service-bundle
index f2da41c..315e045 100644
--- a/mojo/service-bundle
+++ b/mojo/service-bundle
@@ -75,6 +75,7 @@ applications:
<<: *common-options
nova-rcs: include-base64://{{local_dir}}/novarcs.tar
worker-tmp-cleanup-config: D /tmp 1777 root root 30d
+worker-upstream-percentage: 50
{%- if stage_name == "production" %}
net-name: net_prod-proposed-migration
worker-default-flavor: autopkgtest
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:worker-upstream-percentage into autopkgtest-cloud:master
Tim Andersson has proposed merging
~andersson123/autopkgtest-cloud:worker-upstream-percentage into
autopkgtest-cloud:master.
Requested reviews:
Canonical's Ubuntu QA (canonical-ubuntu-qa)
For more details, see:
https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/464318
--
Your team Canonical's Ubuntu QA is requested to review the proposed merge of
~andersson123/autopkgtest-cloud:worker-upstream-percentage into
autopkgtest-cloud:master.
diff --git a/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker b/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker
index 5689302..695e068 100755
--- a/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker
+++ b/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker
@@ -1487,9 +1487,21 @@ def amqp_connect(cfg, callback):
contexts = ["", "huge-", "ppa-"]
+try:
+worker_upstream_percentage = int(
+cfg.get("autopkgtest", "worker_upstream_percentage")
+)
+# catch NoOption, NoSection incase something wrong with config file
+# catch ValueError if int casting unsuccessful
+except (
+configparser.NoOptionError,
+configparser.NoSectionError,
+ValueError,
+) as _:
+worker_upstream_percentage = 50
# crude way to not allow upstream tests to monopolise resources - only 50%
# of workers will take them
-if random.randint(1, 100) < 50:
+if random.randint(1, 100) < worker_upstream_percentage:
contexts += ["upstream-"]
for release in cfg.get("autopkgtest", "releases").split():
diff --git a/charms/focal/autopkgtest-cloud-worker/config.yaml b/charms/focal/autopkgtest-cloud-worker/config.yaml
index e7bbfba..8780bbe 100644
--- a/charms/focal/autopkgtest-cloud-worker/config.yaml
+++ b/charms/focal/autopkgtest-cloud-worker/config.yaml
@@ -114,3 +114,8 @@ options:
default: ""
description: config for periodic cleanup of /tmp directory
type: string
+ worker-upstream-percentage:
+default: 50
+description: Percentage of workers that'll accept upstream tests.
+ This is useful to prioritise certain tests.
+type: int
diff --git a/charms/focal/autopkgtest-cloud-worker/reactive/autopkgtest_cloud_worker.py b/charms/focal/autopkgtest-cloud-worker/reactive/autopkgtest_cloud_worker.py
index 38b6c7a..f94b03b 100644
--- a/charms/focal/autopkgtest-cloud-worker/reactive/autopkgtest_cloud_worker.py
+++ b/charms/focal/autopkgtest-cloud-worker/reactive/autopkgtest_cloud_worker.py
@@ -500,6 +500,7 @@ def write_swift_config():
"config.changed.lxd-remotes",
"config.changed.mirror",
"config.changed.net-name",
+"config.changed.worker-upstream-percentage",
)
@when_any("config.set.nova-rcs", "config.set.lxd-remotes")
def write_worker_config():
@@ -524,6 +525,9 @@ def write_worker_config():
"setup_command": config().get("worker-setup-command"),
"setup_command2": config().get("worker-setup-command2"),
"per_package_config_dir": AUTOPKGTEST_PER_PACKAGE_LOCATION,
+"worker_upstream_percentage": config().get(
+"worker-upstream-percentage"
+),
},
"virt": {
"package_size_default": config().get("worker-default-flavor"),
@@ -543,7 +547,8 @@ def write_worker_config():
for k in replacements: # pylint: disable=consider-using-dict-items
if replacements[k]:
-s = s.replace(k, replacements[k])
+if isinstance(s, str):
+s = s.replace(k, replacements[k])
return s
diff --git a/mojo/service-bundle b/mojo/service-bundle
index f2da41c..315e045 100644
--- a/mojo/service-bundle
+++ b/mojo/service-bundle
@@ -75,6 +75,7 @@ applications:
<<: *common-options
nova-rcs: include-base64://{{local_dir}}/novarcs.tar
worker-tmp-cleanup-config: D /tmp 1777 root root 30d
+worker-upstream-percentage: 50
{%- if stage_name == "production" %}
net-name: net_prod-proposed-migration
worker-default-flavor: autopkgtest
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
Re: [Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:worker-upstream-percentage into autopkgtest-cloud:master
I should add some logging in the exception, actually -- https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/464318 Your team Canonical's Ubuntu QA is requested to review the proposed merge of ~andersson123/autopkgtest-cloud:worker-upstream-percentage into autopkgtest-cloud:master. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Merge] ~hyask/autopkgtest-cloud:skia/private_ppa_noble into autopkgtest-cloud:master
Skia has proposed merging ~hyask/autopkgtest-cloud:skia/private_ppa_noble into
autopkgtest-cloud:master.
Requested reviews:
Canonical's Ubuntu QA (canonical-ubuntu-qa)
For more details, see:
https://code.launchpad.net/~hyask/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/464327
Main high level change is to enable the use of private PPAs on Noble.
Lower-level changes are:
* move away from `apt-key`.
* get the `release` in a way that is deb822 compatible.
* remove the `noble`-specific quirk that was added when it became deb822-only.
--
Your team Canonical's Ubuntu QA is requested to review the proposed merge of
~hyask/autopkgtest-cloud:skia/private_ppa_noble into autopkgtest-cloud:master.
diff --git a/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker b/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker
index 5689302..14fd91d 100755
--- a/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker
+++ b/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker
@@ -912,33 +912,23 @@ def request(msg):
)
else:
ppaprefix = "http://";
-if release == "noble":
-# add GPG key
-argv += [
-"--setup-commands",
-"apt-get install -y software-properties-common",
-]
-# add apt source
-argv += [
-"--setup-commands",
-"add-apt-repository --enable-source --yes ppa:%(u)s/%(p)s"
-% {"u": ppauser, "p": ppaname},
-]
-else:
-# add GPG key
-argv += [
-"--setup-commands",
-"apt-key adv --keyserver keyserver.ubuntu.com --recv-key "
-+ fingerprint,
-]
-# add apt source
-argv += [
-"--setup-commands",
-'REL=$(sed -rn "/^(deb|deb-src) .*(ubuntu.com|ftpmaster)/ { s/^[^ ]+ +(\[.*\] *)?[^ ]* +([^ -]+) +.*$/\\2/p; q }" /etc/apt/sources.list); '
-'echo "deb %(prefix)sppa.launchpad.net/%(u)s/%(p)s/ubuntu $REL main" > /etc/apt/sources.list.d/autopkgtest-%(u)s-%(p)s.list; '
-'echo "deb-src %(prefix)sppa.launchpad.net/%(u)s/%(p)s/ubuntu $REL main" >> /etc/apt/sources.list.d/autopkgtest-%(u)s-%(p)s.list;'
-% {"prefix": ppaprefix, "u": ppauser, "p": ppaname},
-]
+# add GPG key
+# we need to `gpg --dearmor` because at least trusty doesn't seem to support asc keys and
+# OpenPGP HKS protocol doesn't specify a way to directly download unarmored keys
+# both wget and gpg are thus required on the testbed, and both are present on the cloud images by default
+argv += [
+"--setup-commands",
+f"wget -O- 'http://keyserver.ubuntu.com/pks/lookup?op=get&options=mr&v=1&search=0x{fingerprint}' | "
+f"gpg --dearmor > /etc/apt/trusted.gpg.d/autopkgtest-{ppauser}-{ppaname}.gpg",
+]
+# add apt source
+argv += [
+"--setup-commands",
+"REL=$(lsb_release -cs); "
+'echo "deb %(prefix)sppa.launchpad.net/%(u)s/%(p)s/ubuntu $REL main" > /etc/apt/sources.list.d/autopkgtest-%(u)s-%(p)s.list; '
+'echo "deb-src %(prefix)sppa.launchpad.net/%(u)s/%(p)s/ubuntu $REL main" >> /etc/apt/sources.list.d/autopkgtest-%(u)s-%(p)s.list;'
+% {"prefix": ppaprefix, "u": ppauser, "p": ppaname},
+]
# put results into separate container, named by the last PPA
container += "-%s-%s" % (ppauser, ppaname)
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
Re: [Canonical-ubuntu-qa] [Merge] ~hyask/autopkgtest-cloud:skia/private_ppa_noble into autopkgtest-cloud:master
WARNING: this has **not** been tested yet, we are still waiting for a private PPA to be setup for our team. -- https://code.launchpad.net/~hyask/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/464327 Your team Canonical's Ubuntu QA is requested to review the proposed merge of ~hyask/autopkgtest-cloud:skia/private_ppa_noble into autopkgtest-cloud:master. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:resize-docs into autopkgtest-cloud:master
Tim Andersson has proposed merging ~andersson123/autopkgtest-cloud:resize-docs
into autopkgtest-cloud:master.
Requested reviews:
Canonical's Ubuntu QA (canonical-ubuntu-qa)
For more details, see:
https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/464343
--
Your team Canonical's Ubuntu QA is requested to review the proposed merge of
~andersson123/autopkgtest-cloud:resize-docs into autopkgtest-cloud:master.
diff --git a/docs/administration.rst b/docs/administration.rst
index 3bc80b9..f908478 100644
--- a/docs/administration.rst
+++ b/docs/administration.rst
@@ -371,3 +371,51 @@ when you have lots of obsoleted packages, would be like so:
for pkg in $packages; do for arch in amd64 arm64 s390x ppc64el armhf i386; do ./filter-amqp -v debci-huge-noble-$arch "$pkg\b"; done; done
This way you can remove all the packages in one command on every architecture.
+
+Resizing /tmp partitions
+
+
+UNFINISHED ADD MORE DETAIL!
+
+BEFORE DOING ANY OF THE STEPS HERE, RUN:
+.. code-block::
+ # on the worker machine with the volume you intend to resize
+ chmod -x autopkgtest-cloud/worker/worker
+ sudo systemctl stop autopkgtest.target # ensure that you WAIT for all running jobs to finish, i.e. for the stop command to exit
+
+First check that this specific version of openstack is available via:
+
+.. code-block::
+ openstack --os-volume-api-version 3.42 volume list
+
+The command should not fail.
+
+To resize a volume:
+
+.. code-block::
+ # check the storage name
+ juju storage # shows all existing storage volumes (aside from root partitions)
+ # get the 'openstack' name for the volume
+ openstack volume list # $num from tmp/$num should be appended at the end of the volume name
+ # from the above command, get the id, and set it to a variable: VOLUME_ID
+ openstack --os-volume-api-version 3.42 volume set ${VOLUME_ID?} --size ${NEW_SIZE}
+ # this will begin the process of resizing the volume
+ # whilst this is happening, consider running this:
+ while true; do openstack volume show $VOLUME_ID; sleep 5; clear; done
+ # If the volume in question has been retyped (DEFAULT <-> ceph nvme), run the following (not necessary for volumes that haven't been retyped):
+ nova reboot $server_name
+ # where $server_name is the name of the server associated with the volume
+ # to check this:
+ juju storage # make note of the juju unit name associated with the storage you've resized
+ # then
+ openstack server list
+ # and get the server name of the server running the unit mentioned in juju storage
+ # after rebooting, run the following ON THE SERVER you've rebooted
+ lsblk # check that the disk size has increased
+ sudo growpart /dev/vdb 1
+ sudo resize2fs /dev/vdb1
+ lsblk # check that the disk size and partition sizes match
+
+
+
+
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:resize-docs into autopkgtest-cloud:master
The proposal to merge ~andersson123/autopkgtest-cloud:resize-docs into autopkgtest-cloud:master has been updated. Status: Needs review => Work in progress For more details, see: https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/464343 -- Your team Canonical's Ubuntu QA is requested to review the proposed merge of ~andersson123/autopkgtest-cloud:resize-docs into autopkgtest-cloud:master. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2054908] Re: gpg-wks-server pulls in postfix
*** This bug is a duplicate of bug 2060578 *** https://bugs.launchpad.net/bugs/2060578 This was fixed in u-r-u in bug 2060578 ** No longer affects: ubuntu-release-upgrader (Ubuntu) -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to Auto Package Testing. https://bugs.launchpad.net/bugs/2054908 Title: gpg-wks-server pulls in postfix Status in Auto Package Testing: Fix Released Status in apt package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: Won't Fix Status in munin package in Ubuntu: Invalid Bug description: Example 1 I did a sudo apt dist-upgrade today on my developer machine running Ubuntu Desktop 24.04 LTS and it surprisingly pulled in postfix. I did not built this into a full reproducible test case because I found another test case… Example 2 munin's autopkgtests are now failing because postfix is now unexpectedly being installed. https://autopkgtest.ubuntu.com/packages/munin/noble/amd64 Other Info gnupg2's changelog indicates that there was an attempt to avoid this misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is **nothing** in Ubuntu 24.04 LTS that Depends or Recommends gpg-wks-server. I added a munin bug task as a pointer in case anyone wonder's about the autopkgtest regression but I don't believe munin needs any changes. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2054908/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2054908] Re: gpg-wks-server pulls in postfix
*** This bug is a duplicate of bug 2060578 *** https://bugs.launchpad.net/bugs/2060578 ** This bug has been marked a duplicate of bug 2060578 postfix installed during release upgrade to Noble -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to Auto Package Testing. https://bugs.launchpad.net/bugs/2054908 Title: gpg-wks-server pulls in postfix Status in Auto Package Testing: Fix Released Status in apt package in Ubuntu: Invalid Status in gnupg2 package in Ubuntu: Won't Fix Status in munin package in Ubuntu: Invalid Bug description: Example 1 I did a sudo apt dist-upgrade today on my developer machine running Ubuntu Desktop 24.04 LTS and it surprisingly pulled in postfix. I did not built this into a full reproducible test case because I found another test case… Example 2 munin's autopkgtests are now failing because postfix is now unexpectedly being installed. https://autopkgtest.ubuntu.com/packages/munin/noble/amd64 Other Info gnupg2's changelog indicates that there was an attempt to avoid this misbehavior by having gnupg only Suggest gpg-wks-server. In fact, there is **nothing** in Ubuntu 24.04 LTS that Depends or Recommends gpg-wks-server. I added a munin bug task as a pointer in case anyone wonder's about the autopkgtest regression but I don't believe munin needs any changes. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2054908/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2019472] Re: Trailing dot in fqdn of ps5 VMs regresses some tests (e.g. postfix)
I'm still seeing amavisd-new autopkgtests failing on hosts where the hostname has a trailing dot, like on this run from April 12th, 2024[1]: 889s Running newaliases 889s newaliases: warning: valid_hostname: misplaced delimiter: adt-noble-amd64-amavisd-new-20240412-035435-juju-7f2275-prod-pr.openstack.prodstack5.lan. 889s newaliases: fatal: file /etc/postfix/main.cf: parameter myhostname: bad parameter value: adt-noble-amd64-amavisd-new-20240412-035435-juju-7f2275-prod-pr.openstack.prodstack5.lan. 889s dpkg: error processing package postfix (--configure): 1. https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/amd64/a/amavisd-new/20240412_040959_d1c5f@/log.gz -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to Auto Package Testing. https://bugs.launchpad.net/bugs/2019472 Title: Trailing dot in fqdn of ps5 VMs regresses some tests (e.g. postfix) Status in Auto Package Testing: Fix Released Bug description: On ps5 amd64 VMs (lcy02) we have that: $ hostname --fqdn adt-paride-mantic-postfix.openstack.prodstack5.lan. Note the trailing dot. This causes regressions in some packages, see for example LP: #2019195. Ideally we should fix the regressed packages (the trailing dot is technically correct), but it makes sense to workaround the problem while the packages are getting fixed. Some possibilities are: (1) Remove `manage_etc_hosts: true` from the cloud-init user-data used by the create-nova-image-new-release script. This should prevent the hostname to be set to the name advertised by openstack, and left to the static string 'autopkgtest'. I did some git archeology and manage_etc_hosts initially came from this snippet: # unbreak my server option :-( userdata=`mktemp` trap "rm $userdata" EXIT TERM INT QUIT PIPE /bin/echo -e "#cloud-config\nmanage_etc_hosts: True" > $userdata and that was the *only* use of user-data back then. Looks like it was a workaround for some issue? In any case I can't be sure that disabling manage_etc_hosts won't cause other issues. (2) Remove the trailing dot in /etc/hosts using the setup-canonical.sh script, e.g. sed -Ei '/^127\.0\.1\.1 /s/([a-z])\. /\1 /' /etc/hosts I don't think this can be racey with cloud-init reconfiguring the hostname because testbed-setup removes cloud-init. Cons of this approach: very hacky. We ask cloud-init to manage /etc/hosts (via manage_etc_hosts), but then mangle it manually (not nice). To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2019472/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2019472] Re: Trailing dot in fqdn of ps5 VMs regresses some tests (e.g. postfix)
- logwatch (https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/amd64/l/logwatch/20240412_051526_f03d0@/log.gz) -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to Auto Package Testing. https://bugs.launchpad.net/bugs/2019472 Title: Trailing dot in fqdn of ps5 VMs regresses some tests (e.g. postfix) Status in Auto Package Testing: Fix Released Bug description: On ps5 amd64 VMs (lcy02) we have that: $ hostname --fqdn adt-paride-mantic-postfix.openstack.prodstack5.lan. Note the trailing dot. This causes regressions in some packages, see for example LP: #2019195. Ideally we should fix the regressed packages (the trailing dot is technically correct), but it makes sense to workaround the problem while the packages are getting fixed. Some possibilities are: (1) Remove `manage_etc_hosts: true` from the cloud-init user-data used by the create-nova-image-new-release script. This should prevent the hostname to be set to the name advertised by openstack, and left to the static string 'autopkgtest'. I did some git archeology and manage_etc_hosts initially came from this snippet: # unbreak my server option :-( userdata=`mktemp` trap "rm $userdata" EXIT TERM INT QUIT PIPE /bin/echo -e "#cloud-config\nmanage_etc_hosts: True" > $userdata and that was the *only* use of user-data back then. Looks like it was a workaround for some issue? In any case I can't be sure that disabling manage_etc_hosts won't cause other issues. (2) Remove the trailing dot in /etc/hosts using the setup-canonical.sh script, e.g. sed -Ei '/^127\.0\.1\.1 /s/([a-z])\. /\1 /' /etc/hosts I don't think this can be racey with cloud-init reconfiguring the hostname because testbed-setup removes cloud-init. Cons of this approach: very hacky. We ask cloud-init to manage /etc/hosts (via manage_etc_hosts), but then mangle it manually (not nice). To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2019472/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2019472] Re: Trailing dot in fqdn of ps5 VMs regresses some tests (e.g. postfix)
The same error is happening with: - logcheck (https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/amd64/l/logcheck/20240412_050139_559b0@/log.gz) -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to Auto Package Testing. https://bugs.launchpad.net/bugs/2019472 Title: Trailing dot in fqdn of ps5 VMs regresses some tests (e.g. postfix) Status in Auto Package Testing: Fix Released Bug description: On ps5 amd64 VMs (lcy02) we have that: $ hostname --fqdn adt-paride-mantic-postfix.openstack.prodstack5.lan. Note the trailing dot. This causes regressions in some packages, see for example LP: #2019195. Ideally we should fix the regressed packages (the trailing dot is technically correct), but it makes sense to workaround the problem while the packages are getting fixed. Some possibilities are: (1) Remove `manage_etc_hosts: true` from the cloud-init user-data used by the create-nova-image-new-release script. This should prevent the hostname to be set to the name advertised by openstack, and left to the static string 'autopkgtest'. I did some git archeology and manage_etc_hosts initially came from this snippet: # unbreak my server option :-( userdata=`mktemp` trap "rm $userdata" EXIT TERM INT QUIT PIPE /bin/echo -e "#cloud-config\nmanage_etc_hosts: True" > $userdata and that was the *only* use of user-data back then. Looks like it was a workaround for some issue? In any case I can't be sure that disabling manage_etc_hosts won't cause other issues. (2) Remove the trailing dot in /etc/hosts using the setup-canonical.sh script, e.g. sed -Ei '/^127\.0\.1\.1 /s/([a-z])\. /\1 /' /etc/hosts I don't think this can be racey with cloud-init reconfiguring the hostname because testbed-setup removes cloud-init. Cons of this approach: very hacky. We ask cloud-init to manage /etc/hosts (via manage_etc_hosts), but then mangle it manually (not nice). To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2019472/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2019472] Re: Trailing dot in fqdn of ps5 VMs regresses some tests (e.g. postfix)
- mime-construct (https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/amd64/m/mime-construct/20240412_050518_cab97@/log.gz) -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to Auto Package Testing. https://bugs.launchpad.net/bugs/2019472 Title: Trailing dot in fqdn of ps5 VMs regresses some tests (e.g. postfix) Status in Auto Package Testing: Fix Released Bug description: On ps5 amd64 VMs (lcy02) we have that: $ hostname --fqdn adt-paride-mantic-postfix.openstack.prodstack5.lan. Note the trailing dot. This causes regressions in some packages, see for example LP: #2019195. Ideally we should fix the regressed packages (the trailing dot is technically correct), but it makes sense to workaround the problem while the packages are getting fixed. Some possibilities are: (1) Remove `manage_etc_hosts: true` from the cloud-init user-data used by the create-nova-image-new-release script. This should prevent the hostname to be set to the name advertised by openstack, and left to the static string 'autopkgtest'. I did some git archeology and manage_etc_hosts initially came from this snippet: # unbreak my server option :-( userdata=`mktemp` trap "rm $userdata" EXIT TERM INT QUIT PIPE /bin/echo -e "#cloud-config\nmanage_etc_hosts: True" > $userdata and that was the *only* use of user-data back then. Looks like it was a workaround for some issue? In any case I can't be sure that disabling manage_etc_hosts won't cause other issues. (2) Remove the trailing dot in /etc/hosts using the setup-canonical.sh script, e.g. sed -Ei '/^127\.0\.1\.1 /s/([a-z])\. /\1 /' /etc/hosts I don't think this can be racey with cloud-init reconfiguring the hostname because testbed-setup removes cloud-init. Cons of this approach: very hacky. We ask cloud-init to manage /etc/hosts (via manage_etc_hosts), but then mangle it manually (not nice). To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/2019472/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2061365] Re: ubuntu_kvm_smoke_test failed with "fips: mandatory checksum data missing - aborting" on X-fips
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2061365
Title:
ubuntu_kvm_smoke_test failed with "fips: mandatory checksum data
missing - aborting" on X-fips
Status in ubuntu-kernel-tests:
Fix Released
Bug description:
Issue found with X-fips 4.4.0-1100.107
Test failed with:
fips: mandatory checksum data missing - aborting
Test log:
Running 'sudo -u ubuntu
/home/ubuntu/autotest/client/tests/ubuntu_kvm_smoke_test/the-test amd64'
+ SUT=bjf-test
+ SSH_KEY=/home/ubuntu/.ssh/id_rsa
+ SSH_OPTIONS='-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null
-o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa'
++ awk '{print$2}'
++ lsb_release -c
+ DISTRO=xenial
+ ARCHITECTURE=amd64
+ trap cleanup EXIT
+ '[' -z amd64 ']'
+ kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used
+ '[' 0 '!=' 0 ']'
+ set -e
+ '[' '!' -f /home/ubuntu/.ssh/id_rsa ']'
+ ssh-keygen -f /home/ubuntu/.ssh/id_rsa -t rsa -N ''
Generating public/private rsa key pair.
Your identification has been saved in /home/ubuntu/.ssh/id_rsa.
Your public key has been saved in /home/ubuntu/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:gQ81DpOj3eU6BHHn8f8g9en8yXAoFRXU/bJU7H0c6Q0
ubuntu@kt-x-lfps-fps-s2-bc2r4d20-u-kvm-smk-test-amd64
The key's randomart image is:
+---[RSA 2048]+
| +o+ o .==|
| +B +.o Eo=|
| oo+oo. ..o==|
|. .oo.. o+oO|
| .S. .oo+o|
|o ..=o |
| . . o +.|
|. + o|
| o.|
+[SHA256]-+
+ '[' amd64 = ppc64el ']'
++ uvt-simplestreams-libvirt query
++ grep -P 'xenial.*amd64'
++ true
+ image=
+ '[' -z '' ']'
+ uvt-simplestreams-libvirt sync --source
http://cloud-images.ubuntu.com/daily release=xenial arch=amd64
+ uvt-kvm create bjf-test release=xenial arch=amd64
+ uvt-kvm wait bjf-test --insecure --ssh-private-key-file
/home/ubuntu/.ssh/id_rsa
fips: mandatory checksum data missing - aborting
Traceback (most recent call last):
File "/usr/bin/uvt-kvm", line 35, in
uvtool.libvirt.kvm.main_cli_wrapper(sys.argv[1:])
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 717,
in main_cli_wrapper
main(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 712,
in main
args.func(parser, args)
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 645,
in main_wait
main_wait_remote(parser, args)
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 613,
in main_wait_remote
private_key_file=args.ssh_private_key_file,
File "/usr/lib/python2.7/dist-packages/uvtool/libvirt/kvm.py", line 497,
in ssh
ssh_call, preexec_fn=subprocess_setup, close_fds=True, stdin=stdin
File "/usr/lib/python2.7/subprocess.py", line 541, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '[u'ssh', u'-o',
u'UserKnownHostsFile=/dev/null', u'-o', u'StrictHostKeyChecking=no', u'-o',
u'CheckHostIP=no', u'-l', u'ubuntu', u'-i', '/home/ubuntu/.ssh/id_rsa',
u'192.168.122.40', u'env', u'UVTOOL_WAIT_INTERVAL=8.0',
u'UVTOOL_WAIT_TIMEOUT=120.0', u'sh', u'-']' returned non-zero exit status 255
+ cleanup
+ uvt-kvm destroy bjf-test
+ '[' amd64 = ppc64el ']'
This issue does not exist in X-fips 4.4.0-1099.106 from the previous
cycle (s2024.02.05). But it's earlier than the recent fipsdevppa
change was implemented.
This affects just X-fips, other releases appears to have the dependency
configure properly.
We just need to install openssh-client-hmac for this test.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2061365/+subscriptions
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
