Bug #17187
closed
IPv6 address cannot be blank for CR providing IPv4 plus domain with forward DNS
Description
When creating a host (using EC2) it insists that the ipv6 address must be filled in.
This is preventing us from building new hosts, as we have no ipv6 support. (Even if ::1 is used, it fails when trying to add the DNS records.)
There are no ipv6 subnets configured and retrying with the blank address results in the same error.
Files
| foreman-ipv6-2.png | View foreman-ipv6-2.png | 13.6 KB | |||
| foreman-ipv6-1.png | View foreman-ipv6-1.png | 43.9 KB | |||
| foreman-ipv6.png | View foreman-ipv6.png | 32.9 KB |
Updated by Dominic Cleal about 8 years ago
- Translation missing: en.field_release set to 203
What is the value of token_duration in Settings? If zero, try specifying a non-zero value (the default).
Edit: actually, that may not be the issue - if a domain with forward DNS is configured, it would probably trigger the same condition, requiring an IPv6 address.
I think #17071 may contain a fix for this, it improves how IP address validations are skipped when a compute resource provides one of the IPs (e.g. it'd properly skip IPv6 address validation when EC2 provides an IPv4 address).
Updated by Dominic Cleal about 8 years ago
- Related to Feature #14664: Add IPv6 Subnet to Host, Hostgroup and Nic Models added
Updated by Dominic Cleal about 8 years ago
- Related to Bug #17071: IPv6 address incorrectly required with EUI-64 when mac is provided by compute resource added
Updated by Dominic Cleal about 8 years ago
Is a domain set on the interface with a forward DNS proxy set? (I assume so, since you mention DNS in passing.)
Updated by Dis McCarthy about 8 years ago
Dominic Cleal wrote:
Is a domain set on the interface with a forward DNS proxy set? (I assume so, since you mention DNS in passing.)
Yes. We're doing forward/reverse management in ipv4 (with freeipa, which for this purpose can be treated as bind9 with a bunch of wrappers)
Updated by Dominic Cleal about 8 years ago
- Subject changed from IPV6 address cannot be blank to IPv6 address cannot be blank for CR providing IPv4 plus domain with forward DNS
- Category changed from Unattended installations to Host creation
Updated by Dis McCarthy about 8 years ago
- File foreman-ipv6.png foreman-ipv6.png added
Just as an additional datapoint, attached is the error when using ::1 for ipv6
Proxy logs (1.11.4-1) show:
E, [2016-11-02T16:55:33.236719 #5470] ERROR -- : unrecognized 'type' parameter: AAAA
Updated by Timo Goebel about 8 years ago
- Assignee set to Timo Goebel
Dis McCarthy wrote:
Proxy logs (1.11.4-1) show:
You should definitely update your smart proxy to 1.13. Smart Proxy 1.11 is not fully compatible with Foreman 1.13.
As a temporary workaround, you can replace this (in /usr/share/foreman/app/models/nic/base.rb) with "return false"
https://github.com/theforeman/foreman/blob/1.13-stable/app/models/nic/base.rb#L166
Dominic, I'll send a pr with a patch so that we can include a fix in 1.13.2 . #17071 seems a little to big to backport.
Updated by The Foreman Bot about 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3988 added
Updated by Timo Goebel about 8 years ago
Dis McCarthy wrote:
That replacement worked.
Thanks!
Great, would you mind testing the actual patch for this?
wget -O /tmp/17187.patch https://github.com/theforeman/foreman/pull/3988.patch
cd /usr/share/foreman
patch -p1 < /tmp/17187.patch
systemctl restart httpd.service
patch will be unable to find the unit test file, you can safely skip this patch.
Of course, you'll need to revert the hotfix first.
Updated by Timo Goebel about 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset f77f6b91955a79e80aa1c9dc04e6ce8b0716493a.
Updated by Dominic Cleal about 8 years ago
- Has duplicate Bug #17276: Creating new host to be deployed on EC2 fails no lack of IPv6 Interface added