[release-4.10] Bug 2091738: Fix interpretation of Deployment Status Conditions

[openshift-cherrypick-robot]

This is an automated cherry-pick of #266

/assign sadasu

[openshift-ci]

@openshift-cherrypick-robot: Bugzilla bug 2088428 has been cloned as Bugzilla bug 2091738. Retitling PR to link against new bug.
/retitle [release-4.10] Bug 2091738: Fix interpretation of Deployment Status Conditions

In response to this:

[release-4.10] Bug 2088428: Fix interpretation of Deployment Status Conditions

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-cherrypick-robot: This pull request references Bugzilla bug 2091738, which is invalid:

• expected dependent Bugzilla bug 2088428 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:

[release-4.10] Bug 2091738: Fix interpretation of Deployment Status Conditions

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.

[sadasu]

/label backport-risk-assessed

[sadasu]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, sadasu

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 [sadasu]

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

[rhjanders]

I don't think this is going to work (BZs/PRs may need to be created manually to allow parallel-testing) but trying anyway:

/cherrypick release-4.9

[openshift-cherrypick-robot]

@rhjanders: once the present PR merges, I will cherry-pick it on top of release-4.9 in a new PR and assign it to you.

In response to this:

I don't think this is going to work (BZs/PRs may need to be created manually to allow parallel-testing) but trying anyway:

/cherrypick release-4.9

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.

[rhjanders]

/remove-cherrypick release-4.9

[rhjanders]

/cherrypick cancel

[openshift-cherrypick-robot]

@rhjanders: once the present PR merges, I will cherry-pick it on top of cancel in a new PR and assign it to you.

In response to this:

/cherrypick cancel

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.

[rhjanders]

Looks like there's no trivial way of cancelling cherry-pick request. I will ask the Team later, worst case will close the automated cherry pick once it's actually created. Meanwhile I will proceed with manual creation of the backports in the interest of time.

[openshift-ci]

@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.

[rhjanders]

/lgtm

[omichaeli]

/label cherry-pick-approved

[openshift-bot]

/bugzilla refresh

Recalculating validity in case the underlying Bugzilla bug has changed.

[openshift-ci]

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

• expected dependent Bugzilla bug 2088428 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.

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.

[sadasu]

/bugzilla refresh

[openshift-ci]

@sadasu: This pull request references Bugzilla bug 2091738, which is valid.

6 validation(s) were run on this bug

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

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (augol@redhat.com), skipping review request.

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-cherrypick-robot: All pull requests linked via external trackers have merged:

• openshift/cluster-baremetal-operator#267

Bugzilla bug 2091738 has been moved to the MODIFIED state.

In response to this:

[release-4.10] Bug 2091738: Fix interpretation of Deployment Status Conditions

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-cherrypick-robot]

@rhjanders: new pull request created: #270

In response to this:

I don't think this is going to work (BZs/PRs may need to be created manually to allow parallel-testing) but trying anyway:

/cherrypick release-4.9

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-cherrypick-robot]

@rhjanders: cannot checkout cancel: error checking out cancel: exit status 1. output: error: pathspec 'cancel' did not match any file(s) known to git

In response to this:

/cherrypick cancel

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.