Bug 1701075
| Summary: | Subnet is blank after provisioning a discovered host via customize Host form | |||
|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Jayant Bhatia <jbhatia> | |
| Component: | Discovery Image | Assignee: | Lukas Zapletal <lzap> | |
| Status: | CLOSED ERRATA | QA Contact: | Roman Plevka <rplevka> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 6.4.2 | CC: | ahumbe, lzap, rabajaj, roarora | |
| Target Milestone: | 6.9.0 | Keywords: | PrioBumpGSS, Regression, Reopened | |
| Target Release: | Unused | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1933163 (view as bug list) | Environment: | ||
| Last Closed: | 2021-04-21 13:11:48 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
Jayant Bhatia
2019-04-18 00:19:05 UTC
This works for me on 6.5, need to try on 6.4. We haven't changed any behavior for 6.4 in this regard, Satellite Server will try to find and match subnet reported by the discovered host as primary/provisioning IP address just as 6.3 did. When found, subnet is associated to the host and all communication goes through Discovery Capsule associated with the subnet. Then the Customize host works as well. Can you check taxonomy of your Subnet and Host? Paste screens of Host Organization and Location and then Subnet Org/Loc. I just tested this on 6.4. Make sure that the HOSTGROUP taxonomy matches SUBNET taxonomy. Reopening the bug as another customer is hitting this. I checked the taxonomy for hostgroup and subnet and its good. In discovered hosts page, subnet is detected fine but when provisioned and customized, the subnet is not there in the interface. This leads to failed kickstart fetch during build. Let me explain one important aspect of discovery. When a host is discovered in subnet A and then a hostgroup with subnet B is selected, provisioning will not work unless Customize Host button is pressed and IP address is updated (e.g. via Suggest new link) to match the selected Subnet from the hostgroup. Otherwise provisioning will fail with "IP does not match selected subnet". We are tracking a feature request to support this: https://github.com/theforeman/foreman_discovery/pull/306 Please provide reproducer because it works for me. This is still an issue on 6.6.1. This issue has been experienced since upgrading to Satellite 6.4. There is no subnet defined in the host group to which a discovered host is assigned when this has been known to occur. The host on the Discovered Hosts page correctly shows the detected subnet, but when navigating to its interface during its customization, this IPv4 Subnet is not selected (no value is selected). If forgotten or otherwise not manually set, the provisioning process will fail. Hello, only hostgroups with domain/subnet set can be used for discovery provisioning. The subnet for discovered hosts is not subnet that host should be provisioned in. It only helps to pick Discovery Capsule to use to proxy HTTPS requests when talking to discovered hosts. I will implement a warning or even hide hostgoups which has subnet set to blank to prevent confusion. This cannot be a regression, this has never worked a different way. You likely had a hostgroup which had domain/subnet set in the past. Anyway, it's a natural expectation to assume that subnet should carry over to provisioning phase, let's change this behavior. I have implemented this upstream, due to dependency on other rather big change (unused IP call during provisioning) this cannot be backported tho, will be part of future Satellite release. The host group configuration has not changed with regard to the domain/subnet configurations in our environment and the functionality DID change starting with version 6.4 of Satellite and has stopped working as it used to since. Let me change my statement to: if a hostgroup is selected and it has no subnet set, the discovered subnet did not carry over. However when provisioning was done without any hostgroup it did carry over. This is how I read the code today. Anyway, I have fixed this and the patch is now pending review. Once merged, we can ask backport into 6.7. WORKAROUND HOTFIX: Apply this change to https://github.com/theforeman/foreman_discovery/pull/495/files#diff-0e08314173f533a2b6e73218bc5d4b10 to app/controllers/discovered_hosts_controller.rb file and restart httpd. Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/29221 has been resolved. Fix is in Satellite 6.9 SNAP 1 with tfm-rubygem-foreman_discovery-16.3.1-1.el7sat.noarch VERIFIED on sat6.9.0-8.0 the subnet of the automatically discovered host is reported correctly and the same subnet is pre-selected in the customize host dialog during host provisioning 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 (Moderate: Satellite 6.9 Release), 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-2021:1313 |