Bug 1498924
| Summary: | [RFE] When using a lazy-sync kickstart, prevent or show error when trying to provision a new host with that medium | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Billy Holmes <biholmes> | ||||||||||||
| Component: | Content Management | Assignee: | Partha Aji <paji> | ||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | jcallaha | ||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 6.3.0 | CC: | bbuckingham, bkearney, cwelton, ddolguik, ehelms, inecas, jswensso, kbidarka, paji, peter.vreman | ||||||||||||
| Target Milestone: | Unspecified | Keywords: | FutureFeature, Triaged | ||||||||||||
| Target Release: | Unused | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | tfm-rubygem-katello-3.4.5.55-1,foreman-proxy-1.15.6.4-1 | Doc Type: | If docs needed, set a value | ||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2018-02-21 16:54:17 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: | |||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Billy Holmes
2017-10-05 14:48:44 UTC
Tested with Sat6.3.0-snap32.0 Provisioned a RHEL7 Host with on-demand/lazy-sync and provisioning/PXE_boot of the Host was successful. I had faced this issue under these conditions earlier and would be a good thing to ensure, that we are not hitting this issue under these conditions. 1) If the manifest which is imported being used elsewhere, there is a chance of the manifest getting expired, after a certain period. 2) So, if one tries to Provision a Host after the manifest is expired, one wouldn't be able to download content from cdn.redhat.com, here it being initrd/vmlinuz files. 3) IT usually takes few hrs to days before the manifest gets expired, though me not an expert in this area. Let me see how it goes after keeping this setup running for few days ( without importing the manifest anywhere else ) and then trying to provision a new host once again. [root@qe-sat6-setup boot]# ll RedHat* -rw-r--r--. 1 foreman-proxy foreman-proxy 49763300 Jul 11 2017 RedHat-7.4-x86_64-initrd.img -rw-r--r--. 1 foreman-proxy foreman-proxy 5875184 Jul 6 2017 RedHat-7.4-x86_64-vmlinuz Connecting redmine issue http://projects.theforeman.org/issues/22292 from this bug Connecting redmine issue http://projects.theforeman.org/issues/22318 from this bug Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22318 has been resolved. Verified in Satellite 6.3 Snap 35. I had no issues when provisioning a RHEL 7.4 Server host using an on_demand kickstart repo. See attached images for verification. Created attachment 1392815 [details]
on_demand kickstart repo
Created attachment 1392816 [details]
verification screenshot 1
Created attachment 1392817 [details]
verification screenshot 2
Created attachment 1392818 [details]
verification screenshot 3
Created attachment 1392819 [details]
verification screenshot 4
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-2018:0336
|