Bug 1002079 - spacewalk-sync-setup should warn me about missing cert in case I'm running it on non-slave
spacewalk-sync-setup should warn me about missing cert in case I'm running it...
Status: CLOSED DEFERRED
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Satellite Synchronization (Show other bugs)
560
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Grant Gainey
Red Hat Satellite QA List
:
Depends On:
Blocks: sat560-triage
  Show dependency treegraph
 
Reported: 2013-08-28 08:55 EDT by Jan Hutař
Modified: 2018-04-09 05:09 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-09 05:09:48 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Hutař 2013-08-28 08:55:53 EDT
Description of problem:
When you run spacewalk-sync-setup on a different system than to-be-configured-as-slave, it should warn you that you are still not done, that you have to manually download master's cert to the slave.


Version-Release number of selected component (if applicable):
spacewalk-utils-2.0.2-8.el6sat.noarch


How reproducible:
always


Steps to Reproduce:
1. Prepare Sat1, Sat2 and Client3 (3 different systems)
2. Then running spacewalk-sync-setup from Client3 to setup ISS for Sat1
   and Sat2 do not prepares master certificate on a slave


Actual results:
No help to the user is provided


Expected results:
There should be warning printed that you still have to do another step - download master's CA cert to stave


Additional info:
Fix for this issue is probably not required for Sat560 release.
Comment 1 Tomas Lestach 2018-04-09 05:09:48 EDT
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.

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