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

Bug 2022188: Image policy should mutate DeploymentConfigs #261

Merged

Conversation

dmage
Copy link
Member

@dmage dmage commented Nov 24, 2021

This is a backport of #259 to address the bug 2022188.

Impact: Resolution of image stream names in deployment configs does not work because the image policy plugin does not know about them.

Cause: The problem exists since the beginning, but it wasn't visible as the image policy plugin used to resolve image streams names in all pods. Once we've fixed the bug 1925180, the plugin doesn't update controlled objects anymore, i.e. it doesn't update pods that are created for the deployment config.

Resolution: Update the admission plugin so that is aware of deployment configs.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 24, 2021

@dmage: An error was encountered querying GitHub for users with public email (xiuwang@redhat.com) for bug 2022188 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details.

Full error message. non-200 OK status code: 403 Forbidden body: "{\n \"documentation_url\": \"https://docs.github.com/en/free-pro-team@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits\",\n \"message\": \"You have exceeded a secondary rate limit. Please wait a few minutes before you try again.\"\n}\n"

Please contact an administrator to resolve this issue, then request a bug refresh with /bugzilla refresh.

In response to this:

Bug 2022188: Image policy should mutate DeploymentConfigs

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 openshift-ci bot requested review from deads2k and sttts November 24, 2021 14:12
@dmage
Copy link
Member Author

dmage commented Nov 25, 2021

/retest

@dmage
Copy link
Member Author

dmage commented Nov 26, 2021

/retest
/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Nov 26, 2021
@dmage
Copy link
Member Author

dmage commented Nov 26, 2021

/assign @sttts

@sttts
Copy link
Contributor

sttts commented Nov 29, 2021

Somebody from the team has to lgtm first.

@dmage
Copy link
Member Author

dmage commented Nov 29, 2021

/assign @flavianmissi

@xiuwang
Copy link

xiuwang commented Nov 30, 2021

/lgtm
/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Nov 30, 2021
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 30, 2021
@xiuwang
Copy link

xiuwang commented Nov 30, 2021

@wangke19 Could you help add /label cherry-pick-approved ? Thanks

@flavianmissi
Copy link
Member

/lgtm

@dmage
Copy link
Member Author

dmage commented Nov 30, 2021

/bugzilla refresh

@dmage
Copy link
Member Author

dmage commented Nov 30, 2021

/assign @wangke19

@openshift-ci openshift-ci bot added the bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. label Nov 30, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 30, 2021

@dmage: This pull request references Bugzilla bug 2022188, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.7.z) matches configured target release for branch (4.7.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2020644 is in the state CLOSED (ERRATA), which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2020644 targets the "4.8.z" release, which is one of the valid target releases: 4.8.0, 4.8.z
  • bug has dependents

Requesting review from QA contact:
/cc @xiuwang

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.

@openshift-ci openshift-ci bot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Nov 30, 2021
@openshift-ci openshift-ci bot requested a review from xiuwang November 30, 2021 13:05
@sttts
Copy link
Contributor

sttts commented Nov 30, 2021

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 30, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dmage, flavianmissi, sttts, xiuwang

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 Nov 30, 2021
@wangke19
Copy link

wangke19 commented Dec 1, 2021

/label cherry-pick-approved

@openshift-ci 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 Dec 1, 2021
@openshift-merge-robot openshift-merge-robot merged commit c35a474 into openshift:release-4.7 Dec 1, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 1, 2021

@dmage: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Bugzilla bug in order for it to move to the next state. Once unlinked, request a bug refresh with /bugzilla refresh.

Bugzilla bug 2022188 has not been moved to the MODIFIED state.

In response to this:

Bug 2022188: Image policy should mutate DeploymentConfigs

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.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants