-
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
Fixes #29589 - Ensure pulpcore before proxy #252
Conversation
When the Foreman Proxy registration happens, Pulp's features are queried and presented as capabilities. If the service is down, Katello can't detect the right content types.
Looks sane but that dependency cycle is funky with the daemon reloads chaining together. |
Yes. That isn't needed in Puppet >= 6.1 but for now we have to support Puppet 5 too. The workaround is to not let |
@@ -338,6 +338,7 @@ | |||
postgresql_db_ssl_cert => $pulpcore_postgresql_ssl_cert, | |||
postgresql_db_ssl_key => $pulpcore_postgresql_ssl_key, | |||
postgresql_db_ssl_root_ca => $pulpcore_postgresql_ssl_root_ca, | |||
before => Class['foreman_proxy::plugin::pulp'], |
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.
Could we do it before the register?
iff --git a/manifests/init.pp b/manifests/init.pp
index 9bea8db..78d833a 100644
--- a/manifests/init.pp
+++ b/manifests/init.pp
@@ -338,6 +338,7 @@ class foreman_proxy_content (
postgresql_db_ssl_cert => $pulpcore_postgresql_ssl_cert,
postgresql_db_ssl_key => $pulpcore_postgresql_ssl_key,
postgresql_db_ssl_root_ca => $pulpcore_postgresql_ssl_root_ca,
+ before => Class['foreman_proxy::register'],
}
if $pulp_master {
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.
Tried that, same error.
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.
Strange, I made this change, ran tests. Everything passed. I ran it again, got these failures. Perhaps my fixtures weren't up to date? Implies it was a more recent change that led to this?
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.
theforeman/puppet-puppet#741 would remove the dependency cycle. Once that's merged, tests can be restarted. |
When the Foreman Proxy registration happens, Pulp's features are queried and presented as capabilities. If the service is down, Katello can't detect the right content types.