So heads up because I'm not sure we want docker broken again at GA for F-24.
https://bugzilla.redhat.com/show_bug.cgi?id=1322909
The bug has been open since end of March and is on x86 and it appears F-24 docker binaries are broken so F-24 (and likely other) images don't work on F-24.
I'm not sure how the cloud SIG tests docker deliverables but now might be a good time to move to F-24 on the host.
Peter
On 21/04/16, Peter Robinson wrote:
So heads up because I'm not sure we want docker broken again at GA for F-24.
https://bugzilla.redhat.com/show_bug.cgi?id=1322909
The bug has been open since end of March and is on x86 and it appears F-24 docker binaries are broken so F-24 (and likely other) images don't work on F-24.
I'm not sure how the cloud SIG tests docker deliverables but now might be a good time to move to F-24 on the host.
We have docker related tests enabled but only on Atomic images. As we do not have F24 based atomic images, this error never showed up to us.
The question now is, should we install docker on the Cloud base image, and do the docker related tests on it as gating tests? Any thoughts?
Kushal
On 22/04/16, Kushal Das wrote:
On 21/04/16, Peter Robinson wrote:
So heads up because I'm not sure we want docker broken again at GA for F-24.
https://bugzilla.redhat.com/show_bug.cgi?id=1322909
The bug has been open since end of March and is on x86 and it appears F-24 docker binaries are broken so F-24 (and likely other) images don't work on F-24.
I'm not sure how the cloud SIG tests docker deliverables but now might be a good time to move to F-24 on the host.
We have docker related tests enabled but only on Atomic images. As we do not have F24 based atomic images, this error never showed up to us.
My mistake, autocloud is picking the only base images from F24/rawhide, but not the atomic images, that is why we never saw this error. In the coming days we are moving to compose based testing, I hope that will fix this issue.
Kushal
So heads up because I'm not sure we want docker broken again at GA for F-24.
https://bugzilla.redhat.com/show_bug.cgi?id=1322909
The bug has been open since end of March and is on x86 and it appears F-24 docker binaries are broken so F-24 (and likely other) images don't work on F-24.
I'm not sure how the cloud SIG tests docker deliverables but now might be a good time to move to F-24 on the host.
We have docker related tests enabled but only on Atomic images. As we do not have F24 based atomic images, this error never showed up to us.
My mistake, autocloud is picking the only base images from F24/rawhide, but not the atomic images, that is why we never saw this error. In the coming days we are moving to compose based testing, I hope that will fix this issue.
Please make sure it's been tested by the time we hit Beta RCs so the blocker can be properly tested and verified.
On 22/04/16, Peter Robinson wrote:
So heads up because I'm not sure we want docker broken again at GA for F-24.
https://bugzilla.redhat.com/show_bug.cgi?id=1322909
The bug has been open since end of March and is on x86 and it appears F-24 docker binaries are broken so F-24 (and likely other) images don't work on F-24.
I'm not sure how the cloud SIG tests docker deliverables but now might be a good time to move to F-24 on the host.
We have docker related tests enabled but only on Atomic images. As we do not have F24 based atomic images, this error never showed up to us.
My mistake, autocloud is picking the only base images from F24/rawhide, but not the atomic images, that is why we never saw this error. In the coming days we are moving to compose based testing, I hope that will fix this issue.
Please make sure it's been tested by the time we hit Beta RCs so the blocker can be properly tested and verified.
Yes, working on a hotfix. In the coming days autocloud will also move to compose based testing than koji build based (the current model).
Kushal
On Fri, Apr 22, 2016 at 4:46 PM, Kushal Das mail@kushaldas.in wrote:
On 21/04/16, Peter Robinson wrote:
So heads up because I'm not sure we want docker broken again at GA for F-24.
https://bugzilla.redhat.com/show_bug.cgi?id=1322909
The bug has been open since end of March and is on x86 and it appears F-24 docker binaries are broken so F-24 (and likely other) images don't work on F-24.
I'm not sure how the cloud SIG tests docker deliverables but now might be a good time to move to F-24 on the host.
We have docker related tests enabled but only on Atomic images. As we do not have F24 based atomic images, this error never showed up to us.
The question now is, should we install docker on the Cloud base image, and do the docker related tests on it as gating tests? Any thoughts?
I think F-24 docker on the F-24 cloud base images makes sense.
On Fri, 2016-04-22 at 21:16 +0530, Kushal Das wrote:
On 21/04/16, Peter Robinson wrote:
So heads up because I'm not sure we want docker broken again at GA for F-24.
https://bugzilla.redhat.com/show_bug.cgi?id=1322909
The bug has been open since end of March and is on x86 and it appears F-24 docker binaries are broken so F-24 (and likely other) images don't work on F-24.
I'm not sure how the cloud SIG tests docker deliverables but now might be a good time to move to F-24 on the host.
We have docker related tests enabled but only on Atomic images. As we do not have F24 based atomic images, this error never showed up to us.
We do have F24 Atomic images, autocloud just fails to notice them. fedora_nightlies finds them just fine:
https://www.happyassassin.net/nightlies.html
----- Original Message -----
We do have F24 Atomic images, autocloud just fails to notice them. fedora_nightlies finds them just fine:
When I boot the latest F24 Atomic qcow2 image there (right now "Fedora-Atomic-24-20160422.n.0.x86_64.qcow2"), the GRUB2 boot menu says: "Fedora 25 (Rawhide) 25.22 (ostree)" and poking around confirms this:
[cloud-user@f24 ~]$ uname -r 4.6.0-0.rc4.git2.1.fc25.x86_64
[cloud-user@f24 ~]$ head /etc/os-release NAME=Fedora VERSION="25 (Rawhide)" ID=fedora VERSION_ID=25 PRETTY_NAME="Fedora 25 (Rawhide)" ANSI_COLOR="0;34" CPE_NAME="cpe:/o:fedoraproject:fedora:25" HOME_URL="https://fedoraproject.org/" BUG_REPORT_URL="https://bugzilla.redhat.com/" REDHAT_BUGZILLA_PRODUCT="Fedora"
Is this expected? When do we expect to sync to F24 content?
Related: https://bugzilla.redhat.com/show_bug.cgi?id=1308537
On Thu, Apr 21, 2016 at 10:38:07PM +0100, Peter Robinson wrote:
I'm not sure how the cloud SIG tests docker deliverables but now might be a good time to move to F-24 on the host.
Looks like there's an automated test that runs in Atomic but is skipped in the cloud base image. To some degree that makes sense, as Docker isn't shipped _on_ that image.
On Thu, Apr 28, 2016 at 12:20 AM, Matthew Miller mattdm@fedoraproject.org wrote:
On Thu, Apr 21, 2016 at 10:38:07PM +0100, Peter Robinson wrote:
I'm not sure how the cloud SIG tests docker deliverables but now might be a good time to move to F-24 on the host.
Looks like there's an automated test that runs in Atomic but is skipped in the cloud base image. To some degree that makes sense, as Docker isn't shipped _on_ that image.
Sure, I don't care how it's tested, but I sent this heads up because clearly it hasn't been tested because it wasn't working. So maybe it's since been fixed or maybe we're missing something and it needs expansion.
-
Adam Williamson -
Jonathan Lebon -
Kushal Das -
Matthew Miller -
Peter Robinson