Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-7321

Request to add a Warning mechanism when deleting MachinePools with running nodes

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Node
    • None
    • Future Sustainability
    • None
    • False
    • Hide

      None

      Show
      None
    • Red Hat OpenShift Service on AWS
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. Proposed title of this feature request

      Warning mechanism when deleting a machinePool with running nodes
      **

       

      2. What is the nature and description of the request?

      Customer would like to add a WARNING or prevention mechanism when deleting a MachinePool using the rosa CLI command: rosa delete machinepool   in case the MachinePool has running nodes or the node count is different than 0

       

      3. Why does the customer need this? (List the business requirements here)

      The current MachinePool deletion command deletes the MachinePool even if there are nodes in them and there is no way to stop the process. 

      In case of accidental/wrong MachinePool change, there is no way to stop/revert the process of a MachinePool deletion and all the nodes in it will be affected.  The customer mentions that it would be better if there was a flag preventing the deletion of the MachinePool if the nodes still exist on the MachinePool

       

      I informed the customer that the rosa delete MachinePool command already has a confirmation message:

      $ rosa delete machinepool test-machine-pool -c 7a8d6c7f-7214-4742-8fe2-9532b84e81da
      ? Are you sure you want to delete machine pool 'test-machine-pool' on cluster '7a8d6c7f-7214-4742-8fe2-9532b84e81da'? (y/N) Yes <====
      ...
      I: Successfully deleted machine pool 'test-machine-pool' from cluster '7a8d6c7f-7214-4742-8fe2-9532b84e81da'

      But he mentions that during CLI operations, their commands include the --yes flag, as they need to delete multiple MachinePools, since they need to create one MachinePool per Availability zone every time.

      rosa -c <clustername> delete machinepool <machinepool> --yes

      In these cases, a yes/no approval does not check for MachinePool deletion impact. Instead a warning on nodes still existing in the MachinePool might be a better alert/indicator than a simple yes or no.

      I already suggested the customer to remove the --yes flag from the rosa -c <clustername> delete machinepool, but he insisted on an RFE to include this feature.

      4. List any affected packages or components.

      rosa CLI tool

      MachinePools

              gausingh@redhat.com Gaurav Singh
              rhn-support-oariasol Omar Arias Olave
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                None
                None