[release-4.9] Bug 2053149: Fix catalog mirror from files #1064

openshift-cherrypick-robot · 2022-02-10T15:58:30Z

This is an automated cherry-pick of #1058

/assign vitus133

This commit fixes `oc adm catalog mirror` from file to a disconnected registry. For operators with manifest media type `application/vnd.oci.image.config.v1+json` mediaType was incorrectly unmarshalled.

openshift-ci · 2022-02-10T16:02:40Z

@openshift-cherrypick-robot: Detected clone of Bugzilla bug 2049133 with correct target release. Retitling PR to link to clone:
/retitle [release-4.9] Bug 2053149: Fix catalog mirror from files

In response to this:

[release-4.9] Bug 2049133: Fix catalog mirror from files

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.

openshift-ci · 2022-02-10T16:03:51Z

@openshift-cherrypick-robot: This pull request references Bugzilla bug 2053149, which is invalid:

expected dependent Bugzilla bug 2049133 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead
expected dependent Bugzilla bug 2049133 to target a release in 4.10.0, but it targets "4.11.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

[release-4.9] Bug 2053149: Fix catalog mirror from files

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.

deejross · 2022-02-10T16:31:02Z

/lgtm
/assign @soltysh

openshift-bot · 2022-02-11T01:00:23Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-11T01:00:28Z

@openshift-bot: This pull request references Bugzilla bug 2053149, which is invalid:

expected the bug to target the "4.9.z" release, but it targets "4.10.z" instead
expected dependent Bugzilla bug 2049133 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead
expected dependent Bugzilla bug 2053175 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2049133 to target a release in 4.10.0, but it targets "4.11.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

soltysh

/approve
/label backport-risk-assessed

openshift-bot · 2022-02-11T16:43:27Z

/retest-required

Please review the full test history for this PR and help us cut down flakes.

openshift-bot · 2022-02-12T01:00:47Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-12T01:00:52Z

@openshift-bot: This pull request references Bugzilla bug 2053149, which is invalid:

expected the bug to target the "4.9.z" release, but it targets "4.10.z" instead
expected dependent Bugzilla bug 2049133 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2053175 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2049133 to target a release in 4.10.0, but it targets "4.11.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

openshift-bot · 2022-02-13T01:00:19Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-13T01:00:23Z

@openshift-bot: This pull request references Bugzilla bug 2053149, which is invalid:

expected the bug to target the "4.9.z" release, but it targets "4.10.z" instead
expected dependent Bugzilla bug 2049133 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2053175 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2049133 to target a release in 4.10.0, but it targets "4.11.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

openshift-bot · 2022-02-14T01:00:22Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-14T01:00:26Z

@openshift-bot: This pull request references Bugzilla bug 2053149, which is invalid:

expected the bug to target the "4.9.z" release, but it targets "4.10.z" instead
expected dependent Bugzilla bug 2049133 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA instead
expected dependent Bugzilla bug 2053175 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2049133 to target a release in 4.10.0, but it targets "4.11.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

jianzhangbjz · 2022-02-14T08:49:10Z

/bugzilla refresh

openshift-ci · 2022-02-14T08:49:15Z

@jianzhangbjz: This pull request references Bugzilla bug 2053149, which is invalid:

expected dependent Bugzilla bug 2053175 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2049133 to target a release in 4.10.0, but it targets "4.11.0" instead
expected dependent Bugzilla bug 2053175 to target a release in 4.10.0, but it targets "4.10.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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.

cuppett · 2022-02-14T22:14:23Z

/bugzilla refresh

openshift-ci · 2022-02-14T22:14:31Z

@cuppett: This pull request references Bugzilla bug 2053149, which is invalid:

expected dependent Bugzilla bug 2053175 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead
expected dependent Bugzilla bug 2049133 to target a release in 4.10.0, but it targets "4.11.0" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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.

cuppett · 2022-02-14T22:16:53Z

/bugzilla refresh

openshift-ci · 2022-02-14T22:17:03Z

@cuppett: This pull request references Bugzilla bug 2053149, which is invalid:

expected dependent Bugzilla bug 2053175 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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.

jianzhangbjz · 2022-02-15T00:59:47Z

/label qe-approved

openshift-bot · 2022-02-15T01:00:58Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-15T01:01:02Z

@openshift-bot: This pull request references Bugzilla bug 2053149, which is invalid:

expected dependent Bugzilla bug 2053175 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is POST instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

openshift-bot · 2022-02-16T01:01:08Z

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

openshift-ci · 2022-02-16T01:01:13Z

@openshift-bot: This pull request references Bugzilla bug 2053149, which is invalid:

expected dependent Bugzilla bug 2053175 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is MODIFIED instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

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.

jianzhangbjz · 2022-02-16T02:55:36Z

/bugzilla refresh

openshift-ci · 2022-02-16T02:55:41Z

@jianzhangbjz: This pull request references Bugzilla bug 2053149, which is valid.

