Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ocf:Filesystem resource looses "block device" settings after re-opening session #63

Open
swplotner opened this issue Jul 12, 2017 · 0 comments

Comments

@swplotner
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant