Description of problem: Some of the warning messages come while do complete sync or optimized sync on the N-1 capsule. Version-Release number of selected component (if applicable): 6.8 How reproducible: always Steps to Reproduce: 1. Prepare the setup of N-1(satellite:6.8 and Capsule 6.7) 2. Run complete sync on the capsule. 3. Sync completes successfully but sees some warning messages like below. - Puppet server classes cache is disabled, classes retrieval can be slow. - File at /var/lib/pulp/content defined in pulp_content_dir parameter doesn't exist or is unreadable - File at /var/lib/mongodb defined in mongodb_dir parameter doesn't exist or is unreadable Actual results: Some suspecious warning message came in complete sync and optimize sync on 6.7 capsule. Expected results: Wants to confirm that, Is it kind of expected which we can ignore or some problem? Additional info:
These messages have nothing to do with n-1 capsules, and are bugs on the capsule installation/configuration itself. Example: https://access.redhat.com/solutions/4241001 https://access.redhat.com/solutions/4009871 Since both of these messages have been around for quite a while, i'm tempted to: * move this bug to 6.10, since the mongo issue will go away with pulp3 * if we want the puppet warning to be resolved, we should clone it to another bz, and move to the capsule component
the pulp and mongo warnings should no longer be there with pulp2 removal in satellite 6.10
I can confirm the pulp and mongo warnings are gone in 6.10.0 snap 5, for the pulp warnings a KCS article exists: https://access.redhat.com/solutions/4241001
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Satellite 6.10 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:4702