I just upgraded from 2.3 to 2.4. I merged my Pulp server's database
settings and left of the 2.4 settings as default. In order to use
pulp-admin commands using default SSL settings required I set
verify_ssl to False.
I'd like to use verify_ssl, but unsure how to go about this.
I use Puppet for
I just updated from 2.3 to 2.4.1 and ran into a few issues.
First issue I hit was the pulp-manage-db command fails. Below is the
output. I am unsure how to debug this.
# sudo -u apache pulp-manage-db
Loading content types.
/usr/lib/python2.6/site-packages/pulp/server/db/connection.py:133:
Greetings, I have a pulp server that has started giving me a range of problems
just recently. The history: this server had been running 2.3 for several
months without issues. Its been auto syncing yum repos from RHEL and other
sources and serving them to internal servers that we don't allow
Hi Trey,
On 09/25/2014 12:12 PM, Trey Dockendorf wrote:
I'd like to use verify_ssl, but unsure how to go about this.
I use Puppet for my infrastructure, and am comfortable re-using that
CA for Pulp, but unsure how to make that work in Pulp.
My other option would be to get a trusted SSL
Sorry for the 2 replies to myself, but I'm learning as I go and
figured I'd update the thread to my current status.
I found this bug report,
https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=1016612,
which is my exact problem. I rolled my VM back in oVirt that runs
pulp-server but
On 09/25/2014 03:29 PM, Trey Dockendorf wrote:
Is this a bug or is there some way to know if it was a flaw in my setup?
Do you know if you had srpms in your rpm collection? Did you ever upload
srpms as rpms, perhaps?
signature.asc
Description: OpenPGP digital signature
