<div dir="ltr"><div>Hi,</div><div><br></div><div>I tried to recreate this issue, but without success.</div><div><br></div><div>4 Node setup, all LVM<br></div><div>First create a resource with --auto-place 3,</div><div>Create 9 other resources with --auto-place 4</div><div>Create the first resource on the 4th (missing) node</div><div>Check "linstor volume list" <br></div><div><br></div><div>That means, there has to be something else in your setup. <br></div><div>What else did you do? I see that your "first" resource "windows-wm" was more like the second resource, as it got the minor-number 1001, instead of 1000. That minor-number 1000 was later reused by "testvm1". However, was something broken with the "original" resource using minor-number 1000?</div><div><br></div><div>Error report 5F733CD9-00000-000004 is a NullPointerException, but this is most likely just a side-effect of the original issue. <br></div><div><br></div><div>> Since it looks relevant, error reports 1, 2 and 3 are all similar for nodes castle, san5 and san6</div><div> <br></div><div>What about error report 0? Not relevant for this issue?</div><div><br></div><div>> 1) Why did I end up in this state? I assume something was configured on castle/san5/san6 but not on san7.</div><div><br></div><div>Not sure... If something would be broken on san7, you should also have gotten an error report from a satellite. The ones you showed here are all created by the controller (error-ids XXX-00000-YYY are always controller-errors, satellite errors would also have some other "random-looking" number instead of the -00000- part)<br></div><div><br></div><div>>
2) How can I fix it?</div><div><br></div><div>If I cannot recreate it, there is not much I can do. You could of course try restarting the controller, that will reload the data from the database, which might fix things... I would be still curious what caused all of this...</div><div><br></div><div>Best regards,</div><div>Gabor<br></div></div>