Skip to content

Bug 1998029: CustomNoUpgrade should not fire no-upgrade failures#26449

Merged
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
shiftstack:custom_no_upgrade_fixup
Sep 13, 2021
Merged

Bug 1998029: CustomNoUpgrade should not fire no-upgrade failures#26449
openshift-merge-robot merged 1 commit intoopenshift:masterfrom
shiftstack:custom_no_upgrade_fixup

Conversation

@pierreprinetti
Copy link
Copy Markdown
Contributor

Fixup of 5fb0f99 (#26430)

The commit that is being fixed-up introduced a check against a message
that is not implemented anywhere, thus rendering the function
isKubeAPIUpgradableNoUpgradeCondition unusable.

This patch removes the check on the condition message.

/cc JoelSpeed
/assign deads2k

Fixup of 5fb0f99

The commit that is being fixed-up introduced a check against a message
that is not implemented anywhere, thus rendering the function
`isKubeAPIUpgradableNoUpgradeCondition` unusable.

This patch removes the check on the condition message.
@openshift-ci openshift-ci Bot requested a review from JoelSpeed September 3, 2021 09:48
@openshift-ci openshift-ci Bot added bugzilla/severity-medium Referenced Bugzilla bug's severity is medium 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 Sep 3, 2021
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 3, 2021

@pierreprinetti: This pull request references Bugzilla bug 1998029, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, ON_DEV, POST, POST, 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:

Bug 1998029: CustomNoUpgrade should not fire no-upgrade failures

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.

@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/bugzilla refresh

@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 Sep 3, 2021
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 3, 2021

@pierreprinetti: This pull request references Bugzilla bug 1998029, 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.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.9.0) matches configured target release for branch (4.9.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

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

Details

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 removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Sep 3, 2021
Copy link
Copy Markdown
Contributor

@mdbooth mdbooth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks much more robust. I wonder if there was a reason it was originally implemented this way? @JoelSpeed ?

@JoelSpeed
Copy link
Copy Markdown
Contributor

I wonder if there was a reason it was originally implemented this way? @JoelSpeed ?

I think I was just being very explicit about the exact nature of the condition applied by the api server operator, this is fine as well though

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 3, 2021
Copy link
Copy Markdown
Contributor

@Fedosin Fedosin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 3, 2021

@pierreprinetti: 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-agnostic-cmd 8b89e16 link /test e2e-agnostic-cmd
ci/prow/e2e-aws-single-node 8b89e16 link /test e2e-aws-single-node

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.

@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/skip

@openshift-merge-robot
Copy link
Copy Markdown
Contributor

/bugzilla refresh

The requirements for Bugzilla bugs have changed, recalculating validity.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 6, 2021

@openshift-merge-robot: This pull request references Bugzilla bug 1998029, which is invalid:

  • expected the bug to target the "4.10.0" release, but it targets "4.9.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.

Details

In response to this:

/bugzilla refresh

The requirements for Bugzilla bugs have changed, recalculating validity.

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/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. and removed bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Sep 6, 2021
@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/bugzilla refresh

@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 Sep 6, 2021
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 6, 2021

@pierreprinetti: This pull request references Bugzilla bug 1998029, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.10.0) matches configured target release for branch (4.10.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

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

Details

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 removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Sep 6, 2021
@pierreprinetti
Copy link
Copy Markdown
Contributor Author

I believe this requires the attention of @deads2k

Without this patch, we can't get CCM tests green unfortunately (cf openshift/release#21227)

@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/assign mfojtik

@pierreprinetti
Copy link
Copy Markdown
Contributor Author

/cc @bparees

@openshift-ci openshift-ci Bot requested a review from bparees September 13, 2021 08:23
@bparees
Copy link
Copy Markdown
Contributor

bparees commented Sep 13, 2021

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 13, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bparees, Fedosin, JoelSpeed, mdbooth, pierreprinetti

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 Sep 13, 2021
@openshift-merge-robot openshift-merge-robot merged commit 37a0667 into openshift:master Sep 13, 2021
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 13, 2021

@pierreprinetti: All pull requests linked via external trackers have merged:

Bugzilla bug 1998029 has been moved to the MODIFIED state.

Details

In response to this:

Bug 1998029: CustomNoUpgrade should not fire no-upgrade failures

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.

@pierreprinetti pierreprinetti deleted the custom_no_upgrade_fixup branch September 14, 2021 08:25
@wking
Copy link
Copy Markdown
Member

wking commented Nov 18, 2021

/cherrypick release-4.9

@openshift-cherrypick-robot
Copy link
Copy Markdown

@wking: new pull request created: #26615

Details

In response to this:

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

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. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium 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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants