-
Notifications
You must be signed in to change notification settings - Fork 36
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
Fixes #37707 - Purge container_gateway feature without docker #488
Conversation
Tests are broken and there is a commit in #487 that fixes them. |
This will need a bump in |
This can be rebased now. |
Could you review theforeman/puppet-foreman_proxy#843 first? Then I can work on releasing that module. |
96195a7
to
909e817
Compare
puppet-pulpcore can no longer guarantee idempotency and reliably migrate the database[1]. An option[2] was introduced to pretend it's idempotent, which in upgrades may break but is good enough for CI. [1]: theforeman/puppet-pulpcore@f8d0dc6 [2]: theforeman/puppet-pulpcore@0004d05
If smart_proxy_container_gateway was already installed on a host and then enable-docker => false is used, it leaves it enabled but without Apache proxy config. On Foreman it'll also be reported as a feature. This is inconsistent. The new code ensures the feature is actually purged.
909e817
to
268fc30
Compare
Idempotency is broken because of theforeman/puppet-pulpcore#351. I opened #491 and included it here |
class { 'foreman_proxy_content': | ||
pulpcore_mirror => true, | ||
enable_docker => false, | ||
# No Ansible repo is set up in our CI |
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.
what ansible repo? ansible-core is in baseos these days :)
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.
I copied this from another test. I'll see about dropping it.
If smart_proxy_container_gateway was already installed on a host and then enable-docker => false is used, it leaves it enabled but without Apache proxy config. On Foreman it'll also be reported as a feature. This is inconsistent.
The new code ensures the feature is actually purged.
It's a draft because it relies on theforeman/puppet-foreman_proxy#843 to work properly. Otherwise it'll start to install a database and deploy the config file.