WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Conversation

@evgeni
Copy link
Member

@evgeni evgeni commented Sep 19, 2025

No description provided.

@evgeni evgeni force-pushed the debian branch 6 times, most recently from 3ef53b1 to 834aafa Compare September 19, 2025 13:20
@evgeni evgeni changed the title CentOS 10 and Debian 13 CentOS Stream 10 Sep 19, 2025
vars:
foreman_puppet_repositories_version: "8"
when:
- ansible_distribution_major_version == '9'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be when the certificate source is the installer instead?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yepp, but this detail is not passed to the "setup repos" playbook, and I was lazy

@evgeni evgeni force-pushed the debian branch 8 times, most recently from fbb356d to 0f719e0 Compare September 23, 2025 09:09
ansible.builtin.file:
path: /etc/httpd/conf.d/welcome.conf
path: "{{ httpd_conf_path }}/welcome.conf"
state: absent
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A thought for upgrades and not necessary for this PR: RPM will place this file back. Should we ensure it's empty instead?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or just deploy on Debian, where the package manager is actually sane and respects the choices of the admin ;)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or just put it all in a container /me ducks

@evgeni evgeni force-pushed the debian branch 3 times, most recently from 50dede3 to 49d9e3f Compare September 23, 2025 10:39
- ansible_selinux.status == 'enabled'

- name: Enable required modules
community.general.apache2_module:
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like pulling in community.general here, but this is something we'd have to consider anyway.
In the Puppet installer, we run with apache::default_mods: false, which wipes all enabled modules and then we enable the ones we need.
We didn't port that detail over to foremanctl, and rely on the OS to enable those modules for us. But it also most probably enables things we do not want.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We may also want to enable the event MPM in a similar way.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like pulling in community.general here, but this is something we'd have to consider anyway.

May I ask why it is bad to use community.general?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly because it's a dependency we don't yet have

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It also mentions compatibility:

This does not work on RedHat-based distributions. It does work on Debian- and SuSE-based distributions. Whether it works on others depend on whether the C(a2enmod) and C(a2dismod) tools are available or not.

So configuring Apache with Ansible is certainly worse than what we had with our Puppet module.

@evgeni evgeni changed the title CentOS Stream 10 CentOS Stream 10 (and Debian 13?) Sep 23, 2025
@evgeni evgeni force-pushed the debian branch 3 times, most recently from 42c388f to 1660537 Compare October 16, 2025 07:48
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 this pull request may close these issues.

5 participants