Loving that pulp integrates this now. However, when I set this to true on a
repository, the publish always fails. Maybe a missing Python module?
>From the publish command:
Task Failed
'ascii' codec can't decode byte 0xa0 in position 51051: ordinal not in
range(128)
# journalctl SYSLOG_IDENTIFIE
ot; functionality was the main reason I upgraded,
but I think I'm going to have to go back to 2.6.3 until things stabilize.
Reece
On 9/16/15, 2:56 PM, "Webb, Reece" wrote:
>Thanks Randy, the CDN/metadata errors aren't showing up right now, so maybe it
>was just a
7;t return. And if there's any
other info I can provide to help get the email issue resolved, please let me
know.
Reece
On 9/16/15, 2:39 PM, "Randy Barlow" wrote:
>Webb, Reece wrote:
>> Thanks, I upgraded from 2.6.3. As I said in my last follow-up email,
sks:INFO: Task failed :
[af75f802-8ea8-4285-8c47-ce5671ea0316] : Error retrieving metadata: Not found
Sep 16 18:17:48 yummy pulp: celery.worker.job:INFO: Task
pulp.server.managers.repo.sync.sync[af75f802-8ea8-4285-8c47-ce5671ea0316]
raised expected: PulpCodedException()
Sep 16 18:17:48 yummy pulp
If I delete and recreate the repository, sync/publish works. So I guess
something isn't getting updated correctly?
Reece
On 9/16/15, 8:28 AM, "Webb, Reece" wrote:
>I just upgraded from 2.6.3 on RHEL 7.1, using the upgrade instructions
>provided in the release notes. I
I just upgraded from 2.6.3 on RHEL 7.1, using the upgrade instructions provided
in the release notes. I'm now unable to sync or publish. I tried running the
sync with the "-v", but it says the option doesn't exist...
# pulp-admin rpm repo sync run --repo-id rad-epel-7
+--
ilto:gavin...@gmail.com>> wrote:
hey Josh / Reece,
I hate to say I am glad, I am not the only one with this issue. Did anyone on
#Pulp speak about the issue?
Let us know how you go with troubleshooting this.
Thanks
On Wed, May 6, 2015 at 3:22 AM, Webb, Reece
mailto:reece.w...@ucsf.ed
hat you need to do:
>
>
>
>$ pulp-admin rpm repo update --checksum=sha1 --repo-id=repo
>
>$ pulp-admin rpm repo publish run --repo-id=repo
>
>
>
>Thanks,
>
>
>
>Josh
>
>
>
>
>From: pulp-list-boun...@redhat.com [ mailto:pulp-list-boun...@redh
I have seen this issue for months, a sync fails 9 times out of 10. It appears
to be an issue (for me at least) on the Redhat side of things. I use curl to
get more info.
I’ll run it one time and get a failure:
# curl -v —key ./Workstation-Entitlement.pem --cert
./Workstation-Entitlement.pem -k
-list-boun...@redhat.com>
[mailto:pulp-list-boun...@redhat.com] On Behalf Of Webb, Reece
Sent: Monday, May 04, 2015 4:41 PM
To: Pulp-list@redhat.com<mailto:Pulp-list@redhat.com>
Subject: [Pulp-list] syncing RHEL5 repositories
I’m able to sync RHEL5 repositories to Pulp 2.6.1, but I get
I’m able to sync RHEL5 repositories to Pulp 2.6.1, but I get a checksum error
when I try a ‘yum update’ on a RHEL5 host:
[Errno -3] Error performing checksum
I found a few threads from a couple of years ago stating that this was
apparently an issue with the repository being published with sha25
pulp-rpm-plugins-2.6.0-0.8.rc.el7.noarch
python-pulp-bindings-2.6.0-0.10.rc.el7.noarch
pulp-selinux-2.6.0-0.10.rc.el7.noarch
On 3/23/15, 10:50 AM, "Webb, Reece" wrote:
>I’ve been having failures syncing with certain RH repositories as well. For
>me, it’s the 7Workstation an
I’ve been having failures syncing with certain RH repositories as well. For me,
it’s the 7Workstation and 5Client repo’s (7Server doesn’t have any problems). I
get a “Forbidden”, which would seem to indicate a problem with the cert… but
this sync problem is intermittent. If I manually kick off a
13 matches
Mail list logo
