What I'm not sure, is what was the running libknet version.
package was upgraded everywhere to 1.16, but I have notice that corosync
process is not restarted when libknet is upgraded.
so it's quite possible that corosync was still running 1.13 libknet. (I need to
find a way to find last coros
> do you think it could be possible to add an extra optionnal layer of security
> check, not related to corosync ?
I would try to find the bug instead.
> I'm still afraid of this corosync bug since years, and still don't use HA.
> (or I have tried to enable it 2months ago,and this give me a dis
Hello
I didn't know this patch mail got approved, so sorry for the (very) late
response.
My intention for not going with snippets was the fact that they could not be
created via the API and one would have to manually create a file on the target
machine for cloud-init userdata.
One possi
No actually this was a misstake.
I tought my old patch was stuck in approval and got deleted.
These patches can be ignored.
-Ursprüngliche Nachricht-
Von: Mira Limbeck
Gesendet: Freitag 28 August 2020 17:46
An: pve-devel@lists.proxmox.com
Betreff: Re: [pve-devel] [PATCH] api: cloud-in
BTW,
do you think it could be possible to add an extra optionnal layer of security
check, not related to corosync ?
I'm still afraid of this corosync bug since years, and still don't use HA. (or
I have tried to enable it 2months ago,and this give me a disaster yesterday..)
Something like an ex
On 03.09.20 15:52, Dominik Csapak wrote:
> comments inline
>
> On 8/25/20 11:24 AM, Dominic Jäger wrote:
>> Additionally, add parameters that enable directly (avoiding the intermediate
>> step as unused disk) attaching the disk to a bus/device with all known disk
>> options.
>>
>> Required to crea
