[Pulp-list] PulpDataException with pulp-admin rpm repo update

[Ashby, Jason (IMS)]

Hi Randy,
I had changed protected_repo_listing_file in /etc/pulp/repo_auth.conf to a custom path and you're right that my permissions were incorrect.  I ran chmod 755 on the content directory and all looks good now!  Many thanks.

I'll file a bug with this info and mark it as resolved.  This is the url correct?:   https://bugzilla.redhat.com/enter_bug.cgi?product=Pulp

-----Original Message-----
From: pulp-list-bounces at redhat.com [mailto:pulp-list-bounces at redhat.com] On Behalf Of Randy Barlow
Sent: Tuesday, March 25, 2014 4:24 PM
To: pulp-list at redhat.com
Subject: Re: [Pulp-list] PulpDataException with pulp-admin rpm repo update

Ashby, Jason (IMS) wrote:
>    File
> "/usr/lib/python2.6/site-packages/pulp_rpm/repo_auth/protected_repo_utils.py",
> line 155, in save
>
>      f = open(self.filename, 'w')
>
> PulpDataException: Pulp exception occurred: PulpDataException

Hi Jason,

This permission denied error is actually a Linux permission denied on
your protected repos file. In /etc/pulp/repo_auth.conf, there should be
a setting in the [repos] section for protected_repo_listing_file. Apache
will need write permissions to that path. Can you check the permissions?

If the permissions are not solid, can you comment back on whether you
have adjusted FS permissions, or whether these are the stock
permissions? It's possible that our spec file has these permissions wrong.

Also, it would be helpful if you could file a bug on the error reporting
here. It wasn't easy to determine what was causing the problem!

--
Randy Barlow
Raleigh, NC, USA

_______________________________________________
Pulp-list mailing list
Pulp-list at redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

________________________________

Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error.