<div dir="ltr">Hi Rasto,<div><br></div><div>I have a relatively large list of issues with the latest LCMC</div><div><br></div><div><br></div><div>1) When I use the Cluster Wizard to create a new cluster and enter a name for it (e.g. "Test") the default name of "Cluster 1" will always be used. Only when I quit LCMC and restart it the cluster will be named "Test" </div>
<div><br></div><div>2) When I start LCMC with an incorrect drbd config (for instance a wrong IP address) i get the following error (which is expected):</div><div><br></div><div><div>drbd config error: drbd.d/r0.res:8: in resource r0, on node01:</div>
<div><span class="" style="white-space:pre"> </span>IP X.X.X.X not found on this host.</div></div><div><br></div><div>But then I would like to edit this IP address in LCMC but the whole config of r0 is not read and is not shown in LCMC so it is not editable either.</div>
<div><br></div><div>3) Under DRBD the "DRBD Processes" button always results in error</div><div><br></div><div>I noticed that LCMC tries to run a proxy command (drbd-proxy-ctl) during this button press so I guess that's the reason for the error:</div>
<div><br></div><div>sudo: clususer :command not allowed ; TTY=pts/7 ; PWD=/home/clususer ; USER=root ; COMMAND=/sbin/drbd-proxy-ctl -c show hconnections -c show hsubconnections -c show memusage -c print statistics<br></div>
<div><div><br></div><div>I don't have DRBD proxy on this machine but I think this should not result in an error.</div><div><br></div><div>4) When I create a VG from a newly created DRBD volume the VG is not visible to LCMC even after a "Rescan LVM"</div>
<div><br></div><div>I have to disconnect / reconnect to the cluster to see the newly created VG and the "Create LV in VG" option. Rescan LVM doesn't seem to work at all.</div><div><br></div><div>5) When creating a VM the "Browse" button for the installation disk is greyed out when running LCMC from Windows (Ubuntu/Linux is working correctly)</div>
<div><br></div><div>6) It would be nice to have "Driver Cache" option while creating a VM in the "Storage" section, the Driver Cache setting is only available in the Installation Disk section.</div><div>
<br></div><div>7) If during the VM creation wizard in the Storage section a Virtio disk is added, LCMC still adds this virtio disk as "hda" in stead of "vda"</div><div><br></div><div>8) When loading the DRBD module through LCMC and I connect a resource i often get an error message on the console saying:</div>
<div><br></div><div><div>Oct 8 16:49:16 node01 kernel: [ 6926.447449] block drbd0: Different verify-alg settings. me="crc32c" peer=""</div></div><div><br></div><div>Although the config was created through LCMC and is equal on both sides.</div>
<div><br></div><div>A "Load Config (Adjust)" resolves the issue but it shouldn't happen in the first place.</div><div><br></div><div>9) I mailed to this list some time ago about the /dev/disk/by-id but i didn't got any response so here is it again:</div>
<div><br></div><div><div style="font-family:arial,sans-serif;font-size:13px">LCMC doesn't recognise the /dev/disk/by-id/.... symlinks for /dev/sdb, sdc etc...</div><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">Example r0.res:</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px"><div>resource r0 {</div>
<div><br></div><div> device /dev/drbd0;</div><div> meta-disk internal;</div><div><br></div><div> on node01 {</div><div> disk /dev/disk/by-id/wwn-0x5000c5000ee51d23;</div><div> address <a href="http://10.0.0.1:7788/" target="_blank">10.0.0.1:7788</a>;</div>
<div> }</div><div> on node02 {</div><div> disk /dev/disk/by-id/wwn-0x5000c5000ee5ceaf;</div><div> address <a href="http://10.0.0.2:7788/" target="_blank">10.0.0.2:7788</a>;</div><div> }</div><div>}</div></div><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">LCMC only shows two green (unused) /dev/sdb fields on both nodes and doesn't see the DRBD config.</div><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">When I change the r0.res to;</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">
<div>resource r0 {</div><div><br></div><div> device /dev/drbd0;</div><div> meta-disk internal;</div><div> disk /dev/sdb;</div><div><br></div><div> on node01 {</div><div> address <a href="http://10.0.0.1:7788/" target="_blank">10.0.0.1:7788</a>;<br>
</div><div> }</div><div> on node02 {</div><div> address <a href="http://10.0.0.2:7788/" target="_blank">10.0.0.2:7788</a>;<br></div><div> }</div><div>}</div></div><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">LCMC sees the DRBD config correctly.</div><div style="font-family:arial,sans-serif;font-size:13px">Problem is that /dev/sdb is not always the same disk on my test machine.</div>
</div><div><br></div><div><br></div><div>10) When adding a CRM resource (linbit:drbd) and you give the master/slave set a different name then the default (Which is drbd_1) it still gets added to the CIB with the name ms_drbd_1 even if you give it a different name like ms_drbd0 for instance.</div>
<div><br></div><div>You have to disconnect/reconnect for LCMC to see the difference and be able to manage the newly created resource.</div><div><br></div><div>ms <b>ms_drbd_1</b> res_drbd_drbd0 \<br></div><div><div> meta clone-max="2" notify="true" interleave="true"</div>
</div><div><br></div><div>11) When there is no *.res file in /etc/drbd.d or there is no drbd resource configured the global_common.conf file is not parsed. So when you create a drbd volume using LCMC the global_common.conf file is overwritten with very little options set. I would like to keep my global_common.conf file allthough there is no drbd volume configured (yet).</div>
<div><br></div><div>I don't want to manually set all these options again and LCMC should just overwrite it.</div><div><br></div><div>As i said, a fairly big list. I hope you can confirm and reproduce these issues so they can be fixed</div>
<div><br></div><div>Thanks in advance and keep up the good work on LCMC!</div><div><br></div><div>Kind regards,<br>Caspar Smit<br></div></div></div>