Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1360954 - Satellite 5.7 satellite-sync rhel7 parents channels failed for http 403 error
Summary: Satellite 5.7 satellite-sync rhel7 parents channels failed for http 403 error
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Satellite Synchronization
Version: 570
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Tomáš Kašpárek
QA Contact: Red Hat Satellite QA List
Depends On:
TreeView+ depends on / blocked
Reported: 2016-07-28 02:10 UTC by yanpliu
Modified: 2016-07-28 03:08 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-07-28 03:08:15 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description yanpliu 2016-07-28 02:10:28 UTC
Description of problem:
satellite-sync rhel7 parents channels failed for http 403 error.

Version-Release number of selected component (if applicable):
Satellite server: Satellite5.7

How reproducible:

Steps to Reproduce:
1.Setup a Satellite5.7 server
2.Satellite rhel7 channels
# satellite-sync -c rhel-ppc64-server-7
# satellite-sync -c rhel-ppc64-server-7

3:40:16 Red Hat Satellite - live synchronization
03:40:16    url:
03:40:16    debug/output level: 1
03:40:16    db:  rhnuser/<password>@rhnschema

09:53:29 Downloading kickstartable trees files
09:53:29    Retrieving / parsing kickstart tree files: rhel-ppc64-server-7 (8343)
Downloading:09:53:35 ERROR: http error code :403; fault code: 0;
+++ sending log as an email +++

Actual results:
satellite-sync channels failed.

Expected results:
satellite-sync channels should work well.

Additional info:

Comment 1 yanpliu 2016-07-28 03:08:15 UTC
Will open a ticket instead of this bug.

Note You need to log in before you can comment on or make changes to this bug.