You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Input elements accidently change current settings:
If a value in a combobox field does not exist in the dropdown options, lcmc changes is to the first element of the option list.
Example resource agent ocf:Filesystem:
My setting for "block device" is the lvm volume /dev/vgdrbd1/lxc1
Devices in this volumegroup are not listed in the combobox. When restarting lcmc, the "block device" settings of all my filesystem resources are changed to the first entry in the list (which is DRBD: drbd1/0 in my case). If I am not aware of this and press "apply", these wrong settings are applied. I have to press "revert" for all resources first on every lcmc start to get my current values.
lcmc doesn't seem to distinguish betweeen "0" and "nothing selected". In the input field for
"host location" my setting "0" is alwys changed to "(nothing selected)".
Cluster: Debian jessie with backports. Client: LXC 1.7.13. OS Windows 8, OSX. Java 1.8.0_111_b14)
Anway, thx for the helpful software.
The text was updated successfully, but these errors were encountered:
Input elements accidently change current settings:
Example resource agent ocf:Filesystem:
My setting for "block device" is the lvm volume /dev/vgdrbd1/lxc1
Devices in this volumegroup are not listed in the combobox. When restarting lcmc, the "block device" settings of all my filesystem resources are changed to the first entry in the list (which is DRBD: drbd1/0 in my case). If I am not aware of this and press "apply", these wrong settings are applied. I have to press "revert" for all resources first on every lcmc start to get my current values.
"host location" my setting "0" is alwys changed to "(nothing selected)".
Cluster: Debian jessie with backports. Client: LXC 1.7.13. OS Windows 8, OSX. Java 1.8.0_111_b14)
Anway, thx for the helpful software.
The text was updated successfully, but these errors were encountered: