Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1154037

Summary: RPM Repo Sync not working when created according to Documentation
Product: [Retired] Pulp Reporter: bugzilla
Component: z_otherAssignee: Brian Bouterse <bmbouter>
Status: CLOSED NOTABUG QA Contact: pulp-qe-list
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.4.2CC: bmbouter, bugzilla, jortel, mhrivnak
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-29 18:52:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Syslog of the event none

Description bugzilla 2014-10-17 11:20:16 UTC
Description of problem:

Installation of according to documentation with qpit does not end with a working installation. Syncing of repositories fails.
The current documentation does not enable somebody to get pulp installed working according to the documentation.


Version-Release number of selected component (if applicable):

[root@centos65pulp ~]# rpm -qa | grep pulp
python-pulp-puppet-common-2.4.2-1.el6.noarch
mod_wsgi-3.4-1.pulp.el6.x86_64
pulp-rpm-plugins-2.4.2-1.el6.noarch
pulp-selinux-2.4.2-1.el6.noarch
python-pulp-client-lib-2.4.2-1.el6.noarch
pulp-rpm-admin-extensions-2.4.2-1.el6.noarch
python-isodate-0.5.0-4.pulp.el6.noarch
python-rhsm-1.8.0-2.pulp.el6.x86_64
python-pulp-rpm-common-2.4.2-1.el6.noarch
createrepo-0.9.9-21.2.pulp.el6.noarch
python-kombu-3.0.15-12.pulp.el6.noarch
pulp-server-2.4.2-1.el6.noarch
pulp-puppet-plugins-2.4.2-1.el6.noarch
python-pulp-bindings-2.4.2-1.el6.noarch
pulp-admin-client-2.4.2-1.el6.noarch
pulp-puppet-admin-extensions-2.4.2-1.el6.noarch
python-pulp-common-2.4.2-1.el6.noarch

How reproducible:
- Following the guideline on https://pulp-user-guide.readthedocs.org/en/latest/installation.html#server:

Steps to Reproduce:
1. Install virtual machine with CentOS 6.5 (minimal server)
2. Drop http://repos.fedorapeople.org/repos/pulp/pulp/rhel-pulp.repo in `/etc/yum.repos.d`
3.  `$ sudo rpm -Uvh https://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm`
4.  `$ sudo yum clean all && sudo yum  makecache`
5.  `$ sudo yum install mongodb-server`
6.  `$ sudo service mongod start && sudo chkconfig mongod on`
8.  `$ sudo yum install qpid-cpp-server qpid-cpp-server-store`
9.  `$ sudo service qpidd start && sudo chkconfig qpidd on`
10. `$ sudo yum groupinstall pulp-server-qpid`
11. `$ sudo -u apache pulp-manage-db`
12. `$ sudo service httpd start && sudo chkconfig httpd on`
13. `$ sudo chkconfig pulp_workers on && sudo service pulp_workers start`
14. `$ sudo chkconfig pulp_celerybeat on && sudo service pulp_celerybeat start`
15. `$ sudo chkconfig pulp_resource_manager on && sudo service pulp_resource_manager start` 
16. `$ sudo yum groupinstall pulp-admin`
17. Updating `/etc/pulp/admin/admin.conf` with SSL=false and the correct hostname
18. Loging in with the admin client
  
  $ pulp-admin login -u admin -p

19. Creating a CentOS mirror repository:

  $ pulp-admin rpm repo create --repo-id centos65-x86_64 --serve-http true --serve-https true --feed http://mirror.centos.org/centos/6.5/os/x86_64

20. Starting synchronization

  $ pulp-admin rpm repo sync run --repo-id centos65-x86_64


Actual results:

[root@centos65pulp ~]#  pulp-admin rpm repo sync run --repo-id centos65-x86_64
+----------------------------------------------------------------------+
               Synchronizing Repository [centos65-x86_64]
+----------------------------------------------------------------------+

An internal error occurred on the Pulp server:

RequestException: POST request
on /pulp/api/v2/repositories/centos65-x86_64/actions/sync/ failed with 500 -
Unhandled Exception


Expected results:

either

a) a syncing repo
b) an update to the documentation leading to a working installation
c) a workaround.


Additional info:

* Related BUG: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1141336
* Fix is according to IRC available in v2.5.1, but not in the upcoming v2.5

Comment 1 Jeff Ortel 2014-10-22 16:18:56 UTC
Please attach the syslog for this event.

Comment 2 bugzilla 2014-10-29 08:20:37 UTC
Created attachment 951661 [details]
Syslog of the event

Syslog messages from /var/log/messages on CentOS 6.5 when running ` pulp-admin rpm repo sync run --repo-id <repo>`

Comment 3 Brian Bouterse 2014-10-29 18:52:48 UTC
From the attachment, I can see this is an issue with your environment/configuration missing sasl plain support for Qpid which is provided by a package you can install. Since it's not a Pulp bug I'm going to close this, but here is some info that should help you resolve this.

The problem is that Pulp can't connect to Qpid using an agreed authentication mechanism. SASL is used by Qpid for authentication. This was resolved more gracefully with 2.5.1 release [0], but since you're on 2.4 and 2.5.1 isn't released yet you should read this note [1] about installing the cyrus-sasl-plain package.

If this still doesn't resolve this issue for you, please send a note to pulp-list.

[0]:  http://pulp.readthedocs.org/en/latest/user-guide/release-notes/2.5.x.html?highlight=sasl#new-features
[1]:  http://pulp.readthedocs.org/en/latest/user-guide/broker-settings.html?highlight=sasl#qpid-with-username-and-password-authentication

Comment 4 bugzilla 2014-11-04 09:17:47 UTC
The support is missing because it is not part of the installation description in the documentation I think.
This bug is mainly about the documentation on the pulp website not reflecting the actual actions to take to get it up and running than configuration or missing packages for the pulp installation itself.
Currently: no one following the documentation on the project side will be able to get to a running pulp server state just by following the step-by-step guide.

Comment 5 Brian Bouterse 2014-11-04 14:47:48 UTC
I looked back through the docs for 2.4, and I agree it doesn't identify the cyrus-sasl-plain explicitly as being a requirement. It does say that either auth needs to be disabled, or you should configure SASL and it refers the user to the upstream Qpid docs. Any user who follows those recommendations will end up with a working system (and many users have).

Regarding this being a documentation bug: cyrus-sasl-plain will only affect 2.4 and 2.5.0 but not 2.5.1 or future versions of Pulp. If you want to make a "note" or "warning" (sphinx terms) in the installation guide [0] near step 2 and submit it as a PR to pulp/pulp that would be great. If you plan to do that, let me know and I can re-open the bug and assigned to you. Improvements are always welcome.

[0]: http://pulp-user-guide.readthedocs.org/en/2.4-release/installation.html#server