On Tue, Aug 23, 2022 at 10:21 PM Reid Wahl <nw...@redhat.com> wrote: > > On Tue, Aug 23, 2022 at 10:14 PM Lentes, Bernd > <bernd.len...@helmholtz-muenchen.de> wrote: > > > > > > > > ----- On 24 Aug, 2022, at 07:03, arvidjaar arvidj...@gmail.com wrote: > > > > > On 24.08.2022 07:34, Lentes, Bernd wrote: > > >> > > >> > > >> ----- On 24 Aug, 2022, at 05:33, Reid Wahl nw...@redhat.com wrote: > > >> > > >> > > >>> The stop-all-resources cluster property is set to true. Is that > > >>> intentional? > > >> OMG. Thanks Reid ! > > You're welcome :) > > > >> > > >> But unfortunately not all virtual domains are running: > > >> > > > > > > what exactly is not clear in this output? All these resources are > > > explicitly disabled (target-role=stopped) and so will not be started. > > > > > That's clear. But a manual "crm resource start virtual_domain" should start > > them, > > but it doesn't. > > I'm familiar with pcs and the pacemaker CLI tools but not crmsh, so > I'm not sure exactly what `crm resource start` does. However, running > a manual start command in pcs or crm_resource simply runs the resource > agent's start operation. **It does not inform Pacemaker.** I presume > crmsh behaves similarly. > > As a result, your command might start the virtual machines, but > Pacemaker will still show that the resources are "Stopped (disabled)". > To fix that, you'll need to enable the resources.
Are the VMs running after your start command? > > > > > Bernd_______________________________________________ > > Manage your subscription: > > https://lists.clusterlabs.org/mailman/listinfo/users > > > > ClusterLabs home: https://www.clusterlabs.org/ > > > > -- > Regards, > > Reid Wahl (He/Him) > Senior Software Engineer, Red Hat > RHEL High Availability - Pacemaker -- Regards, Reid Wahl (He/Him) Senior Software Engineer, Red Hat RHEL High Availability - Pacemaker _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
