On Tue, Oct 10, 2017 at 2:57 PM, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Tue, Oct 10, 2017 at 1:29 PM, Yaniv Kaul <ykaul@redhat.com> wrote:


On Oct 6, 2017 2:41 PM, "Gianluca Cecchi" <gianluca.cecchi@gmail.com> wrote:
Hello,
I'm relocating some disks from some storage domains to other ones.
At the end I'm going to remove source storage domains.
All the SD involved are FC and the hosts are CentOS 7.4
I see that after removing an SD from oVirt, the multipath part on host remains.
What is the correct sequence of operations to do at hosts' side after completing the Webadmin Gui part?


(which seems to be similar to your steps below. I'd remove it from the storage side after flushing though). 
Y. 


Yes, when removing from physical servers I took that link as reference and my steps reproduce them in practice.
I have not understood what do you mean with

"
 I'd remove it from the storage side after flushing though
" 

Do yo mean this sequence:
1) flush the single path devices
2) remove the multipath device with multipath -f
??
O another thing?

As soon as you are done flushing IO, I'd remove the device (unzone). The reason is that you do not want it to be re-discovered.
Y.
 

Also I found in the mean time this bugzilla (for RHEV)
where you replied and have work in progress... thanks!

I also found a reference (I miss the bugzilla id right now), that if you have vdsm > of a certain version there are "no problems" on hosts in case some unused (from oVirt point of view) LUNs are removed from storage array while the hosts still enumerating them in their multipath listing. So that this can lower potential problems...
I don't now if the enhancement s related to some sort of blacklisting or what has been done at vdsm level....

Gianluca