Skip to content

[release-4.9] Bug 2034504: Ensure old deployment is deleted before new deployment creation#162

Merged
openshift-merge-robot merged 1 commit into
openshift:release-4.9from
openshift-cherrypick-robot:cherry-pick-157-to-release-4.9
Jan 5, 2022
Merged

[release-4.9] Bug 2034504: Ensure old deployment is deleted before new deployment creation#162
openshift-merge-robot merged 1 commit into
openshift:release-4.9from
openshift-cherrypick-robot:cherry-pick-157-to-release-4.9

Conversation

@openshift-cherrypick-robot

Copy link
Copy Markdown

This is an automated cherry-pick of #157

/assign vrutkovs

@openshift-ci

openshift-ci Bot commented Dec 21, 2021

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: Bugzilla bug 2028054 has been cloned as Bugzilla bug 2034504. Retitling PR to link against new bug.
/retitle [release-4.9] Bug 2034504: Ensure old deployment is deleted before new deployment creation

Details

In response to this:

[release-4.9] Bug 2028054: Ensure old deployment is deleted before new deployment creation

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 changed the title [release-4.9] Bug 2028054: Ensure old deployment is deleted before new deployment creation [release-4.9] Bug 2034504: Ensure old deployment is deleted before new deployment creation Dec 21, 2021
@openshift-ci 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 Dec 21, 2021
@openshift-ci

openshift-ci Bot commented Dec 21, 2021

Copy link
Copy Markdown
Contributor

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

  • expected dependent Bugzilla bug 2028054 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA 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.

Details

In response to this:

[release-4.9] Bug 2034504: Ensure old deployment is deleted before new deployment creation

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 Fedosin and lobziik December 21, 2021 07:36
@damdo

damdo commented Dec 21, 2021

Copy link
Copy Markdown
Member

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Dec 21, 2021
@damdo

damdo commented Dec 21, 2021

Copy link
Copy Markdown
Member

/retest-required

4 similar comments
@damdo

damdo commented Dec 21, 2021

Copy link
Copy Markdown
Member

/retest-required

@damdo

damdo commented Dec 21, 2021

Copy link
Copy Markdown
Member

/retest-required

@damdo

damdo commented Dec 21, 2021

Copy link
Copy Markdown
Member

/retest-required

@damdo

damdo commented Dec 21, 2021

Copy link
Copy Markdown
Member

/retest-required

@openshift-ci

openshift-ci Bot commented Dec 21, 2021

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ccm eede9ac link false /test e2e-aws-ccm
ci/prow/e2e-openstack-ccm eede9ac link false /test e2e-openstack-ccm

Full PR test history. Your PR dashboard.

Details

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-bot

Copy link
Copy Markdown

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci

openshift-ci Bot commented Dec 22, 2021

Copy link
Copy Markdown
Contributor

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

  • expected dependent Bugzilla bug 2028054 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA 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.

Details

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

Copy link
Copy Markdown

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci

openshift-ci Bot commented Dec 23, 2021

Copy link
Copy Markdown
Contributor

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

  • expected dependent Bugzilla bug 2028054 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA 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.

Details

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

Copy link
Copy Markdown

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci

openshift-ci Bot commented Dec 24, 2021

Copy link
Copy Markdown
Contributor

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

  • expected dependent Bugzilla bug 2028054 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but it is ON_QA 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.

Details

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

Copy link
Copy Markdown

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

@openshift-ci

openshift-ci Bot commented Dec 25, 2021

Copy link
Copy Markdown
Contributor

@openshift-bot: This pull request references Bugzilla bug 2034504, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

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 NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 2028054 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE))
  • dependent Bugzilla bug 2028054 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 @sunzhaohua2

Details

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-ci openshift-ci Bot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Dec 25, 2021
@openshift-ci openshift-ci Bot requested a review from sunzhaohua2 December 25, 2021 01:00
@JoelSpeed

Copy link
Copy Markdown
Contributor

/approve
/label backport-risk-assessed
/skip

@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 Jan 4, 2022
@openshift-ci

openshift-ci Bot commented Jan 4, 2022

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

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

The pull request process is described here

Details 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 Jan 4, 2022
@sunzhaohua2

Copy link
Copy Markdown
Contributor

/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 Jan 5, 2022
@openshift-merge-robot openshift-merge-robot merged commit 1826b16 into openshift:release-4.9 Jan 5, 2022
@openshift-ci

openshift-ci Bot commented Jan 5, 2022

Copy link
Copy Markdown
Contributor

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

Bugzilla bug 2034504 has been moved to the MODIFIED state.

Details

In response to this:

[release-4.9] Bug 2034504: Ensure old deployment is deleted before new deployment creation

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants