Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuring unicast mode is confusing #496

Open
agriffit79 opened this issue Dec 14, 2020 · 1 comment
Open

Configuring unicast mode is confusing #496

agriffit79 opened this issue Dec 14, 2020 · 1 comment

Comments

@agriffit79
Copy link

agriffit79 commented Dec 14, 2020

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 5.5.22
  • Ruby: 2.4.10p364
  • Distribution: CentOS 7.9.2008
  • Module version: 7.0.0

How to reproduce (e.g Puppet code you use)

class pg {

  class { 'corosync':
    bind_address   => $facts['networking']['interfaces']['eth0']['ip'],
    cluster_name   => 'pg12',
    enable_secauth => false,
    set_votequorum => true,
    quorum_members => [ 'pgsql01', 'pgsql02' ],
    unicast_addresses => [ '192.168.100.200', '192.168.100.212']
  }

  corosync::service { 'pacemaker':
    version => '0',
  }

  cs_property { 'stonith-enabled':
    value => 'false',
  }

  cs_property { 'no-quorum-policy':
    value => 'ignore',
  }
}

What are you seeing

In order to have transport set to udpu it it necessary to populate unicast_addresses but these values are not actually populated into corosync.conf when set_votequorom => true which is the default setting on Red Hat (and derivatives).

What behaviour did you expect instead

It seems confusing to set a value which is not used directly but instead used to infer another value. I could put complete rubbish in unicast_addresses and still get the same output. Should there not be an explicit transport param or at least some way to explicit state you want to use udpu transport?

Output log

Any additional information you'd like to impart

@agriffit79 agriffit79 changed the title Configuring unicast mode is configusing Configuring unicast mode is confusing Dec 14, 2020
@jnguiot
Copy link

jnguiot commented Jan 5, 2021

I agree with you, this system is strange. I also have a udpu system with several rings (corosync 2.4.3 and pacemake 1.1.18). However, I need to declare a bindnetaddr or pacemaker have a lot of trouble to run.
The disabling of member have been introduced in #430 to resolve #421. @btravouillon has stated that member are not needed (#422 (comment)) which is confirmed by corosync/corosync@de70c00.
However, I have found useful to put the bindnetaddress outside of the set_votequorum condition, so to invert those lines:

bindnetaddr: <%= Array(@bind_address)[interface] %>
and
Is there a reason why corosync need this declaration?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants