DFBUGS-7422: Enable Namespacestore dropdown for Vector BucketClass creation

[Soundarya189r]

Description

The Namespacestore dropdown was disabled if Vector type selected and no nsfs present, Removed that check to enable create NamespaceStore option

---

Change Type

Please select all applicable options:

• Feature
• [✅ ] Bug Fix
• Improvement
• Refactor
• Tests

---

Component / Area Impacted

Please select all applicable options:

• [✅ ] ODF
• FDF
• Client
• MCO
• Fusion Access (SAN Storage)
• CNSA (Remote Mount)
• E2E Test

---

Screenshots / Recordings

Recordings / Demo Videos

Screen.Recording.2026-07-29.at.19.50.20.mov

---

Testing

Please select the type of tests included:

• [✅ ] Unit Tests
• E2E Tests
• No Tests Required (with justification below)

Tested by Creating a BucketClass of Vector type

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• packages/odf/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@Soundarya189r: This pull request references [Jira Issue DFBUGS-7422](https://redhat.atlassian.net/browse/DFBUGS-7422), which is valid. The bug has been moved to the POST state.

2 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (srozen@redhat.com), skipping review request.

Details

In response to this:

Description

The Namespacestore dropdown was disabled if Vector type selected and no nsfs present, Removed that check to enable create NamespaceStore option

---

Change Type

Please select all applicable options:

• Feature
• [✅ ] Bug Fix
• Improvement
• Refactor
• Tests

---

Component / Area Impacted

Please select all applicable options:

• [✅ ] ODF
• FDF
• Client
• MCO
• Fusion Access (SAN Storage)
• CNSA (Remote Mount)
• E2E Test

---

Screenshots / Recordings

Recordings / Demo Videos

Screen.Recording.2026-07-29.at.19.50.20.mov

---

Testing

Please select the type of tests included:

• [✅ ] Unit Tests
• E2E Tests
• No Tests Required (with justification below)

Tested by Creating a BucketClass of Vector type

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.

[Soundarya189r]

/jira backport release-4.22

[openshift-ci-robot]

@Soundarya189r: The following backport issues have been created:

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.22

Details

In response to this:

/jira backport release-4.22

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-cherrypick-robot]

@openshift-ci-robot: once the present PR merges, I will cherry-pick it on top of release-4.22 in a new PR and assign it to you.

Details

In response to this:

@Soundarya189r: The following backport issues have been created:

Queuing cherrypicks to the requested branches to be created after this PR merges:
/cherrypick release-4.22

In response to this:

/jira backport release-4.22

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.

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.