It appears that LCMC with 1.7.13 (possibly earlier too, not verified), the ocf:Filesystem resource object looses the setting of /dev/vg_rdm_0/lv_lms2_db (our example value) and reverts it to /dev/sda2.
When I see it and realize it, I have to choose the "Rev..." button - so that's the work around - every time I open a session with LCMC to a cluster, I will have to click on each Filesystem resource and click on "Rev..." which changes the "block device" value from /dev/sda2 to whatever the actual desired setting was (even so there were no changes made and in theory the "Rev.." option should not be even available at that time). The block device value also shows up in purple when initially opening the session. I assume that means the value was modified.
I think this might be a bug. The LCMC tool has been live safer in terms of building the cib.xml files for the pacemaker cluster. Thank you.
It appears that LCMC with 1.7.13 (possibly earlier too, not verified), the ocf:Filesystem resource object looses the setting of /dev/vg_rdm_0/lv_lms2_db (our example value) and reverts it to /dev/sda2.
When I see it and realize it, I have to choose the "Rev..." button - so that's the work around - every time I open a session with LCMC to a cluster, I will have to click on each Filesystem resource and click on "Rev..." which changes the "block device" value from /dev/sda2 to whatever the actual desired setting was (even so there were no changes made and in theory the "Rev.." option should not be even available at that time). The block device value also shows up in purple when initially opening the session. I assume that means the value was modified.
I think this might be a bug. The LCMC tool has been live safer in terms of building the cib.xml files for the pacemaker cluster. Thank you.
Steffen