Issue #5104
closed
Pulp 2 stops working after installing Pulp 3
Description
After Pulp 3 is installed on the same machine that has Pulp 2 running on it the following message appears in the logs anytime httpd tries to connect to Qpid:
Jul 10 11:48:07 pulp2-nightly-pulp3-source-centos7.localhost.example.com pulp[19490]: gofer.messaging.adapter.connect:INFO: connecting: qpid+tcp://localhost:5672
Jul 10 11:48:07 pulp2-nightly-pulp3-source-centos7.localhost.example.com pulp[19490]: gofer.messaging.adapter.qpid.connection:INFO: open: URL: tcp://localhost|SSL: ca: /etc/pki/qpid/ca/
ca.crt|key: None|certificate: /etc/pki/qpid/client/client.pem|host-validation: False
Jul 10 11:48:07 pulp2-nightly-pulp3-source-centos7.localhost.example.com qpidd[19462]: 2019-07-10 11:48:07 [Security] error Rejected un-encrypted connection.
Jul 10 11:48:07 pulp2-nightly-pulp3-source-centos7.localhost.example.com qpidd[19462]: 2019-07-10 11:48:07 [Protocol] error Connection qpid.[::1]:5672-[::1]:36582 closed by error: conne
ction-forced: Connection must be encrypted.(320)
Jul 10 11:48:07 pulp2-nightly-pulp3-source-centos7.localhost.example.com pulp[19490]: gofer.messaging.adapter.connect:ERROR: connect: qpid+tcp://localhost:5672, failed: connection abort
ed
Jul 10 11:48:07 pulp2-nightly-pulp3-source-centos7.localhost.example.com pulp[19490]: gofer.messaging.adapter.connect:INFO: retry in 10 seconds
Related issues
Updated by dalley almost 5 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 56
Updated by dkliban@redhat.com almost 5 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dkliban@redhat.com
Updated by dkliban@redhat.com almost 5 years ago
- Status changed from ASSIGNED to POST
Updated by dkliban@redhat.com over 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset ansible-pulp3|4151d394be7c9ba21d28d718a70e7bba18244d60.
Added by dkliban@redhat.com over 4 years ago
Added by dkliban@redhat.com over 4 years ago
Revision a8d2b05c | View on GitHub
Problem: Pulp 2 stops working after installing Pulp 3
Solution: make use of the 'pulp' group when setting permissions
Pulp 2.20 changed ownership of /var/lib/pulp and /etc/pulp from group 'apache' to group 'pulp'. This change to the installer ensures that the permissions on these directories remain the same after the installer runs on a machine that already has Pulp 2 installed.
This patch introduces 3 new pulp settings called 'pulp_group', 'pulp_group_id', and 'pulp_user_id'. The 'pulp_group' defaults to 'pulp'. The 'pulp_user' is added to the 'pulp_ group' group. The connection is reset after this to support installations where the ssh user being used for ansible is the same as the pulp_user. This allows the user changes to take affect. The defaults for 'pulp_user_id' and 'pulp_group_id' are empty. When specified, the installer will use values to set 'uid' and 'gid' respectively.
Updated by dkliban@redhat.com over 4 years ago
Applied in changeset ansible-pulp3|a8d2b05c6e68bfb236a6ab15867c493a01711db0.
Updated by kersom over 4 years ago
- Related to Test #5258: Test - Pulp 2 stops working after installing Pulp 3 added
Updated by bmbouter over 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
.
Problem: Pulp 2 stops working after installing Pulp 3
Solution: make use of the 'pulp' group when setting permissions
Pulp 2.20 changed ownership of /var/lib/pulp and /etc/pulp from group 'apache' to group 'pulp'. This change to the installer ensures that the permissions on these directories remain the same after the installer runs on a machine that already has Pulp 2 installed.
This patch introduces 3 new pulp settings called 'pulp_group', 'pulp_group_id', and 'pulp_user_id'. The 'pulp_group' defaults to 'pulp'. The 'pulp_user' is added to the 'pulp_ group' group. The connection is reset after this to support installations where the ssh user being used for ansible is the same as the pulp_user. This allows the user changes to take affect. The defaults for 'pulp_user_id' and 'pulp_group_id' are empty. When specified, the installer will use values to set 'uid' and 'gid' respectively.
closes: #5104 https://pulp.plan.io/issues/5104