| 2017-07-18 09:56:27 |
Łukasz Zemczak |
bug |
|
|
added bug |
| 2017-07-18 09:56:36 |
Łukasz Zemczak |
ubuntu-image: status |
New |
Triaged |
|
| 2017-07-18 09:56:50 |
Łukasz Zemczak |
bug task added |
|
ubuntu-image (Ubuntu) |
|
| 2017-07-18 09:57:03 |
Łukasz Zemczak |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-07-18 09:57:03 |
Łukasz Zemczak |
bug task added |
|
ubuntu-image (Ubuntu Zesty) |
|
| 2017-07-18 09:57:03 |
Łukasz Zemczak |
nominated for series |
|
Ubuntu Yakkety |
|
| 2017-07-18 09:57:03 |
Łukasz Zemczak |
bug task added |
|
ubuntu-image (Ubuntu Yakkety) |
|
| 2017-07-18 09:57:03 |
Łukasz Zemczak |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-07-18 09:57:03 |
Łukasz Zemczak |
bug task added |
|
ubuntu-image (Ubuntu Xenial) |
|
| 2017-07-19 13:21:44 |
Łukasz Zemczak |
ubuntu-image: status |
Triaged |
In Progress |
|
| 2017-07-24 15:52:21 |
Launchpad Janitor |
ubuntu-image (Ubuntu): status |
New |
Fix Released |
|
| 2017-07-25 11:10:39 |
Łukasz Zemczak |
description |
We have an autopkgtest called snap.sh that checks if we're able to properly build an ubuntu-image snap from the current source and that the resulting tool is usable. This test started failing with ubuntu-image 1.1 for armhf, ppc64el and s390x.
By checking the test logs, this test was never really working for archs other than amd64 and i386. The snap never really got properly built and installed, and the test only passed because, for some reason, ubuntu-image was available as a deb (you can see it in the old logs by examining the ubuntu-image --version output, stating a non-snap version number). Starting with changes from 1.1, we now have some tests that make sure the deb is not installed.
In theory building the ubuntu-image snap should be possible on all arches. In practice, on all the fancy archs basically the core snap is *always* failing to install with:
error: cannot communicate with server: Post http://localhost/v2/snaps/core: dial unix /run/snapd.socket: connect: connection refused
This doesn't seem to be a transient error. This causes ubuntu-image to not migrate. |
[Impact]
With the current ubuntu-image 1.1, it is impossible for the package to migrate to the release pocket as the autopkgtests for armhf, ppc64el and am64 will be failing (the snap.sh test). This test does not make sense to be ran as part of .deb migration as it's testing snap buildability - it's a bad idea to mix those two worlds.
[Test Case]
Make sure that all the autopkgtests pass for all architectures (with the snap.sh test skipped).
[Regression Potential]
None. This is only a test change. Skipping the test on package migration introduces no real possibility of regressions. Snap buildability is checked during the github source CI for each pull-request. Besides, snap buildability is a feature of the source that is not used by the .deb parts and is completely irrelevant to users.
[Original Description]
We have an autopkgtest called snap.sh that checks if we're able to properly build an ubuntu-image snap from the current source and that the resulting tool is usable. This test started failing with ubuntu-image 1.1 for armhf, ppc64el and s390x.
By checking the test logs, this test was never really working for archs other than amd64 and i386. The snap never really got properly built and installed, and the test only passed because, for some reason, ubuntu-image was available as a deb (you can see it in the old logs by examining the ubuntu-image --version output, stating a non-snap version number). Starting with changes from 1.1, we now have some tests that make sure the deb is not installed.
In theory building the ubuntu-image snap should be possible on all arches. In practice, on all the fancy archs basically the core snap is *always* failing to install with:
error: cannot communicate with server: Post http://localhost/v2/snaps/core: dial unix /run/snapd.socket: connect: connection refused
This doesn't seem to be a transient error. This causes ubuntu-image to not migrate. |
|
| 2017-07-25 11:10:54 |
Łukasz Zemczak |
ubuntu-image (Ubuntu Yakkety): status |
New |
Invalid |
|
| 2017-07-25 11:11:39 |
Łukasz Zemczak |
ubuntu-image: status |
In Progress |
Fix Committed |
|
| 2017-07-27 23:06:19 |
Brian Murray |
bug |
|
|
added subscriber Brian Murray |
| 2017-08-04 18:21:02 |
Steve Langasek |
description |
[Impact]
With the current ubuntu-image 1.1, it is impossible for the package to migrate to the release pocket as the autopkgtests for armhf, ppc64el and am64 will be failing (the snap.sh test). This test does not make sense to be ran as part of .deb migration as it's testing snap buildability - it's a bad idea to mix those two worlds.
[Test Case]
Make sure that all the autopkgtests pass for all architectures (with the snap.sh test skipped).
[Regression Potential]
None. This is only a test change. Skipping the test on package migration introduces no real possibility of regressions. Snap buildability is checked during the github source CI for each pull-request. Besides, snap buildability is a feature of the source that is not used by the .deb parts and is completely irrelevant to users.
[Original Description]
We have an autopkgtest called snap.sh that checks if we're able to properly build an ubuntu-image snap from the current source and that the resulting tool is usable. This test started failing with ubuntu-image 1.1 for armhf, ppc64el and s390x.
By checking the test logs, this test was never really working for archs other than amd64 and i386. The snap never really got properly built and installed, and the test only passed because, for some reason, ubuntu-image was available as a deb (you can see it in the old logs by examining the ubuntu-image --version output, stating a non-snap version number). Starting with changes from 1.1, we now have some tests that make sure the deb is not installed.
In theory building the ubuntu-image snap should be possible on all arches. In practice, on all the fancy archs basically the core snap is *always* failing to install with:
error: cannot communicate with server: Post http://localhost/v2/snaps/core: dial unix /run/snapd.socket: connect: connection refused
This doesn't seem to be a transient error. This causes ubuntu-image to not migrate. |
[Impact]
With the current ubuntu-image 1.1, it is impossible for the package to migrate to the release pocket as the autopkgtests for armhf, ppc64el and arm64 will fail (the snap.sh test). This test does not make sense to be run as part of .deb migration as it's testing snap buildability - it's a bad idea to mix those two worlds.
[Test Case]
Make sure that all the autopkgtests pass for all architectures (with the snap.sh test skipped).
[Regression Potential]
None. This is only a test change. Skipping the test on package migration introduces no real possibility of regressions. Snap buildability is checked during the github source CI for each pull-request. Besides, snap buildability is a feature of the source that is not used by the .deb parts and is completely irrelevant to users.
[Original Description]
We have an autopkgtest called snap.sh that checks if we're able to properly build an ubuntu-image snap from the current source and that the resulting tool is usable. This test started failing with ubuntu-image 1.1 for armhf, ppc64el and s390x.
By checking the test logs, this test was never really working for archs other than amd64 and i386. The snap never really got properly built and installed, and the test only passed because, for some reason, ubuntu-image was available as a deb (you can see it in the old logs by examining the ubuntu-image --version output, stating a non-snap version number). Starting with changes from 1.1, we now have some tests that make sure the deb is not installed.
In theory building the ubuntu-image snap should be possible on all arches. In practice, on all the fancy archs basically the core snap is *always* failing to install with:
error: cannot communicate with server: Post http://localhost/v2/snaps/core: dial unix /run/snapd.socket: connect: connection refused
This doesn't seem to be a transient error. This causes ubuntu-image to not migrate. |
|
| 2017-08-04 18:22:45 |
Steve Langasek |
ubuntu-image (Ubuntu Zesty): status |
New |
Fix Committed |
|
| 2017-08-04 18:22:46 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-08-04 18:22:47 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2017-08-04 18:22:51 |
Steve Langasek |
tags |
|
verification-needed verification-needed-zesty |
|
| 2017-08-04 18:26:02 |
Steve Langasek |
ubuntu-image (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2017-08-04 18:26:09 |
Steve Langasek |
tags |
verification-needed verification-needed-zesty |
verification-needed verification-needed-xenial verification-needed-zesty |
|
| 2017-08-09 08:25:14 |
Łukasz Zemczak |
tags |
verification-needed verification-needed-xenial verification-needed-zesty |
verification-done-xenial verification-done-zesty |
|
| 2017-08-17 21:26:46 |
Launchpad Janitor |
ubuntu-image (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-08-17 21:26:54 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-08-17 21:27:48 |
Launchpad Janitor |
ubuntu-image (Ubuntu Zesty): status |
Fix Committed |
Fix Released |
|
| 2017-08-28 11:31:18 |
Łukasz Zemczak |
ubuntu-image: status |
Fix Committed |
Fix Released |
|
