Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #672

/assign sdodson

The label was dropped back in:

  $ git --no-pager log -1 --oneline 75f34c7
  75f34c7 manifests: Remove run-level, insights operator does not need it

That landed between 4.2 and 4.3:

  $ git --no-pager grep openshift.io/run-level origin/release-4.2 -- manifests
  origin/release-4.2:manifests/02-namespace.yaml:    openshift.io/run-level: "1"
  $ git --no-pager grep openshift.io/run-level origin/release-4.3 -- manifests
  ...no hits...

So clusters which were born in 4.1 or 4.2 may have the old label
still in place.  This commit clears it like
openshift/cluster-version-operator@539e944920 (Fix run-level label to
empty string, 2021-07-07, openshift/cluster-version-operator#623), so
the cluster-version operator will clear the stale label.
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-959 has been cloned as Jira Issue OCPBUGS-1158. Retitling PR to link against new bug.
/retitle [release-4.11] OCPBUGS-1158: manifests/02-namespace: Explicitly clear run-level label

Details

In response to this:

This is an automated cherry-pick of #672

/assign sdodson

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.11] OCPBUGS-959: manifests/02-namespace: Explicitly clear run-level label [release-4.11] OCPBUGS-1158: manifests/02-namespace: Explicitly clear run-level label Sep 12, 2022
@openshift-ci
Copy link

openshift-ci bot commented Sep 12, 2022

@openshift-cherrypick-robot: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

[release-4.11] OCPBUGS-1158: manifests/02-namespace: Explicitly clear run-level label

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-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Sep 12, 2022
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-1158, 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 version (4.11.z) matches configured target version for branch (4.11.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-959 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-959 targets the "4.12.0" version, which is one of the valid target versions: 4.12.0
  • bug has dependents
Details

In response to this:

This is an automated cherry-pick of #672

/assign sdodson

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-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Sep 12, 2022
@sdodson sdodson added approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Sep 12, 2022
@openshift-ci
Copy link

openshift-ci bot commented Sep 12, 2022

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

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

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

@sdodson sdodson added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Sep 12, 2022
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 3e6d182 and 2 for PR HEAD 4b065c2 in total

@sdodson
Copy link
Member

sdodson commented Sep 12, 2022

/override ci/prow/lint

@openshift-ci
Copy link

openshift-ci bot commented Sep 12, 2022

@sdodson: sdodson unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight.

Details

In response to this:

/override ci/prow/lint

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.

@tremes
Copy link
Contributor

tremes commented Sep 13, 2022

/override ci/prow/lint

@tremes
Copy link
Contributor

tremes commented Sep 13, 2022

/test insights-operator-e2e-tests

@openshift-ci
Copy link

openshift-ci bot commented Sep 13, 2022

@tremes: Overrode contexts on behalf of tremes: ci/prow/lint

Details

In response to this:

/override ci/prow/lint

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.

@tremes
Copy link
Contributor

tremes commented Sep 13, 2022

OK ci/prow/insights-operator-e2e-tests failed again. I am overriding. We have to fix the tests for 4.11
/override ci/prow/insights-operator-e2e-tests

@openshift-ci
Copy link

openshift-ci bot commented Sep 13, 2022

@tremes: Overrode contexts on behalf of tremes: ci/prow/insights-operator-e2e-tests

Details

In response to this:

OK ci/prow/insights-operator-e2e-tests failed again. I am overriding. We have to fix the tests for 4.11
/override ci/prow/insights-operator-e2e-tests

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-merge-robot openshift-merge-robot merged commit 3b9cfcb into openshift:release-4.11 Sep 13, 2022
@openshift-ci-robot
Copy link
Contributor

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

Jira Issue OCPBUGS-1158 has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #672

/assign sdodson

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
Copy link

openshift-ci bot commented Sep 13, 2022

@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/insights-operator-e2e-tests 4b065c2 link true /test insights-operator-e2e-tests
ci/prow/lint 4b065c2 link true /test lint

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.

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/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. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira 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.

6 participants