-
Notifications
You must be signed in to change notification settings - Fork 37
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
include apache::mod::alias in foreman_proxy_content::pub_dir #409
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#326 is merged, so you can go ahead here |
I did re-kick the tests, and at least this doesn't seem to break anything? :) |
Interesting:
This may actually something we do want as a base module. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the spam, but looking closer: I do wonder, where does the alias come from. Looking at the contents here I don't see what creates it. It's actually in templates/httpd_pub.erb
so it should be defined close to that. So manifests/pub_dir.pp
is the correct file to place it in.
Even after working through #411 I've still been struggling to determine why in my testing, when passing
When for other projects I've been through this process already and was able to trim it down to an initially smaller list and build that back up by including specific modules as required by the configuration. It finally occurred to me to check again what this looks when omitting the So the good news is that although the behavior is different from what I expected, my hieradata isn't actually being ignored. And it seems the explicit A good test will be to run |
@wbclark Can you clarify then the state of this PR? Are you performing further tests or is it OK to merge? |
I'm testing the comparison between the apache modules installed by this module when working around theforeman/forklift#1487 to do that |
I've been having further issues with forklift in testing this, but I believe I've solved the problem. will update when my pipeline completes |
Testing the latest version with https://github.com/wbclark/forklift/tree/default_mods To test, first clean up the previous environment if any: $ for id in $(vagrant global-status --prune 2>&1 | grep $(pwd) | awk '{print $1}') ; do vagrant destroy -f $id ; done Then run the test (Katello in this example): $ ansible-playbook pipelines/install_pipeline.yml -e forklift_state=up -e pipeline_os=centos8-stream -e pipeline_type=katello -e pipeline_version=nightly |
Regarding the unit test failures here, I'm unable to reproduce in my environment:
|
The failures are unrelated to your change. This are result of dropping apipie:cache:index and I forgot that this work around lived in here. I've opened #414 to address it |
With this branch, I can now run foreman-installer nightly with
And the following modules for the foreman-proxy-content scenario:
|
This reverts commit 8dcbeb4. theforeman/puppet-foreman_proxy_content#409 is now merged, so pulling in the custom branch is no longer necessary for this testing.
Part of the effort that was originally theforeman/foreman-installer#754