Instance exists in prado (which is due for migration soon [1]).
A new one got installed manually in the new db machine (belvedere).
Puppetize it.
[1] T1773
Description
Description
Related Objects
Related Objects
- Mentioned In
- rSPRE4b4b54ec961c: README: Explain how to initialize and apply changes to infra
D1795: README: Explain how to initialize and apply changes to infra
D1762: Provision staging vms through terraform (up to the first puppet run)
rSPSITE07c9a5c79927: Migrate indexer-storage service to use somerset's pgbouncer instance
rSPSITE79580c26e485: Migrate services to use the pgbouncer instances
D1560: Migrate services to use pgbouncer instances
rSPSITEa1400c6db845: pgbouncer: Deal with somerset/prado's instance
D1555: pgbouncer: Deal with somerset/prado's instance
rSPSITEb40b2036f49b: Puppetfile: pgbouncer: Use fix in puppet module
D1554: Puppetfile: pgbouncer: Use commit with puppet module fix
rSPSITEbb8f6d428bef: pgbouncer: Run pgbouncer as postgres user
rSPSITE6f7fc6fe41f3: pgbouncer: Adapt listen_addr, admin_users config appropriately
rSPSITE56bbad5d8a63: Reference actual pgbouncer configuration
rSPSITE438377ce0287: Puppetfile: Reference pgbouncer module
D1550: Add pgbouncer configuration
rSENVd841393fcfc4: .mrconfig: Add new puppet external module to manage pgbouncer - Mentioned Here
- R191:9ec0d8a1255b: database: Use `auth_user` directive as intended
Event Timeline
Comment Actions
There is an issue in the pgbouncer puppet module [1]
I'm fixing it [2], checking it works [3]
I opened the issue upstream.
I also opened a PR to fix it upstream [4]
[1] https://github.com/covermymeds/puppet-pgbouncer/issues/31
[2] 9ec0d8a
Comment Actions
I confirm that using the fix published in our mirror and proposed upstream, it now works!