cloud-images

daily maas images not being cleaned

Bug #1627739 reported by Scott Moser
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-images
Fix Released
Medium
Unassigned
maas-images
Fix Released
Medium
Unassigned

Bug Description

It seems we've stopped cleaning images from the daily maas stream.

This isn't specific to xenial, but thats the one I've shown here.

$ sstream-query --keyring=/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg --output-format="%(product_name)32s %(version_name)s %(arch)s/%(subarch)s" http://maas.ubuntu.com/images/ephemeral-v2/daily/streams/v1/com.ubuntu.maas:daily:v2:download.sjson ftype=root-image.gz release=xenial arch=amd64 subarch=hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160925 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160922 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160921 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160914 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160909 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160907.1 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160907 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160830 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160826 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160825.1 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160825 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160822 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160819.1 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160815 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160812 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160811 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160805 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160725 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160723 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160721 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160720.1 amd64/hwe-x

Related branches

lp:~smoser/maas-images/trunk.meph-import-out
Lee Trager (community): Approve
Diff: 1036 lines (+504/-421)
5 files modified
bin/meph2-import (+27/-0)
meph2/commands/flags.py (+107/-0)
meph2/commands/meph2_util.py (+25/-421)
meph2/commands/mimport.py (+306/-0)
meph2/util.py (+39/-0)
Revision history for this message
Scott Moser (smoser) wrote :

Seems likely related to
https://cloud-images-jenkins.canonical.com/view/MAAS/job/MAASv2_Cleaner/
not having run successfully since July 25.

Revision history for this message
Scott Moser (smoser) wrote :

failures prior to 20160925 [1]
show a failure 'no module named backports' (from meph2/commands/dpkg.py):

| Sun, 25 Sep 2016 12:15:43 +0000: running cmd: PYTHONPATH=/var/lib/jenkins/jobs/MAASv2_Cleaner/workspace/sstreams:/var/lib/jenkins/jobs/MAASv2_Cleaner/workspace/maasv2 /var/lib/jenkins/jobs/MAASv2_Cleaner/workspace/maasv2/bin/meph2-util clean-md 3 /srv/maas-images/ephemeral-v2/daily//streams/v1/index.json
| Unable to find meph2.commands.meph2_util.main: No module named backports
| failed to run cmd: PYTHONPATH=/var/lib/jenkins/jobs/MAASv2_Cleaner/workspace/sstreams:/var/lib/jenkins/jobs/MAASv2_Cleaner/workspace/maasv2 /var/lib/jenkins/jobs/MAASv2_Cleaner/workspace/maasv2/bin/meph2-util clean-md 3 /srv/maas-images/ephemeral-v2/daily//streams/v1/index.json
| Build step 'Execute shell' marked build as failure
| Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
| Finished: FAILURE

Today's attempt though fails with bzr checkout [2]
| + scripts=/var/lib/jenkins/jobs/MAASv2_Cleaner/workspace/scripts
| + bzr branch 'lp:~ubuntu-on-ec2/vmbuilder/jenkins_kvm' /var/lib/jenkins/jobs/MAASv2_Cleaner/workspace/scripts
| Permission denied (publickey).
| ConnectionReset reading response for 'BzrDir.open_2.1', retrying
| Permission denied (publickey).
| bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist.
| Build step 'Execute shell' marked build as failure
| Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
| Finished: FAILURE

--
[1] https://cloud-images-jenkins.canonical.com/view/MAAS/job/MAASv2_Cleaner/710/console
[2] https://cloud-images-jenkins.canonical.com/view/MAAS/job/MAASv2_Cleaner/711/console

Scott Moser (smoser)
Changed in maas-images:
status: New → Confirmed
Changed in cloud-images:
status: New → Confirmed
importance: Undecided → Medium
Changed in maas-images:
importance: Undecided → Medium
Revision history for this message
Robert C Jennings (rcj) wrote :

Changed the job to create a virtualenv and pip install backports as needed by this job

Changed in cloud-images:
status: Confirmed → Fix Released
Revision history for this message
Robert C Jennings (rcj) wrote :

$ sstream-query --keyring=/usr/share/keyrings/ubuntu-cloudimage-keyring.gpg --output-format="%(product_name)32s %(version_name)s %(arch)s/%(subarch)s" http://maas.ubuntu.com/images/ephemeral-v2/daily/streams/v1/com.ubuntu.maas:daily:v2:download.sjson ftype=root-image.gz release=xenial arch=amd64 subarch=hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160925 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160922 amd64/hwe-x
com.ubuntu.maas.daily:v2:boot:16.04:amd64:hwe-x 20160921 amd64/hwe-x

Revision history for this message
Scott Moser (smoser) wrote :

marking this fix-released as revno 333 now does not need lzma for meph-util.

Changed in maas-images:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.