-
Bug
-
Resolution: Fixed
-
Normal
-
None
-
None
-
NDS Sprint 4
Step to recreate:
- Log into UI
- Setup a Dataverse stack with the optional dvicat service
- You will be asked to configure 4 volumes as a part of this setup
- After confirming the configuration, expand your new stack and view the service list
- Click "Remove Service" next to Dataverse iRODS iCAT
- The service should be "removed" from the stack (but not the UI)
- The service status should be replaced with the "Add Service" button
- Click on the "Volumes" tab
- Even though we have deleted 1 of the 4 services requiring a volume, all 4 volumes remain "attached" to our stack
This behavior seems incorrect.
At the very least, it is inconsistent with the work being done to resolve NDS-188 unless we expect the UI should be performing this detachment themselves, which seemed rather undesirable.
I will likely need to discuss this workflow with willis8 about to discover any necessary changes to the API server.