Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Pull Fedora from api.ci #1999

Merged
merged 1 commit into from
Feb 27, 2020

Conversation

cgwalters
Copy link
Member

Currently we pull from quay.io and api.ci, and the Fedora registry
is being very flaky. I set up a mirror on api.ci for now.

Currently we pull from quay.io and api.ci, and the Fedora registry
is being very flaky.  I set up a mirror on api.ci for now.
@jlebon
Copy link
Member

jlebon commented Feb 27, 2020

/lgtm

@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cgwalters, jlebon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jlebon
Copy link
Member

jlebon commented Feb 27, 2020

   upgrades: Trying to pull registry.svc.ci.openshift.org/coreos/fedora:31...
   upgrades: Getting image source signatures
   upgrades:   Error fetching blob: invalid status code from registry 404 (Not Found)
   upgrades: Error: unable to pull registry.svc.ci.openshift.org/coreos/fedora:31: unable to pull image: Error reading blob sha256:a7fc14226e67b8303c32a1287dbea5ea5e240e8476f6e54a2d0ae54b35597848: Error fetching blob: invalid status code from registry 404 (Not Found)

Hmm weird, it works locally. Maybe it wasn't set up yet when it ran? Anyway, I'm going to override it because I really want to get #1997 in and the only thing that flaked is upgrade and we know that test is fine since it passed in #1997, which is also using the f31 image.

/override continuous-integration/jenkins/pr-merge

@openshift-ci-robot
Copy link
Collaborator

@jlebon: Overrode contexts on behalf of jlebon: continuous-integration/jenkins/pr-merge

In response to this:

  upgrades: Trying to pull registry.svc.ci.openshift.org/coreos/fedora:31...
  upgrades: Getting image source signatures
  upgrades:   Error fetching blob: invalid status code from registry 404 (Not Found)
  upgrades: Error: unable to pull registry.svc.ci.openshift.org/coreos/fedora:31: unable to pull image: Error reading blob sha256:a7fc14226e67b8303c32a1287dbea5ea5e240e8476f6e54a2d0ae54b35597848: Error fetching blob: invalid status code from registry 404 (Not Found)

Hmm weird, it works locally. Maybe it wasn't set up yet when it ran? Anyway, I'm going to override it because I really want to get #1997 in and the only thing that flaked is upgrade and we know that test is fine since it passed in #1997, which is also using the f31 image.

/override continuous-integration/jenkins/pr-merge

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@cgwalters
Copy link
Member Author

This one failed too with a 404. Weird. I can pull it from outside just fine.

And I can also

oc run -i -t walters-sh --image=registry.svc.ci.openshift.org/coreos/fedora:31 --restart=Never
If you don't see a command prompt, try pressing enter.
bash-5.0$ 

just fine.

I wonder if this is possibly related to qemu usermode networking?

@cgwalters
Copy link
Member Author

I think a pattern we should enable BTW is having mantle inject content (including container images) from the host.

@openshift-merge-robot openshift-merge-robot merged commit 21bdb54 into coreos:master Feb 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants