Bug #35157
closed
cache-enabled setting for proxy content module isn't migrated to 'true' properly
Description
This migration (https://github.com/theforeman/foreman-installer/commit/4155c66f59ea42fe10d709434d6ab5dcdb66b572) is directed at the proxy-content puppet module, but it needs to be migrated through the Katello puppet module. As a result, folks are seeing the redis cache being turned off on their systems. Community thread: https://community.theforeman.org/t/upgrade-issue-to-4-4-1-internal-server-error-and-a-notice-about-4-5-rc2/29124/16
Updated by Ian Ballou almost 2 years ago
Katello expects the redis cache to be enabled. If it isn't it fails. Perhaps the redis cache should be permanently on rather than configurable.
Updated by Ewoud Kohl van Wijngaarden almost 2 years ago
it needs to be migrated through the Katello puppet module.
I don't see how that could work. puppet-katello doesn't have any Pulp settings: it's all in puppet-foreman_proxy_content. Perhaps you meant the katello installer scenario? https://community.theforeman.org/t/upgrade-issue-to-4-4-1-internal-server-error-and-a-notice-about-4-5-rc2/29124/15 suggests you are talking about the katello scenario.
Updated by Ewoud Kohl van Wijngaarden almost 2 years ago
- Related to Feature #34325: Enable the redis cache for pulp content server by default added
Updated by The Foreman Bot almost 2 years ago
- Status changed from New to Ready For Testing
- Assignee set to Ewoud Kohl van Wijngaarden
- Pull request https://github.com/theforeman/foreman-installer/pull/794 added
Updated by Ewoud Kohl van Wijngaarden almost 2 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset installer|b6305f7f8d7877ec9a38314a6eed521143bd27ff.
Updated by The Foreman Bot over 1 year ago
- Pull request https://github.com/theforeman/foreman-installer/pull/802 added