Pacemaker::New::Setup::Pcsd/Pacemaker_pcsd_auth[setup] error

Bug #1907606 reported by Yu Chan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
puppet-pacemaker
New
Undecided
Unassigned

Bug Description

OS: centos 8
Platform: Google Cloud Platform
pcs version: 0.10.6

Error happened when running:

sudo puppet agent -t

Error log:

Error: /Stage[main]/Pacemaker::New::Setup::Pcsd/Pacemaker_pcsd_auth[setup]: Could not evaluate: Could not parse the result of the cluster auth command: ''
Notice: /Stage[main]/Pacemaker::New::Setup::Pcsd/Exec[create-cluster]: Dependency Pacemaker_pcsd_auth[setup] has failures: true
Warning: /Stage[main]/Pacemaker::New::Setup::Pcsd/Exec[create-cluster]: Skipping because of failed dependencies
Warning: /Stage[main]/Pacemaker::New::Setup::Pcsd/Exec[start-cluster]: Skipping because of failed dependencies
Warning: /Stage[main]/Pacemaker::New::Service/Service[corosync]: Skipping because of failed dependencies
Warning: /Stage[main]/Pacemaker::New::Service/Service[pacemaker]: Skipping because of failed dependencies
Warning: /Stage[main]/Pacemaker::New::Setup::Pcsd/Pacemaker_online[setup]: Skipping because of failed dependencies
Warning: /Stage[main]/Beacon::Main_server::Pcs/Pacemaker_resource[beacond]: Skipping because of failed dependencies

No error happened on centos 7 with pcs version 0.9.168

puppet code:

class { 'pacemaker::new' :
    cluster_nodes => $cluster_nodes,
    cluster_name => "main_${::environ}",
    cluster_password => 'password',

    firewall_corosync_manage => false,
    firewall_pcsd_manage => false,
  }
  pacemaker_property { 'stonith-enabled' :
    ensure => 'present',
    value => false,
  }
  pacemaker_property { 'no-quorum-policy' :
    ensure => 'present',
    value => 'stop',
  }

affects: tripleo → puppet-pacemaker
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.