Description of problem: Following documentation when you run final spacewalk-sync-setup command, error which is probably not important (as all seem to be setup correctly after that) is printed. Version-Release number of selected component (if applicable): spacewalk-utils-2.0.2-8.el6sat.noarch How reproducible: always Steps to Reproduce: 1. Have two satellites and attempt to configure ISS between them: # spacewalk-sync-setup --ss=<sat1> --sl=<sat1_admin> --sp=<sat1_pass> --ms=<sat2> --ml=<sat2_admin> --mp=<sat2_pass> --create-templates --apply Actual results: ERROR: /root/.spacewalk-sync-setup/slave.txt INFO: Connecting to <sat2_admin>@<sat1> INFO: Connecting to <sat1_admin>@<sat2> INFO: Generating master-setup file /root/.spacewalk-sync-setup/master.txt INFO: Generating slave-setup file /root/.spacewalk-sync-setup/slave.txt INFO: About to wget master CA cert: [wget -q -O /usr/share/rhn/<sat2>_RHN-ORG-TRUSTED-SSL-CERT http://<sat2>/pub/RHN-ORG-TRUSTED-SSL-CERT] INFO: Applying master-setup /root/.spacewalk-sync-setup/master.txt INFO: Applying slave-setup /root/.spacewalk-sync-setup/slave.txt # echo $? 0 Expected results: That error should not be there or should be more verbose as it is clear where is the problem Additional info: Reported after testing of bug 997021
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog. This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.