-
Notifications
You must be signed in to change notification settings - Fork 7
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
auto-add-quorum-tie-breaker not honoured for containers (only) #45
Comments
The "unrecognized argument" looks like a client bug (@rp- ). |
well the advise command seems just wrong here, I guess it should be |
Well, yes, unless the ResourceDefinition overrules the otherwise inherited controller-property. The same property can be set on multiple levels (Controller, ResourceGroup, ResourceDefinition, etc...). As a rule of thumb: The closer the property is to the actual volume (LVM / ZFS / ...) the higher its priority. In this case the Regarding the rest: please update the linstor-client. That means, I assume that you indeed had your tie-breaking resource deployed as expected, but it was simply hidden by the mentioned client behavior. I suspect this due to these logs:
only 2 resources shown here
Suddenly you have 3 resources. A tie-breaking resource that gets promoted (DRBD primary) immediately loses its |
In this case RD properties are set automatically during the VM/CT creation process via the LINSTOR Proxmox plugin. There are no properties set at the RG level..
Below follow some more tests, both when creating a Qemu VM and a LXC container... QEMU VM=vm-109-disk-1
|
Ok, after some further testing it looks like this is not a LINSTOR issue, as when I create RD/VD/Resource directly via linstor in the command line, auto-tie-breaker is automatically created once I delete the Diskless resource from the respective node. The property is correctly inherited from the Controller as expected in this case. The "issue" seems to be related to Proxmox/LINSTOR plugin and how it handles "live migration" and "shutdown/start" actions no matter if that's a VM or a CT. So to summarise, in order for the auto-tie-breaker resource to be created in Proxmox, there are 2 options:
|
hm, yes, without thinking it through completely, such things could happen. The "when to create a diskless and when to remove it" logic is currently in the plugin: if there is none whatsoever, create a diskless one. If moved away and it is diskless, just delete it. That in combination with auto-tiebreaker might have funny consequences. LINSTOR now can handle that on its own, there is a "make available" API that does the right thing and handles more complicated storage situations. The plugin has not switched to that API. So let's keep this open as tracking issue. |
I'm doing some tests regarding quorum auto tie breaker and I noticed that even though it's honoured for qemu VMs, it does not for LXC containers. Not sure if this the right place to post this, but I thought that since this occurs on Proxmox, it might be more related to its plugin.
Here's a sequence of the commands...
Shouldn't the property inherited from the controller set properties ?...anyway I add it manually...
Not sure if the above advise is correct in the first place ?
The text was updated successfully, but these errors were encountered: