Created attachment 1415730 [details] heketi_logs
Created attachment 1415731 [details] topology info
Let me say, this is is actually good behavior. We could have a nicer error message. But it is correct to not proceed with node removal while the volume delete is operating on the node. Also thanks for confirming that the db stayed consistent. Not sure what to make out of this BZ: Is it a request for a better error message? Or to block the CLI until the volume delete is done and only afterwards remove the node?
(In reply to Michael Adam from comment #5) > Let me say, this is is actually good behavior. > We could have a nicer error message. > But it is correct to not proceed with node removal while the volume delete > is operating on the node. The expectation from this bug is to have a seamless node removal operation. I believe the error seen is due to the fact that the brick replace operation has failed as the existing brick is already deleted as part of volume delete. It would be great if this is handled gracefully by the node removal process. > > Also thanks for confirming that the db stayed consistent. > > Not sure what to make out of this BZ: > Is it a request for a better error message? > Or to block the CLI until the volume delete is done and only afterwards > remove the node? As mentioned above, the expectation from this bug is to handle the node removal process gracefully. We cannot fail Node removal each time a volume delete operation is run which involves node remove. With scale, admin will have to run the node removal command several times which kills the uer experience.