Bug 1472382
Summary: | discovery provision endpoint misses the pxe_loader option | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Roman Plevka <rplevka> |
Component: | Discovery Plugin | Assignee: | Rahul Bajaj <rabajaj> |
Status: | CLOSED ERRATA | QA Contact: | Roman Plevka <rplevka> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3.0 | CC: | bbuckingham, bkearney, ehelms, kgaikwad, lzap, rabajaj |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | foreman_discovery-9.1.3 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-21 17:30:09 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: |
Description
Roman Plevka
2017-07-18 15:23:57 UTC
Lukas, thoughts on this one? Should it be addressed in 6.3? Yes we are not there yet, broken tests in discovery upstream. THe other one will be CLI, if needed. Might be only one. We have a PR fix for unit tests now in discovery, merging today and then will push the PR this week. https://github.com/theforeman/foreman/pull/4864 @Lukas, will create a redmine issue for the missing CLI and will fix it in the meanwhile time :) commit 590d811374dea734ea4c23a78c4a2d50bf60cc4d Author: Rahul Bajaj <rahulrb0509> AuthorDate: Wed Sep 6 11:58:53 2017 +0000 Commit: Lukas Zapletal <lzap+git> CommitDate: Wed Oct 4 09:12:23 2017 +0200 Fixes #20337 - Add pxe loader into discovery v2 API (cherry picked from commit 38de3404134ad99111c62aa2e2159a0d8bbcddfb) VERIFIED on sat6.3.0-19 tested all options and they correctly deploy files and update dhcp.lease file, pointing the host to the correct loader. 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 |