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

Patch 1.6.1 #699

Closed
wants to merge 18 commits into from
Closed

Patch 1.6.1 #699

wants to merge 18 commits into from

Conversation

rishabhatdell
Copy link
Contributor

@rishabhatdell rishabhatdell commented Sep 24, 2024

Description

CSM-Operator changes for CSM 1.11.1

GitHub Issues

List the GitHub issues impacted by this PR:

GitHub Issue #
dell/csm#1478
dell/csm#1482

Checklist:

  • I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
  • I have verified that new and existing unit tests pass locally with my changes
  • I have not allowed coverage numbers to degenerate
  • I have maintained at least 90% code coverage
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • I have maintained backward compatibility

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

  • Installed csm-operator successfully
  • ran all unit tests
  • installed csi-unity, csi-powerstore and csi-powerflex using latest samples
  • ran cert-csi for all the installed drivers

ChristianAtDell and others added 2 commits September 25, 2024 15:46
* Add Powerscale port variable

* Template auth variables

* Update go files

* Add Powerscale port variable handling

* Fix scenarios for PowerScale

* Update powerscale template files
Copy link
Contributor

@francis-nijay francis-nijay left a 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

@francis-nijay
Copy link
Contributor

francis-nijay commented Sep 26, 2024

We need to make sure all yams that has changes work without errors. Is e2e run successful?

Comment on lines -296 to -312
---
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
Copy link
Contributor

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

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

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

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

Copy link
Contributor

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

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

Copy link
Contributor

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

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?

Copy link
Contributor

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

@JacobGros JacobGros Sep 26, 2024

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"

@JacobGros
Copy link
Contributor

Call was made today to not include yaml lint fixes in1.6.1,
Opened this PR: #709 but kept this branch the same in case we ever need to revisit

@mjsdell mjsdell deleted the patch-1.6.1 branch October 17, 2024 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.