-
Bug
-
Resolution: Done
-
Normal
-
None
-
rhos-16.2.z
-
None
Description of problem:
The customer has a large productive cluster and implemented his own backup solution.
For this he constantly boots containers in his tenant(s), which then automatedly attach a volume and push backup data to it. Then the container self destroys and volume gets detached.
The next container boots and pushes his data to the volume and so on.
So a selected set of volumes are attached/detached dozens of times per day.
The volume acts as a vessel for multiple backup jobs and gets passed around regularly.
The customer is encountering errors during volume attachment, specifically the Invalid volume: volume XXX already attached error. This indicates that the volume, despite being detached in theory, is still perceived as attached by the system, preventing new attachments.
Version-Release number of selected component (if applicable):
RHOSP 16.2
Actual results:
- The operations are not working as expected.
Expected results:
- This should work seamlessly.
- external trackers