[openstack-ansible][masakari][yoga]pcs cluster not getting started
Dear All, I have upgraded my openstack cluster from wallaby to Yoga. And I am facing issue with masakari services. pacemaker service is running fine on all nodes but pacemaker_remote.service is not getting started on any of the nodes. And Masakari containers doesn't have any idea of it monitor nodes. I purged the masakari cluster and tried to deploy it again. Playbook is running successfully again and again but it is not setting up the cluster. Playbook is not installing corosync service on masakari containers and now pacemaker server is also not getting installed on masakari api containers. I idea to run masakari in a way that it can create the cluster and install required services on its own? I tried with below but that did not work:
forgot to add below lines in mail: I tried with below but that did not work: Purged pacemaker, corosyn and masakari services from everywhere(masakari containers and compute nodes) so that playbook can install packages and can create fresh config files. #openstack-ansible os-masakari-install.yml -e venv_rebuild=yes -e force_containers_rebuild=yes -e package_state=latest But my masakari cluster is still now UP: from compute node: root@host5:~# crm status Cluster Summary: * Stack: corosync * Current DC: host4 (version 2.0.3-4b1f869f0f) - partition with quorum * Last updated: Fri Feb 7 15:00:33 2025 * Last change: Fri Feb 7 14:35:58 2025 by hacluster via crmd on host7 * 6 nodes configured * 0 resource instances configured Node List: * Online: [ host2 host3 host4 host5 host6 host7 ] Full List of Resources: * No resources root@host5:~# pcs cluster status Cluster Status: Cluster Summary: * Stack: corosync * Current DC: host4 (version 2.0.3-4b1f869f0f) - partition with quorum * Last updated: Fri Feb 7 15:00:42 2025 * Last change: Fri Feb 7 14:35:58 2025 by hacluster via crmd on host7 * 6 nodes configured * 0 resource instances configured Node List: * Online: [ host2 host3 host4 host5 host6 host7 ] PCSD Status: Warning: Unable to read the known-hosts file: No such file or directory: '/var/lib/pcsd/known-hosts' host7: Offline host6: Unable to authenticate host4: Unable to authenticate host5: Unable to authenticate host2: Unable to authenticate host3: Unable to authenticate root@host5:~# From masakari container: root@host1-masakari-api-container:~# crm status bash: crm: command not found root@bbs-m-cloud-infra1-masakari-api-container:~# pcs cluster status No such file or directory Error: unable to locate command: /usr/sbin/crm_mon Regards, Danish On Fri, Feb 7, 2025 at 12:30 PM Danish Khan <danish52.jmi@gmail.com> wrote:
Dear All,
I have upgraded my openstack cluster from wallaby to Yoga. And I am facing issue with masakari services.
pacemaker service is running fine on all nodes but pacemaker_remote.service is not getting started on any of the nodes.
And Masakari containers doesn't have any idea of it monitor nodes.
I purged the masakari cluster and tried to deploy it again. Playbook is running successfully again and again but it is not setting up the cluster.
Playbook is not installing corosync service on masakari containers and now pacemaker server is also not getting installed on masakari api containers.
I idea to run masakari in a way that it can create the cluster and install required services on its own?
I tried with below but that did not work:
Dear All, I think I got it now. In yoga we are using crm instead of pcs. So pcsd pacemaker_remote services are not of used now hence I have disabled it. And now crm or pcs command is not supposed to run by default from masakari containers. Regards. Danish On Fri, 7 Feb, 2025, 12:30 pm Danish Khan, <danish52.jmi@gmail.com> wrote:
Dear All,
I have upgraded my openstack cluster from wallaby to Yoga. And I am facing issue with masakari services.
pacemaker service is running fine on all nodes but pacemaker_remote.service is not getting started on any of the nodes.
And Masakari containers doesn't have any idea of it monitor nodes.
I purged the masakari cluster and tried to deploy it again. Playbook is running successfully again and again but it is not setting up the cluster.
Playbook is not installing corosync service on masakari containers and now pacemaker server is also not getting installed on masakari api containers.
I idea to run masakari in a way that it can create the cluster and install required services on its own?
I tried with below but that did not work:
participants (1)
-
Danish Khan