Skip to content

Conversation

@perdasilva
Copy link

@perdasilva perdasilva commented Oct 15, 2024

Preconditions:

  • openshift/api#2066 merged
  • catalogd and o-c APIs promoted to v1 and downsync'ed
  • cluster-olm-operator has been updated to use openshift/api/operator/v1 OLM resource
  • OPRUN-3576 done
  • OPRUN-3589 done (outcome may require changes to this PR)

Changes:

  • removes TechPreview annotation
  • adds cluster profile annotations to all manifests
  • adds OLM v1 cluster capability annotation to all manifests

Next PR: openshift/release#57844

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 15, 2024
@openshift-ci openshift-ci bot requested review from kevinrizza and oceanc80 October 15, 2024 11:39
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 15, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: perdasilva

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 Oct 15, 2024
@perdasilva perdasilva changed the title [WIP] Add cluster-olm-operator to payload by default [WIP] Update manifest annotations for GA Oct 18, 2024
@perdasilva perdasilva changed the title [WIP] Update manifest annotations for GA [HOLD] Update manifest annotations for GA Oct 18, 2024
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 18, 2024
@perdasilva perdasilva changed the title [HOLD] Update manifest annotations for GA [HOLD] OPRUN-3401, OPRUN-3588: Update manifest annotations for GA Oct 21, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 21, 2024

@perdasilva: This pull request references OPRUN-3401 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

This pull request references OPRUN-3588 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to this:

Preconditions:

  • openshift/api#2066 merged
  • catalogd and o-c APIs promoted to v1 and downsync'ed
  • cluster-olm-operator has been updated to use openshift/api/operator/v1 OLM resource
  • OPRUN-3576 done
  • OPRUN-3589 done (outcome may require changes to this PR)

Changes:

  • removes TechPreview annotation
  • adds cluster profile annotations to all manifests
  • adds OLM v1 cluster capability annotation to all manifests

Next PR: openshift/release#57844

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 21, 2024
@perdasilva
Copy link
Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 30, 2024
@perdasilva
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 30, 2024

@perdasilva: This pull request references OPRUN-3401 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

This pull request references OPRUN-3588 which is a valid jira issue.

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

@perdasilva
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 30, 2024

@perdasilva: This pull request references OPRUN-3401 which is a valid jira issue.

This pull request references OPRUN-3588 which is a valid jira issue.

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

@perdasilva
Copy link
Author

/hold don't merge

@LalatenduMohanty
Copy link
Member

@perdasilva We should not remove tech-preview yet. We should add the annotations (including the capability) in this PR and remove the tech-preview stuff in a separate PR.

@perdasilva
Copy link
Author

@perdasilva We should not remove tech-preview yet. We should add the annotations (including the capability) in this PR and remove the tech-preview stuff in a separate PR.

The other capability only PR has been merged =D

@jianzhangbjz
Copy link
Contributor

Hi, I'd like to list the current test status here, the OperatorLifecycleManagerV1 capability has been enabled as default by now, as follows,

jiazha-mac:~ jiazha$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.18.0-0.nightly-2024-11-15-113437   True        False         20m     Cluster version is 4.18.0-0.nightly-2024-11-15-113437
jiazha-mac:~ jiazha$ oc get clusterversion version -o yaml
apiVersion: config.openshift.io/v1
kind: ClusterVersion
...
status:
  availableUpdates: null
  capabilities:
    enabledCapabilities:
    - Build
    - CSISnapshot
    - CloudControllerManager
    - CloudCredential
    - Console
    - DeploymentConfig
    - ImageRegistry
    - Ingress
    - Insights
    - MachineAPI
    - NodeTuning
    - OperatorLifecycleManager
    - OperatorLifecycleManagerV1
    - Storage
    - baremetal
    - marketplace
    - openshift-samples
    knownCapabilities:
    - Build
    - CSISnapshot
    - CloudControllerManager
    - CloudCredential
    - Console
    - DeploymentConfig
    - ImageRegistry
    - Ingress
    - Insights
    - MachineAPI
    - NodeTuning
    - OperatorLifecycleManager
    - OperatorLifecycleManagerV1
    - Storage
    - baremetal
    - marketplace
    - openshift-samples

However, the corresponding OLMv1 resources weren't enabled because this PR wasn't merged. Correct me if I'm wrong, thanks!

jiazha-mac:~ jiazha$ oc get clustercatalog
error: the server doesn't have a resource type "clustercatalog"

And, due to conflicts, I couldn't create cluster to test it.
image

