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

Support RegistryUnavailable type #6842

Merged

Conversation

saschagrunert
Copy link
Member

What type of PR is this?

/kind feature

What this PR does / why we need it:

If we agree on the fix in kubernetes/kubernetes#117612, then we can support the RegistryUnavailable error message as well. This has the benefit that we display the information directly to the end user as better error indicator.

/hold

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

Support `RegistryUnavailable` error on container image pull.

@openshift-ci openshift-ci bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Apr 26, 2023
@openshift-ci openshift-ci bot requested review from klihub and QiWang19 April 26, 2023 09:30
@openshift-ci openshift-ci bot added dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/feature Categorizes issue or PR as related to a new feature. labels Apr 26, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 26, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: saschagrunert

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 26, 2023
@codecov
Copy link

codecov bot commented Apr 26, 2023

Codecov Report

Merging #6842 (66c7547) into main (7d45aa0) will decrease coverage by 0.16%.
The diff coverage is 0.00%.

❗ Current head 66c7547 differs from pull request most recent head bf23f5c. Consider uploading reports for the commit bf23f5c to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6842      +/-   ##
==========================================
- Coverage   49.75%   49.60%   -0.16%     
==========================================
  Files         127      127              
  Lines       14994    14971      -23     
==========================================
- Hits         7461     7426      -35     
- Misses       6645     6655      +10     
- Partials      888      890       +2     

@saschagrunert
Copy link
Member Author

/test e2e-gcp-ovn

@saschagrunert
Copy link
Member Author

saschagrunert commented May 2, 2023

/unhold
kubernetes/kubernetes#117612 merged.

@cri-o/cri-o-maintainers PTAL

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 2, 2023
server/image_pull.go Outdated Show resolved Hide resolved
If we agree on the fix in
kubernetes/kubernetes#117612, then we can
support the `RegistryUnavailable` error message as well. This has the
benefit that we display the information directly to the end user as
better error indicator.

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
@saschagrunert
Copy link
Member Author

@haircommander PTAL again

@haircommander
Copy link
Member

thank you!

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 3, 2023
@openshift-merge-robot openshift-merge-robot merged commit 0941edd into cri-o:main May 3, 2023
56 of 57 checks passed
@saschagrunert saschagrunert deleted the registry-unavailable branch May 3, 2023 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants