Hi team, here's a new case.
Problem Symptom
When starting services for a node in a converged storage pool on DeviceManager, an error is reported, indicating that the node already exists in the cluster.
Problem Diagnosis
On the Task Center page, check whether the service startup task fails.
If yes, delete the service cluster and try again.
Causes
When starting services for a converged storage pool, processes in the EDS service cluster are started. After such processes are started successfully, the service cluster is automatically created.
After the service cluster is created, there are other subsequent steps to be processed, such as notifying the EDS module to create a storage pool object. If a subsequent step fails, the created service cluster cannot be rolled back. Therefore, you need to run a command to delete the service cluster. After the deletion, try to start services for the storage pool again.
Solution
Check the ID of the converged storage pool that fails to be started.
After confirmation, log in to the management node and run the /OSM/script/ismcli -u admin command. This command requires you to enter the password of user admin (if user admin does not exist, use the user for logging in to DeviceManager). Then, run the delete converged_eds_service general storage_pool_id=XXX command to delete the service cluster.
After the command is executed, check whether the deletion task is complete on the Task Center page of DeviceManager. If yes, start the services again.
If the deletion task fails to complete after you run the command for multiple times, contact technical support engineers.
Check After Recovery
Services are successfully started for the converged storage pool.
Applicable Versions
OceanStor Pacific series 8.1.0; OceanStor Atlantic series 8.1.0