And, a bug about the installer config: https://issues.redhat.com/browse/OCPBUGS-44642

Per Goncalves da Silva added 2 commits November 18, 2024 11:36
Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 18, 2024
@grokspawn
Copy link
Contributor

And, a bug about the installer config: https://issues.redhat.com/browse/OCPBUGS-44642

@jianzhangbjz this is being worked as openshift/installer#9196

@jianzhangbjz
Copy link
Contributor

this is being worked as openshift/installer#9196

Ahh, sorry, I missed it.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 19, 2024
@jianzhangbjz
Copy link
Contributor

@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 20, 2024
Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
@perdasilva
Copy link
Author

/hold currently replaces openshift/api dependency with the branch that promotes NewOLM to default - need to revert back to openshift/api before merge

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 20, 2024

@joelanford: This PR was included in a payload test run from openshift/api#2099
trigger 4 job(s) of type blocking for the ci release of OCP 4.18

  • periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.18-e2e-gcp-ovn-upgrade
  • periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/1f932580-a764-11ef-91df-736755db3e6c-0

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 20, 2024

@joelanford: This PR was included in a payload test run from openshift/api#2099
trigger 14 job(s) of type blocking for the nightly release of OCP 4.18

  • periodic-ci-openshift-release-master-ci-4.18-e2e-aws-upgrade-ovn-single-node
  • periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.18-e2e-azure-ovn-upgrade
  • periodic-ci-openshift-release-master-ci-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-rt-upgrade
  • periodic-ci-openshift-hypershift-release-4.18-periodics-e2e-aws-ovn-conformance
  • periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial
  • periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview
  • periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-techpreview-serial
  • periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-upgrade
  • periodic-ci-openshift-release-master-nightly-4.18-fips-payload-scan
  • periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-bm
  • periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-ipv6
  • periodic-ci-openshift-microshift-release-4.18-periodics-e2e-aws-ovn-ocp-conformance
  • periodic-ci-openshift-microshift-release-4.18-periodics-e2e-aws-ovn-ocp-conformance-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8415a6a0-a76d-11ef-8e6a-5e18a0a92929-0

@jianzhangbjz
Copy link
Contributor

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Nov 21, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 21, 2024

@perdasilva: This pull request references OPRUN-3401 which is a valid jira issue.

This pull request references OPRUN-3588 which is a valid jira issue.

In response to this:

Preconditions:

  • openshift/api#2066 merged
  • catalogd and o-c APIs promoted to v1 and downsync'ed
  • cluster-olm-operator has been updated to use openshift/api/operator/v1 OLM resource
  • OPRUN-3576 done
  • OPRUN-3589 done (outcome may require changes to this PR)

Changes:

  • removes TechPreview annotation
  • adds cluster profile annotations to all manifests
  • adds OLM v1 cluster capability annotation to all manifests

Next PR: openshift/release#57844

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 openshift-eng/jira-lifecycle-plugin repository.

@grokspawn
Copy link
Contributor

/label acknowledge-critical-fixes-only
/lgtm

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Nov 21, 2024
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 21, 2024
@joelanford
Copy link
Member

/override ci/prow/openshift-e2e-aws-techpreview

@perdasilva please remove the hold after openshift/api#2099 merges.

Once both openshift/api#2099 and this PR merge, we can follow back up (more leisurely) with a rebase of this repo off of my branch and back onto o/api.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2024

@joelanford: Overrode contexts on behalf of joelanford: ci/prow/openshift-e2e-aws-techpreview

In response to this:

/override ci/prow/openshift-e2e-aws-techpreview

@perdasilva please remove the hold after openshift/api#2099 merges.

Once both openshift/api#2099 and this PR merge, we can follow back up (more leisurely) with a rebase of this repo off of my branch and back onto o/api.

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-sigs/prow repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2024

@perdasilva: 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-sigs/prow repository. I understand the commands that are listed here.

@joelanford
Copy link
Member

openshift/origin#29313 has merged. Proceeding now with a dual merge of this PR and openshift/api#2099

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 21, 2024
@joelanford joelanford changed the title [HOLD] OPRUN-3401, OPRUN-3588: Update manifest annotations for GA OPRUN-3401, OPRUN-3588: Update manifest annotations for GA Nov 21, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit a0cfc8b into openshift:main Nov 21, 2024
6 checks passed
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-cluster-olm-operator
This PR has been included in build ose-cluster-olm-operator-container-v4.19.0-202411212037.p0.ga0cfc8b.assembly.stream.el9.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. 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.

10 participants