Skip to content

added forceful deployment option#2602

Open
gourhari1 wants to merge 1 commit intored-hat-storage:masterfrom
gourhari1:RHSTOR-8584/Add-Forceful-deployment-option-in-the-storage-cluster-creation-UI
Open

added forceful deployment option#2602
gourhari1 wants to merge 1 commit intored-hat-storage:masterfrom
gourhari1:RHSTOR-8584/Add-Forceful-deployment-option-in-the-storage-cluster-creation-UI

Conversation

@gourhari1
Copy link
Contributor

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 26, 2026

Hi @gourhari1. Thanks for your PR.

I'm waiting for a red-hat-storage member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

@gourhari1
Copy link
Contributor Author

gourhari1 commented Feb 26, 2026

image image image

Comment on lines +591 to +595
if (enableForcefulDeployment) {
requestData.spec.forcefulDeployment = {
enabled: enableForcefulDeployment,
};
}
Copy link
Collaborator

Choose a reason for hiding this comment

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

can plz u paste some reference where it says that this is the correct field that we need to add for this use case ??

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have recitified it with required change after discussing with backend owner.

Image

@SanjalKatiyar
Copy link
Collaborator

/ok-to-test

@gourhari1 gourhari1 force-pushed the RHSTOR-8584/Add-Forceful-deployment-option-in-the-storage-cluster-creation-UI branch from a4fd979 to 40f6dcd Compare March 2, 2026 07:26
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 2, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: gourhari1
Once this PR has been reviewed and has the lgtm label, please ask for approval from sanjalkatiyar. 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:

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

@gourhari1 gourhari1 force-pushed the RHSTOR-8584/Add-Forceful-deployment-option-in-the-storage-cluster-creation-UI branch 3 times, most recently from 10eb5c4 to e0901d7 Compare March 2, 2026 07:57
"Out of {{capacity}}": "Out of {{capacity}}",
"Over the past {{daysUp}} ": "Over the past {{daysUp}} ",
"Overall image health": "Overall image health",
"Override and completely wipe any data on disks used to create this storage system": "Override and completely wipe any data on disks used to create this storage system",
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
"Override and completely wipe any data on disks used to create this storage system": "Override and completely wipe any data on disks used to create this storage system",
"Override and completely wipe any data on disks used to create this storage cluster": "Override and completely wipe any data on disks used to create this storage system",

Comment on lines +591 to +595
if (enableForcefulDeployment) {
requestData.spec.managedResources.cephCluster.cleanupPolicy = {
wipeDevicesFromOtherClusters: enableForcefulDeployment,
};
}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is this tested ? didn't u get any error ?

requestData.spec.managedResources.cephCluster is undefined, u should have gotten error when accessing requestData.spec.managedResources.cephCluster.cleanupPolicy.

@SanjalKatiyar
Copy link
Collaborator

plz add the latest screenshot as well...

Comment on lines +591 to +595
if (enableForcefulDeployment) {
requestData.spec.managedResources.cephCluster.cleanupPolicy = {
wipeDevicesFromOtherClusters: enableForcefulDeployment,
};
}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
if (enableForcefulDeployment) {
requestData.spec.managedResources.cephCluster.cleanupPolicy = {
wipeDevicesFromOtherClusters: enableForcefulDeployment,
};
}
if (enableForcefulDeployment) {
requestData.spec.managedResources = {
...requestData.spec.managedResources,
cephCluster: { wipeDevicesFromOtherClusters: true },
},
};

};
}
// Add forceful deployment configuration if enabled
if (enableForcefulDeployment) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

nits:

Suggested change
if (enableForcefulDeployment) {
if (isNoProvisioner && enableForcefulDeployment) {

@gourhari1 gourhari1 force-pushed the RHSTOR-8584/Add-Forceful-deployment-option-in-the-storage-cluster-creation-UI branch from e0901d7 to be21c1b Compare March 3, 2026 12:22
// Add forceful deployment configuration if enabled
if (isNoProvisioner && enableForcefulDeployment) {
requestData.spec.managedResources.cephCluster = {
...requestData.spec.managedResources.cephCluster,
Copy link
Collaborator

Choose a reason for hiding this comment

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

again, did u test this flow by creating a storage cluster ?

did u not get any error like cannot read property undefined while destruct ??

as mentioned earlier, requestData.spec.managedResources.cephCluster is undefined, right ?

Copy link
Collaborator

Choose a reason for hiding this comment

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

@gourhari1 gourhari1 force-pushed the RHSTOR-8584/Add-Forceful-deployment-option-in-the-storage-cluster-creation-UI branch 2 times, most recently from 8610d33 to 88614f9 Compare March 9, 2026 08:56
Comment on lines +600 to +602
requestData.spec.managedResources.cephCluster = {
...(requestData.spec.managedResources
.cephCluster as ManagedResourcesCephClusterKind),
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
requestData.spec.managedResources.cephCluster = {
...(requestData.spec.managedResources
.cephCluster as ManagedResourcesCephClusterKind),
requestData.spec.managedResources.cephCluster = {
...(requestData.spec.managedResources
.cephCluster || ({} as ManagedResourcesCephClusterKind)),

@gourhari1 gourhari1 force-pushed the RHSTOR-8584/Add-Forceful-deployment-option-in-the-storage-cluster-creation-UI branch 2 times, most recently from 7a5305a to 1b4d48c Compare March 10, 2026 11:58
// The Next button is disabled when forceful deployment is enabled but confirmation text not equals confirm
const hasForcefulDeploymentButNoConfirmation =
enableForcefulDeployment &&
!(forcefulDeploymentConfirmation?.trim().toLowerCase() === 'confirm');
Copy link
Contributor

Choose a reason for hiding this comment

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

Please keep this as upper case validation as if user writes it lower case we might want to stop it since the placeholder is all caps.

@gourhari1 gourhari1 force-pushed the RHSTOR-8584/Add-Forceful-deployment-option-in-the-storage-cluster-creation-UI branch from 1b4d48c to 1846bd9 Compare March 11, 2026 04:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants