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

OSASINFRA-3652: openstack-cinder: Use new --with-topology flag #345

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

stephenfin
Copy link
Contributor

@stephenfin stephenfin commented Dec 10, 2024

Rather than relying on the soon-to-be-removed feature gate.

/hold

This requires kubernetes/cloud-provider-openstack#2743

EDIT: This is now available on the release-4.18 and release-4.19 branches openshift/cloud-provider-openstack@6cb478d

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

openshift-ci-robot commented Dec 10, 2024

@stephenfin: This pull request references OSASINFRA-3652 which is a valid jira issue.

In response to this:

Rather than relying on the soon-to-be-removed feature gate.

/hold

This requires kubernetes/cloud-provider-openstack#2743

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 openshift-ci bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Dec 10, 2024
Copy link
Contributor

openshift-ci bot commented Dec 10, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@stephenfin stephenfin marked this pull request as ready for review March 10, 2025 09:17
@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 Mar 10, 2025
@openshift-ci openshift-ci bot requested review from EmilienM and mpatlasov March 10, 2025 09:18
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 10, 2025

@stephenfin: This pull request references OSASINFRA-3652 which is a valid jira issue.

In response to this:

Rather than relying on the soon-to-be-removed feature gate.

/hold

This requires kubernetes/cloud-provider-openstack#2743

This is now available on the release-4.18 and release-4.19 branches openshift/cloud-provider-openstack@6cb478d

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

openshift-ci-robot commented Mar 10, 2025

@stephenfin: This pull request references OSASINFRA-3652 which is a valid jira issue.

In response to this:

Rather than relying on the soon-to-be-removed feature gate.

/hold

This requires kubernetes/cloud-provider-openstack#2743

EDIT: This is now available on the release-4.18 and release-4.19 branches openshift/cloud-provider-openstack@6cb478d

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

/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 Mar 10, 2025
@mdbooth
Copy link

mdbooth commented Mar 10, 2025

This changes a command line argument to the provisioner from:

        - --feature-gates=Topology=$(ENABLE_TOPOLOGY)

to

        - --feature-gates=Topology=true
        - --with-topology=$(ENABLE_TOPOLOGY)

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?

@stephenfin
Copy link
Contributor Author

This changes a command line argument to the provisioner from:

        - --feature-gates=Topology=$(ENABLE_TOPOLOGY)

to

        - --feature-gates=Topology=true
        - --with-topology=$(ENABLE_TOPOLOGY)

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 true. I will push a follow-up commit to remove this option shortly.

@mdbooth
Copy link

mdbooth commented Mar 10, 2025

Thanks for the explanation.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 10, 2025
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 10, 2025
@stephenfin
Copy link
Contributor Author

/retest

1 similar comment
@stephenfin
Copy link
Contributor Author

/retest

@stephenfin
Copy link
Contributor Author

/test e2e-openstack

Copy link
Contributor

openshift-ci bot commented Mar 12, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: stephenfin
Once this PR has been reviewed and has the lgtm label, please assign jsafrane for approval. For more information see the Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@stephenfin
Copy link
Contributor Author

/retest

@stephenfin
Copy link
Contributor Author

/test e2e-openstack

Copy link

@mdbooth mdbooth left a 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:

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: []
Copy link

Choose a reason for hiding this comment

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

nit: omit this?.

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 is auto-generated (and generated from scratch each time rather than updated) so I'm thinking I can't.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 20, 2025
@rlobillo
Copy link

rlobillo commented Mar 20, 2025

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Mar 20, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 20, 2025

@stephenfin: This pull request references OSASINFRA-3652 which is a valid jira issue.

In response to this:

Rather than relying on the soon-to-be-removed feature gate.

/hold

This requires kubernetes/cloud-provider-openstack#2743

EDIT: This is now available on the release-4.18 and release-4.19 branches openshift/cloud-provider-openstack@6cb478d

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

/hold

While we investigate a potential QE failure.

@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 Mar 21, 2025
Rather than relying on the soon-to-be-removed feature gate.

Signed-off-by: Stephen Finucane <[email protected]>
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 24, 2025
Copy link
Contributor

openshift-ci bot commented Mar 24, 2025

New changes are detected. LGTM label has been removed.

Copy link
Contributor

openshift-ci bot commented Mar 24, 2025

@stephenfin: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/hypershift-e2e-aks 53ee18f link true /test hypershift-e2e-aks
ci/prow/okd-scos-e2e-aws-ovn 53ee18f link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-openstack-cinder-csi 53ee18f link true /test e2e-openstack-cinder-csi
ci/prow/e2e-openstack 53ee18f link false /test e2e-openstack

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants