Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WINC-803: Update correct WMCO subscription info #1044

Merged
merged 1 commit into from May 4, 2022

Conversation

selansen
Copy link
Contributor

@selansen selansen commented Apr 30, 2022

This commit aims to address WINC-803 issue. We need to update
OpenShift Container Platform for Windows Containers subscription
as subscription info to be in sync with rlease and support docs.

Signed-off-by: selansen esiva@redhat.com

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 30, 2022
@selansen
Copy link
Contributor Author

/approve cancel

@openshift-ci openshift-ci bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 30, 2022
Usage of this operator requires a Red Hat OpenShift subscription. Users looking to deploy Windows containers workloads in
production clusters should acquire a subscription before attempting to install this operator. Users without a subscription
can try the community operator, a distribution which lacks official support.
Usage of this operator requires a OpenShift Container Platform for Windows Containers subscription. Users looking to
Copy link
Contributor

Choose a reason for hiding this comment

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

a OpenShift -> an OpenShift

@@ -27,12 +27,13 @@ spec:
or by specifying existing instances through a [ConfigMap](https://docs.openshift.com/container-platform/latest/windows_containers/configuring-byoh-windows-instance.html)
Copy link
Contributor

Choose a reason for hiding this comment

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

@selansen , You may need to run make bundle to reflect the changes in the bundle.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

why do I need to run make bundle? Looked into previous changes in the same file, haven't noticed anyone ran make bundle for this file change. Am I missing anything?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I am not creating any bundle image.

Copy link
Contributor

Choose a reason for hiding this comment

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

why do I need to run make bundle? Looked into previous changes in the same file, haven't noticed anyone ran make bundle for this file change. Am I missing anything?

make bundle will apply the changes in the bundle CSV, here. Otherwise won't take effect.

For references, you can take a look at #780.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This will be done as part of release prep, right? I am not seeing previous commits in CSV that had run make bundle. That's why I am confused if I have to do it for this PR or should we do it as part of release prep?

Copy link
Contributor

Choose a reason for hiding this comment

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

This will be done as part of release prep, right?

Yes, and running make bundle now will apply the changes in the bundle CSV.

@selansen selansen force-pushed the winc_803 branch 2 times, most recently from 48dc535 to 671f01b Compare May 2, 2022 22:11
@@ -11,9 +11,8 @@ metadata:
olm.skipRange: '>=4.0.0 <5.0.0'
Copy link
Contributor

Choose a reason for hiding this comment

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

PR title should be prefixed with the Jira id (WINC-803).

Also, there is a typo in the commit message: s/rlease/release

Copy link
Contributor

Choose a reason for hiding this comment

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

I suggest using [bundle] as the sub-component in the first line of the commit

- entrypoint:
- scorecard-test
- olm-bundle-validation
image: quay.io/operator-framework/scorecard-test:v1.5.0
labels:
suite: olm
test: olm-bundle-validation-test
storage:
Copy link
Contributor

Choose a reason for hiding this comment

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

@selansen These changes are not related and should be reverted.

@@ -11,8 +11,7 @@ metadata:
olm.skipRange: '>=4.0.0 <5.0.0'
operatorframework.io/cluster-monitoring: "true"
operatorframework.io/suggested-namespace: openshift-windows-machine-config-operator
operators.openshift.io/valid-subscription: '["Red Hat OpenShift support for Windows
Containers"]'
Copy link
Contributor

Choose a reason for hiding this comment

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

Revert

@@ -189,11 +197,3 @@ rules:
- securitycontextconstraints
verbs:
- use
- apiGroups:
Copy link
Contributor

Choose a reason for hiding this comment

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

Revert

@selansen selansen changed the title [config] Update correct WMCO subscription info WINC-803: Update correct WMCO subscription info May 4, 2022
@selansen
Copy link
Contributor Author

selansen commented May 4, 2022

$ operator-sdk version
operator-sdk version: "v1.15.0", commit: "f6326e832a8a5e5453d0ad25e86714a0de2c0fc8", kubernetes version: "1.21", go version: "go1.16.10", GOOS: "linux", GOARCH: "amd64"

@selansen selansen force-pushed the winc_803 branch 4 times, most recently from 4101287 to 7d0eb14 Compare May 4, 2022 17:17

### Pre-requisites
* A Red Hat OpenShift subscription
* A Red Hat OpenShift Container Platform for Windows Containers subscription
Copy link
Contributor

Choose a reason for hiding this comment

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

Would it help to add a link to the support page here: https://access.redhat.com/support/policy/updates/openshift#windows

@sebsoto
Copy link
Contributor

sebsoto commented May 4, 2022

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 4, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sebsoto

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 May 4, 2022
 This commit aims to address WINC-803 issue. We need to update
 OpenShift Container Platform for Windows Containers subscription
 as subscription info to be in sync with release and support docs.

Signed-off-by: selansen <esiva@redhat.com>
@selansen selansen merged commit f409122 into openshift:master May 4, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 4, 2022

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

@selansen
Copy link
Contributor Author

selansen commented May 4, 2022

/cherry-pick release-4.10

@selansen
Copy link
Contributor Author

selansen commented May 4, 2022

/cherry-pick community-4.10

@openshift-cherrypick-robot

@selansen: new pull request created: #1053

In response to this:

/cherry-pick release-4.10

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

@selansen: #1044 failed to apply on top of branch "community-4.10":

Applying: Update correct WMCO subscription info
Using index info to reconstruct a base tree...
M	bundle/manifests/windows-machine-config-operator.clusterserviceversion.yaml
M	config/manifests/bases/windows-machine-config-operator.clusterserviceversion.yaml
Falling back to patching base and 3-way merge...
Auto-merging config/manifests/bases/windows-machine-config-operator.clusterserviceversion.yaml
Auto-merging bundle/manifests/windows-machine-config-operator.clusterserviceversion.yaml
CONFLICT (content): Merge conflict in bundle/manifests/windows-machine-config-operator.clusterserviceversion.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Update correct WMCO subscription info
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick community-4.10

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.

@selansen
Copy link
Contributor Author

selansen commented May 4, 2022

/cherry-pick release-4.9

@openshift-cherrypick-robot

@selansen: #1044 failed to apply on top of branch "release-4.9":

Applying: Update correct WMCO subscription info
Using index info to reconstruct a base tree...
M	bundle/manifests/windows-machine-config-operator.clusterserviceversion.yaml
M	config/manifests/bases/windows-machine-config-operator.clusterserviceversion.yaml
M	config/rbac/role.yaml
Falling back to patching base and 3-way merge...
Auto-merging config/rbac/role.yaml
Auto-merging config/manifests/bases/windows-machine-config-operator.clusterserviceversion.yaml
CONFLICT (content): Merge conflict in config/manifests/bases/windows-machine-config-operator.clusterserviceversion.yaml
Auto-merging bundle/manifests/windows-machine-config-operator.clusterserviceversion.yaml
CONFLICT (content): Merge conflict in bundle/manifests/windows-machine-config-operator.clusterserviceversion.yaml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Update correct WMCO subscription info
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick 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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants