Bug 1150293
| Summary: | Kickstart tree doesn't appear in ks after sync repo/channel using --sync-kickstart | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Community] Spacewalk | Reporter: | Waldirio M Pinheiro <waldirio.pinheiro> | ||||
| Component: | Server | Assignee: | Michael Mráka <mmraka> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Red Hat Satellite QA List <satqe-list> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 2.2 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-10-08 13:20:51 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: | 1484117 | ||||||
| Attachments: |
|
||||||
Command used during the test spacewalk-repo-sync -crepo1 --url=http://mirror.globo.com/centos/6.5/os/x86_64/ --sync-kickstart You have to create a kickstart distribution first. See e.g. https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.6/html/Getting_Started_Guide/chap-Getting_Started_Guide-System_Provisioning.html#sect-Reference_Guide-Introduction_to_Kickstart-Kickstart_Explained This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug. |
Created attachment 944758 [details] Image with messages Description of problem: After create a repo/base channel and sync with flag "--sync-kickstart" checked (via cli or webUi), I can't see the kickstart tree when creating a new ks profile. IMHO should appear automatically the structure of the OS that we had a complete download/sync. That´s correct ?! Version-Release number of selected component (if applicable): 2.2 How reproducible: 100% Steps to Reproduce: 1. Create a new repo 2. Create a new channel and link with repo 3. Syncronize the channel 4. After complete, try to create a new ks profile Actual results: In Base Channel appear: No Kickstartable Channel found. In Kickstartable Tree: No trees were found for the selected channel Expected results: Show the ks structure for the version that was realized the download/sync, for example, CentOS6.5 Additional info: I can create the structure manually and works fine, but I really believe, just selecting the option --sync-kickstart should works. That's correct ?! Appreciate your help. Waldirio