Bug 1527338
| Summary: | Satellite-clone fails with mandatory parameters warning message. | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | maneesh verma <mverma> |
| Component: | Satellite Clone | Assignee: | John Mitsch <jomitsch> |
| Status: | CLOSED ERRATA | QA Contact: | sthirugn <sthirugn> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.3.0 | CC: | bbuckingham, bkearney, cmarinea, hprakash, mmccune, sthirugn, swadeley |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-02-19 17:23:44 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Comment 1
John Mitsch
2017-12-19 14:51:04 UTC
I think we should make sure to prioritize the following BZ which would prevent this situation. Satellite Installation Guides are never stipulating to use Activation Key, thus the registration is expected to have been done manually so we should not be having to explicitly change the variable. https://bugzilla.redhat.com/show_bug.cgi?id=1519515 Thanks Cristian, We have an upstream issue around this https://github.com/RedHatSatellite/satellite-clone/issues/285 *** Bug 1527288 has been marked as a duplicate of this bug. *** Verified in satellite-clone-1.2.1-1.el7sat.noarch Now the default behavior is manual registration to portal. The default workflow is: 1. Manually register to portal and attach right subscriptions 2. copy backup files 3. install satellite-clone 4. Run satellite-clone Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0330 |