Bug 1447963
| Summary: | Switching installation media (or source) back and forth corrupts initdamdisk/kernel | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Lukas Zapletal <lzap> |
| Component: | TFTP | Assignee: | Shimon Shtein <sshtein> |
| Status: | CLOSED ERRATA | QA Contact: | Roman Plevka <rplevka> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3.0 | CC: | bkearney, ddolguik, gapatil, inecas, jcallaha, lzap, mmccune, pcreech, peter.vreman |
| Target Milestone: | 6.5.0 | Keywords: | FieldEngineering, PrioBumpField, PrioBumpGSS, PrioBumpPM, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://projects.theforeman.org/issues/19389 | ||
| Whiteboard: | hotfix, hotfix_delivered | ||
| Fixed In Version: | Doc Type: | Release Note | |
| Doc Text: |
Satellite 6.5 is changing naming conventions of kernel and initramdisk in TFTP folder. It was previously based operating system name, version and architecture:
boot/Redhat-6.1-x86_64-vmlinuz
boot/Redhat-6.1-x86_64-initrd.img
However this was causing issues when operating system variant (Server, Workstation) was changed leading to corrupted files. The new naming convention is based on installation media or repository name followed by hash of URL:
boot/CentOS_mirror-aBsbsZ_lDn-vmlinuz
boot/CentOS_mirror-aBsbsZ_lDn-initrd.img
Note when a content is promoted to a new content view, the URL changes therefore new pair of files is downloaded. This is expected behavior, more files will appear in the TFTP folder compared to previous naming scheme.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-05-14 12:36:19 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: | 1122832, 1459226 | ||
|
Description
Lukas Zapletal
2017-05-04 10:27:25 UTC
WORKAROUND: Locate http_download.rb file in /usr/share/foreman-proxy directory and remove "-c" (continue) flag. https://github.com/theforeman/smart-proxy/blob/933f2b096a8474538915a1edefadfb8f5e757a0d/lib/proxy/http_download.rb Lukas, it doesn't appear there is any solid upstream patch for this yet? Can you confirm if the workaround is suitable for a real fix? Sup Mike, upstream did not much like the idea of adding temporary setting for wget to be able to remove faulty "-c" option. On the other hand, there is a associated ticket which solves this problem in a nicer way and it is Pending Merge: http://projects.theforeman.org/issues/19389 I am now associating this with this BZ and closing the original issue. This problem can also happen when there is kernel/initramdisk update from Red Hat release engineering (it rarely happens). *** Bug 1571290 has been marked as a duplicate of this bug. *** Upstream bug assigned to sshtein Upstream bug assigned to sshtein I don't think the change we are talking about is back-portable to 6.3 (or even 6.4) Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19389 has been resolved. VERIFIED on sat6.5.0 snap #19 i enabled & synced (immediate dl policy) both Rhel 7.5 Workstation & Server kickstart repos. - then i provisioned a rhel server host and after that a rhe lworkstation host: [root@sat-6-5-qa-rhel7 boot]# pwd /var/lib/tftpboot/boot [root@sat-6-5-qa-rhel7 boot]# ll total 119016 -rw-r--r--. 1 foreman-proxy foreman-proxy 54525200 Mar 13 13:45 red-hat-enterprise-linux-7-server-kickstart-x86_64-7-5-29-initrd.img -rw-r--r--. 1 foreman-proxy foreman-proxy 6381872 Mar 13 13:44 red-hat-enterprise-linux-7-server-kickstart-x86_64-7-5-29-vmlinuz -rw-r--r--. 1 foreman-proxy foreman-proxy 54572776 Mar 13 13:54 red-hat-enterprise-linux-7-workstation-kickstart-x86_64-7-5-30-initrd.img -rw-r--r--. 1 foreman-proxy foreman-proxy 6381872 Mar 13 13:54 red-hat-enterprise-linux-7-workstation-kickstart-x86_64-7-5-30-vmlinuz both hosts got provisioned properly 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/RHSA-2019:1222 |