Bug 1388112
| Summary: | Fedora distribution isn't shown in wizard of creating kickstart profile | ||
|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Pavel StudenÃk <pstudeni> |
| Component: | Server | Assignee: | Gennadii Altukhov <galtukho> |
| Status: | CLOSED ERRATA | QA Contact: | Radovan Drazny <rdrazny> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 570 | CC: | galtukho, jdobes, rdrazny, tlestach |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | spacewalk-java-2.3.8-156 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-02-01 15:55:34 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1368978, 1391420 | ||
|
Description
Pavel StudenÃk
2016-10-24 13:35:59 UTC
Taking... fixed in upstream, spacewalk.git: dc6ca0ffcc7a337a965e5959b085f9e58fa7aa73 Switching to modified... Reproduced on spacewalk-java-2.3.8-155 using the reproducer from the initial report. I have created a Fedora base channel, assigned a Fedora repo to it, and synced the repo. Fedora distribution was present, but when creating a new kickstart profile, there was no Fedora channel present it the list of available base channels. Updated to spacewalk-java-2.3.8-157, restarted the Satellite server, and started creation of a new kicktart profile again. This time there was Fedora channel present in the list of available base channels, and it was possible to create a new kickstart profile based on the Fedora kickstart tree and base channel. VERIFIED 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://rhn.redhat.com/errata/RHBA-2017-0236.html |