-
Notifications
You must be signed in to change notification settings - Fork 6
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
Patch 1.6.1 #699
Patch 1.6.1 #699
Conversation
…elease branch (#669) Signed-off-by: shefali-malhotra <kalrashefali10@gmail.com>
* Add Powerscale port variable * Template auth variables * Update go files * Add Powerscale port variable handling * Fix scenarios for PowerScale * Update powerscale template files
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are multiple yaml lint errors that needs to be fixed
We need to make sure all yams that has changes work without errors. Is e2e run successful? |
* Fix pmaxCreds not set correctly in e2e * Update scenarios.yaml
--- | ||
apiVersion: v1 | ||
kind: ConfigMap | ||
metadata: | ||
name: isilon-config-params | ||
namespace: isilon | ||
data: | ||
driver-config-params.yaml: | | ||
CSI_LOG_LEVEL: "debug" | ||
CSI_LOG_FORMAT: "TEXT" | ||
PODMON_CONTROLLER_LOG_LEVEL: "debug" | ||
PODMON_CONTROLLER_LOG_FORMAT: "TEXT" | ||
PODMON_NODE_LOG_LEVEL: "debug" | ||
PODMON_NODE_LOG_FORMAT: "TEXT" | ||
spec: | ||
driver: | ||
configVersion: v2.11.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we removing this configmap? What did it do that was wrong? What does removing it unblock?
@@ -1,488 +1,488 @@ | |||
apiVersion: storage.dell.com/v1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What happened to this file, why is it being shown as every line removed and re-added? I can't see a difference between the two versions.
@@ -1,488 +1,488 @@ | |||
apiVersion: storage.dell.com/v1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is another 500 line difference; what did this change encompass?
This PR is so large that it is crashing my browser trying to go through the diffs. If all of this is a result of YAML linting, then we should have rolled out those changes incrementally, shouldn't we?
namespace: placeholder | ||
spec: | ||
apiservicedefinitions: {} | ||
customresourcedefinitions: | ||
owned: | ||
- description: ApexConnectivityClient is the Schema for the ApexConnectivityClient |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For everything below line1469:
Why were these changes made? What was the yaml lint error? It looks like these sections were removed and added back w/ no changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh I see, the indentation went up a level
endpointPort: "REPLACE_PORT" | ||
endpointPort: REPLACE_AUTH_PORT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here we have it as REPLACE_AUTH_PORT with no quotation...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thought quotations was causing issues but it doesn't. With or without quotes it works but it was last verified without.
endpointPort: 8080 | ||
endpointPort: "REPLACE_PORT" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
... and here we have it inside quotation marks. Does it matter that it's in quotes sometimes and not in quotes others?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't matter. Tested with and without, both approaches worked but it was last tested with quotes in this scenario.
@@ -15,4 +15,4 @@ annotations: | |||
operators.operatorframework.io.test.config.v1: tests/scorecard/ | |||
|
|||
# Annotations to specify supported OCP versions. | |||
com.redhat.openshift.versions: v4.15-v4.16 | |||
com.redhat.openshift.versions: "v4.15" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Main branch has:
com.redhat.openshift.versions: "v4.16-v4.17"
operator 1.6.0 has
com.redhat.openshift.versions: v4.15-v4.16
Are we dropping 4.16 for the patch only? If this is due to yaml lint fix, we probably want to put the range in quotes rather than get rid of 4.16
com.redhat.openshift.versions: "v4.16-v4.17" |
Call was made today to not include yaml lint fixes in1.6.1, |
Description
CSM-Operator changes for CSM 1.11.1
GitHub Issues
List the GitHub issues impacted by this PR:
Checklist:
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration