Skip to content

/etc/puppetlabs/enterprise/conf.d missing on postgres server causing upgrade to fail #344

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

Closed
16c7x opened this issue Apr 25, 2023 · 1 comment · Fixed by #346
Closed
Assignees

Comments

@16c7x
Copy link

16c7x commented Apr 25, 2023

Describe the Bug

If you build an x-large infrastructure with peadm, the /etc/puppetlabs/enterprise/conf.d is not created. If you then use peadm::upgrade plan it fails on the Postgres server trying to write the pe.conf file.

Expected Behavior

The install of the Postgres server should create the /etc/puppetlabs/enterprise/conf.d directory
Or
The peadm::upgrade plan should check it /etc/puppetlabs/enterprise/conf.d exists and if not create it.

Steps to Reproduce

Run peadm::install for an x-large infrastructure.
rn peadm::upgrade.

Environment

  • Version [e.g. 1.27.0]
  • Platform [e.g. Ubuntu 18.04]

Additional Context

Add any other context about the problem here.

@16c7x 16c7x added the bug label Apr 25, 2023
@16c7x
Copy link
Author

16c7x commented Apr 27, 2023

This looks like it only affect postgres server added with the add database plan, anything built in one hit will have had the install sub plan run on it which does this
https://github.com/puppetlabs/puppetlabs-peadm/blob/main/plans/subplans/install.pp#L393
So similar functionality need to be added to the add database plan.

@16c7x 16c7x self-assigned this Apr 27, 2023
@16c7x 16c7x linked a pull request Apr 27, 2023 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant