In a workflow with two certified commands: remove volume (if exists) and clone volume.
Reservation works fine, I can run multiple times the workflow.
Hovewer if I force data source acquisition from dfm 5.2, cache updated come YES only for clone volume. That means the next workflow failed because remove volume is disabled.
Why remove volume cache is not updated, that break the reservation process. I miss something?
Solved! See The Solution
Could you please look at this post and see if it helps in understanding this behavior:
Oh sorry, I totally miss the post of anil, it's more clear now.
But to solved this behavior, if I need to have remove volume and clone volume in the same workflow, how can i proceed.
Thing is, I want to have a refresh workflow that work in all cases even volume clone doesn't exit. Example, when workflow is executed the first time.
I made some tests based on comments of anil and I remarqued that usage of remove volume and clone volume in separate workflows work fine. Even I acquire from DFM.
In this case that should be possible to make prioritization in reservation? depending on where commands are executed in workflow, from left to right and top to bottom.
I am afraid there is no straight workaround here.
There are two things you could do:
1. Manually remove the reservation for remove volume.
2. Use different volume names.
This is a very tricky situation and we have a lot of conflicting commands that can be put in a workflow.
It is not fixed in 3.0RC1.
Since it is a major fix, we are currently looking at the prospect of fixing it in future release.
Please let me know if you have any questions.
As a workaround to the issue, you can try disabling the following in your workflow setup details (under Setup --> General tab):
1) Consider Reserved Elements and
2) Enable element existence validation
I'am again faced to reservation problem with couple of vol clone and vol rename.
So i decided to totaly disable reservations, because they are not usable for me. It's a shame because that could be very helpfull.
When do you planned to have a look on that, I really need this problem fixed.