-
Notifications
You must be signed in to change notification settings - Fork 40
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
OSASINFRA-3652: openstack-cinder: Use new --with-topology flag #345
base: main
Are you sure you want to change the base?
Conversation
@stephenfin: This pull request references OSASINFRA-3652 which is a valid jira issue. In response to this:
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. |
Skipping CI for Draft Pull Request. |
3db5d09
to
f051ebe
Compare
@stephenfin: This pull request references OSASINFRA-3652 which is a valid jira issue. In response to this:
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. |
@stephenfin: This pull request references OSASINFRA-3652 which is a valid jira issue. In response to this:
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. |
/hold cancel |
This changes a command line argument to the provisioner from:
to
So we're now enabling the feature gate unconditionally, but disabling it when ENABLE_TOPOLOGY is false. Why do we enable it when ENABLE_TOPOLOGY is false? Does it do anything else? Or is it just for simpler templating? |
We were previously relying on the feature gate to enable/disable the feature, but that feature gate is planned for removal in a future release. As a result, we've added a new boolean option to enable/disable the feature, which we can use in place of the feature gate. The reason I kept the feature gate flag was because I didn't know whether this defaulted to enabled or disabled, however, your comment was enough for me to go investigate, and it seems this defaults to |
Thanks for the explanation. /lgtm |
63d5579
to
56eb54b
Compare
/retest |
1 similar comment
/retest |
/test e2e-openstack |
56eb54b
to
574f975
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: stephenfin The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
574f975
to
7a32614
Compare
/retest |
/test e2e-openstack |
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 now keyed from the enable_topology
key in some config map. I'm guessing the configmap is the one produced by configsync from merging these 2 configmaps:
csi-operator/pkg/openstack-cinder/config/configsync.go
Lines 118 to 125 in 608149d
configSources = []configSource{ | |
// First, we try to retrieve from the Cinder CSI-specific config map | |
{util.OpenShiftConfigNamespace, "cinder-csi-config", "config"}, | |
// Failing that, we attempt to retrieve from the cloud provider-specific config map | |
// TODO(stephenfin): We should stop retrieving this once Installer creates the new | |
// config, which will allow us to simplify things somewhat here | |
{util.OpenShiftConfigNamespace, infra.Spec.CloudConfig.Name, infra.Spec.CloudConfig.Key}, | |
} |
It seems we've been using this key for a while, so guessing there's no upgrade or documentation impact here.
By my admittedly limited understand of how we provision this driver this looks fine to me. I have one nit. If it's there for a reason, a comment would be good because it looks weird, but it's not important.
/lgtm
configMapKeyRef: | ||
key: enable_topology | ||
name: cloud-conf | ||
env: [] |
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.
nit: omit this?.
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 auto-generated (and generated from scratch each time rather than updated) so I'm thinking I can't.
According to https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_csi-operator/345/pull-ci-openshift-csi-operator-main-e2e-openstack-cinder-csi/1902504203914317824/artifacts/e2e-openstack-cinder-csi/openshift-e2e-test/build-log.txt, the cinder-csi tests are passing so we are ready to merge it and run full regresion on 4.19 release. /label qe-approved |
@stephenfin: This pull request references OSASINFRA-3652 which is a valid jira issue. In response to this:
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. |
/hold While we investigate a potential QE failure. |
Rather than relying on the soon-to-be-removed feature gate. Signed-off-by: Stephen Finucane <[email protected]>
This defaults to true [1], meaning there is no reason to set it manually. [1] https://github.com/kubernetes-csi/external-provisioner/blob/c7277b7a5181ff6eab89dc9e36390306417471d4/pkg/features/features.go#L63 Signed-off-by: Stephen Finucane <[email protected]>
7a32614
to
53ee18f
Compare
New changes are detected. LGTM label has been removed. |
@stephenfin: The following tests failed, say
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. |
Rather than relying on the soon-to-be-removed feature gate.
/hold
This requires kubernetes/cloud-provider-openstack#2743EDIT: This is now available on the
release-4.18
andrelease-4.19
branches openshift/cloud-provider-openstack@6cb478d