Bug 1699097
| Summary: | Error when creating hosts with Infoblox DHCP and non-Infoblox DNS | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Perry Gagne <pgagne> |
| Component: | Infoblox integration | Assignee: | Lukas Zapletal <lzap> |
| Status: | CLOSED NOTABUG | QA Contact: | Radovan Drazny <rdrazny> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.5.0 | CC: | lzap |
| Target Milestone: | Unspecified | Keywords: | Triaged |
| 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: | Environment: | ||
| Last Closed: | 2020-01-20 10:49:37 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: | |||
Does setting the record type to fixedaddress fixes this? What is the point of creating a host record when configure_for_dns is set to false? clearing the needinfo on this. The issue here was due to the earlier confusion wrt what record type to use. Uses fixedaddress avoids this issue. Lzap, do you see any reason to leave this open. If not we can probably close it. Nah, thanks. |
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Configure satellite or capsule with Infoblox DHCP 2. Configure non-Infoblox DNS (like ISC) 3. Create a host Actual results: Error in proxy.log 2019-04-11T14:27:56 d379428e [E] Error: 400 { "Error": "AdmConDataError: None (IBDataConflictError: IB.Data.Conflict:The action is not allowed. A parent was not found.)", "code": "Client.Ibap.Data.Conflict", "text": "The action is not allowed. A parent was not found." } Expected results: Host is created Additional info: Infoblox WAPI Host record object seems to have an option called "configure_for_dns" that appears to fix this. I edited build_host to add: ost.configure_for_dns = false and was able to create the host successfully. We should look into this more to see if we can use it in this scenario.