[ClusterLabs] [ClusterLabs Developers] ERROR: LXC container name not set!

[Reid Wahl]

Moving to users list

On Thu, Mar 30, 2023 at 3:04 AM John via Developers
<developers at clusterlabs.org> wrote:
>
> Hey guys! I found some problem with /usr/lib/ocf/resource.d/heartbeat/lxc :
>
> OS: Debian 11 (And debian 10)
>
> Kernel: 5.10.0-15-amd64
>
> Env: resource-agents 1:4.7.0-1~bpo10+1, pacemaker 2.0.5-2, corosync 3.1.2-2, lxc 1:4.0.6-2
>
> Just trying to add new resource
>
>
> lxc-start -n front-2.fr
> pcs resource create front-2.fr ocf:heartbeat:lxc config=/mnt/cluster_volumes/lxc2/front-2.fr/config container=front-2.fr
>
>
> After ~5min want to remove it
>
>
> pcs resource remove front-2.fr --force
>
>
> got an error and cluster starts to migrate
>
>
> Mar 29 23:28:51 cse2.fr lxc(front-2.fr)[2103391]: ERROR: LXC container name not set!
>
> as i can see in /usr/lib/ocf/resource.d/heartbeat/lxc the error spawns when agent can't get OCF_RESKEY_container variable.
> This bug is only on clusters who work without reboot a long time. For example after fencing i can add/remove lxc resources and everything will be fine for a while.
>
> The question is: why? And how to debug it?
>
>
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/developers
>
> ClusterLabs home: https://www.clusterlabs.org/



-- 
Regards,

Reid Wahl (He/Him)
Senior Software Engineer, Red Hat
RHEL High Availability - Pacemaker