6 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target release (4.9.z) matches configured target release for branch (4.9.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
dependent bug Bugzilla bug 2053175 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
dependent Bugzilla bug 2053175 targets the "4.10.0" release, which is one of the valid target releases: 4.10.0
bug has dependents

Requesting review from QA contact:
/cc @jianzhangbjz

In response to this:

/bugzilla refresh

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.

jianzhangbjz · 2022-02-16T02:56:38Z

/label cherry-pick-approved

openshift-ci · 2022-02-16T02:56:39Z

@jianzhangbjz: Can not set label cherry-pick-approved: Must be member in one of these teams: []

In response to this:

/label cherry-pick-approved

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.

jianzhangbjz · 2022-02-16T02:57:51Z

/lgtm

openshift-ci · 2022-02-16T02:59:31Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deejross, jianzhangbjz, openshift-cherrypick-robot, soltysh

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:

~~OWNERS~~ [soltysh]

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

zhouying7780 · 2022-02-16T03:01:07Z

/label cherry-pick-approved

openshift-ci · 2022-02-16T05:03:45Z

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

openshift-ci · 2022-02-16T05:05:00Z

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

openshift/oc#1064

Bugzilla bug 2053149 has been moved to the MODIFIED state.

In response to this:

[release-4.9] Bug 2053149: Fix catalog mirror from files

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.

Fix catalog mirror from files

e1bfb40

This commit fixes `oc adm catalog mirror` from file to a disconnected registry. For operators with manifest media type `application/vnd.oci.image.config.v1+json` mediaType was incorrectly unmarshalled.

openshift-cherrypick-robot mentioned this pull request Feb 10, 2022

Bug 2049133: Fix catalog mirror from files #1058

Merged

openshift-ci bot assigned vitus133 Feb 10, 2022

openshift-ci bot changed the title ~~[release-4.9] Bug 2049133: Fix catalog mirror from files~~ [release-4.9] Bug 2053149: Fix catalog mirror from files Feb 10, 2022

openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Feb 10, 2022

openshift-ci bot requested review from smarterclayton and soltysh February 10, 2022 16:09

openshift-ci bot assigned soltysh and deejross Feb 10, 2022

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 10, 2022

soltysh approved these changes Feb 11, 2022

View reviewed changes

openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Feb 11, 2022

openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Feb 15, 2022

openshift-ci bot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Feb 16, 2022

openshift-ci bot removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Feb 16, 2022

openshift-ci bot requested a review from jianzhangbjz February 16, 2022 02:55

openshift-ci bot assigned jianzhangbjz Feb 16, 2022

openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Feb 16, 2022

openshift-merge-robot merged commit 5035cc3 into openshift:release-4.9 Feb 16, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[release-4.9] Bug 2053149: Fix catalog mirror from files #1064

[release-4.9] Bug 2053149: Fix catalog mirror from files #1064

openshift-cherrypick-robot commented Feb 10, 2022

openshift-ci bot commented Feb 10, 2022

openshift-ci bot commented Feb 10, 2022

deejross commented Feb 10, 2022

openshift-bot commented Feb 11, 2022

openshift-ci bot commented Feb 11, 2022

soltysh left a comment

openshift-bot commented Feb 11, 2022

openshift-bot commented Feb 12, 2022

openshift-ci bot commented Feb 12, 2022

openshift-bot commented Feb 13, 2022

openshift-ci bot commented Feb 13, 2022

openshift-bot commented Feb 14, 2022

openshift-ci bot commented Feb 14, 2022

jianzhangbjz commented Feb 14, 2022

openshift-ci bot commented Feb 14, 2022

cuppett commented Feb 14, 2022

openshift-ci bot commented Feb 14, 2022

cuppett commented Feb 14, 2022

openshift-ci bot commented Feb 14, 2022

jianzhangbjz commented Feb 15, 2022

openshift-bot commented Feb 15, 2022

openshift-ci bot commented Feb 15, 2022

openshift-bot commented Feb 16, 2022

openshift-ci bot commented Feb 16, 2022

jianzhangbjz commented Feb 16, 2022

openshift-ci bot commented Feb 16, 2022

jianzhangbjz commented Feb 16, 2022

openshift-ci bot commented Feb 16, 2022

jianzhangbjz commented Feb 16, 2022

openshift-ci bot commented Feb 16, 2022

zhouying7780 commented Feb 16, 2022

openshift-ci bot commented Feb 16, 2022

openshift-ci bot commented Feb 16, 2022

[release-4.9] Bug 2053149: Fix catalog mirror from files #1064

[release-4.9] Bug 2053149: Fix catalog mirror from files #1064

Conversation

openshift-cherrypick-robot commented Feb 10, 2022

openshift-ci bot commented Feb 10, 2022

openshift-ci bot commented Feb 10, 2022

deejross commented Feb 10, 2022

openshift-bot commented Feb 11, 2022

openshift-ci bot commented Feb 11, 2022

soltysh left a comment

Choose a reason for hiding this comment

openshift-bot commented Feb 11, 2022

openshift-bot commented Feb 12, 2022

openshift-ci bot commented Feb 12, 2022

openshift-bot commented Feb 13, 2022

openshift-ci bot commented Feb 13, 2022

openshift-bot commented Feb 14, 2022

openshift-ci bot commented Feb 14, 2022

jianzhangbjz commented Feb 14, 2022

openshift-ci bot commented Feb 14, 2022

cuppett commented Feb 14, 2022

openshift-ci bot commented Feb 14, 2022

cuppett commented Feb 14, 2022

openshift-ci bot commented Feb 14, 2022

jianzhangbjz commented Feb 15, 2022

openshift-bot commented Feb 15, 2022

openshift-ci bot commented Feb 15, 2022

openshift-bot commented Feb 16, 2022

openshift-ci bot commented Feb 16, 2022

jianzhangbjz commented Feb 16, 2022

openshift-ci bot commented Feb 16, 2022

jianzhangbjz commented Feb 16, 2022

openshift-ci bot commented Feb 16, 2022

jianzhangbjz commented Feb 16, 2022

openshift-ci bot commented Feb 16, 2022

zhouying7780 commented Feb 16, 2022

openshift-ci bot commented Feb 16, 2022

openshift-ci bot commented Feb 16, 2022