| Summary: | New client kickstart failed if child channel is not cached in /var/cached/rhn | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | DzungDo <ddo> | ||||
| Component: | Provisioning | Assignee: | Jan Dobes <jdobes> | ||||
| Status: | CLOSED DEFERRED | QA Contact: | Red Hat Satellite QA List <satqe-list> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 560 | CC: | dyordano, tlestach | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1007319 (view as bug list) | Environment: | |||||
| Last Closed: | 2018-04-09 09:13:13 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: | |||||
| Bug Depends On: | |||||||
| Bug Blocks: | 462714 | ||||||
| Attachments: |
|
||||||
Having the kickstart wait for the repodata to be available is not really feasible. Depending on how big the channel is, how fast your satellite is, how many other channels have metadata regenerating, if taskomatic is running or not, etc, the metadata may not be available for a very long time. However, it is reasonable to ask that we begin the process of generating the metadata, so that maybe the next time the user tries the kickstart it will work. That is now the process works currently for registered clients - the first client that requests non-existent metadata will get a 404, but we'll also start generating it so that the next time will work. Should there be somewhere in the documentation that tells people how to deal with this if it comes up? Probably extremely uncommon. So the use case where ddo hit this: 1) Install an new server from scratch, install Sat 5.6 on it 2) Upgrade / migrate over an old 5.5 database from a different machine 3) Try to kickstart a server Currently nothing triggers metadata regeneration in that path, so the kickstarts will keep failing with a 404. Resetting to default owner. 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. |
Created attachment 796469 [details] screenshot Description of problem: Kickstart profile has base and child channel. When kickstart new client, kickstart failed with the "404 Not Found" error as it could not locate repomd.xml file belonging to the child channel. Version-Release number of selected component (if applicable): Satellite 5.6 How reproducible: Always Steps to Reproduce: 1. Assign child channel "rhn-tools-rhel-x86_64-server-6" to a kickstart profile 2. Remove this directory from /var/cache/rhn 3. Kickstart a client Actual results: Kickstart failed because the directory does not exist. If we run the following command to build the cache, then kickstart will complete: # spacewalk-api --user=satadmin --server=$HOSTNAME channel.software.regenerateYumCache %session% rhn-tools-rhel-x86_64-server-6 Expected results: If /var/cache/rhn/rhn-tools-rhel-x86_64-server-6/ does not exist, kickstart fails. We want kickstart process to wait while /var/cache/rhn/rhn-tools-rhel-x86_64-server-6/ builds instead of error-ing out. Additional info: