Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts

51 views
Skip to first unread message

Hadmut Danisch (JIRA)

unread,
Feb 7, 2019, 5:35:03 AM2/7/19
to puppe...@googlegroups.com
Hadmut Danisch created an issue
 
Puppet / Improvement PUP-9480
puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Issue Type: Improvement Improvement
Affects Versions: PUP 5.4.0
Assignee: Unassigned
Created: 2019/02/07 2:34 AM
Priority: Normal Normal
Reporter: Hadmut Danisch

Hi,

an old problem, known at least since 2011, still exists in puppet and is causing more and more trouble: the host resource and put a host into /etc/hosts with either its ipv4 or ipv6 address, but not with both.

Since it is state of the art today and normal that machines have both addresses, this really causes headache and problems.

 

I wonder why a problem know for at least 8 years still exists, if

https://puppet.com/docs/puppet/5.5/types/host.html

is still correct.

 

regards

 

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Hadmut Danisch (JIRA)

unread,
Feb 7, 2019, 5:38:03 AM2/7/19
to puppe...@googlegroups.com
Hadmut Danisch commented on Improvement PUP-9480
 
Re: puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts

BTW, the host resource seems to be somewhat broken by design, since the leading entity and key in /etc/hosts is the ip address and not the host name.

 

A better way would be to bind host names to ip addresses and not ip addresses to host names.

Rob Braden (JIRA)

unread,
Feb 8, 2019, 4:26:04 PM2/8/19
to puppe...@googlegroups.com

Geoff Nichols (JIRA)

unread,
Feb 19, 2019, 1:40:04 PM2/19/19
to puppe...@googlegroups.com

Geoff Nichols (JIRA)

unread,
May 15, 2019, 1:12:02 PM5/15/19
to puppe...@googlegroups.com

Geoff Nichols (JIRA)

unread,
May 15, 2019, 1:13:04 PM5/15/19
to puppe...@googlegroups.com
Geoff Nichols assigned an issue to Unassigned
Change By: Geoff Nichols
Assignee: Geoff Nichols

Josh Cooper (JIRA)

unread,
May 17, 2019, 12:22:03 AM5/17/19
to puppe...@googlegroups.com

Rob Braden (JIRA)

unread,
Jun 10, 2019, 2:35:05 PM6/10/19
to puppe...@googlegroups.com
Rob Braden updated an issue
Change By: Rob Braden
Sprint: Coremunity Grooming

Jorie Tappa (JIRA)

unread,
Jun 12, 2019, 5:08:03 PM6/12/19
to puppe...@googlegroups.com
Jorie Tappa updated an issue
Change By: Jorie Tappa
Acceptance Criteria: Because this type was part of the T&P extraction in Puppet 6, it needs to both be updated in the code in 5.5.x, as well as the extracted module.

Jorie Tappa (JIRA)

unread,
Jul 8, 2019, 2:45:02 PM7/8/19
to puppe...@googlegroups.com
Jorie Tappa updated an issue
Change By: Jorie Tappa
Sprint: Coremunity Grooming Hopper

Kris Bosland (JIRA)

unread,
Aug 22, 2019, 2:30:04 PM8/22/19
to puppe...@googlegroups.com
Kris Bosland updated an issue
Change By: Kris Bosland
Sprint: Coremunity Hopper Platform Core KANBAN

Kris Bosland (JIRA)

unread,
Aug 22, 2019, 2:30:06 PM8/22/19
to puppe...@googlegroups.com

Kris Bosland (JIRA)

unread,
Aug 26, 2019, 6:47:03 PM8/26/19
to puppe...@googlegroups.com
Kris Bosland commented on Improvement PUP-9480
 
Re: puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts

The hosts file implementation can deal with both IPv4 and IPv6:

kris.bosland@kris:puppet % cat ../tmp/pup-9480/apply.pp
host { 'dummy.ipv.4':
  ensure => 'present',
  ip     => '192.168.2.1',
  target => '/Users/kris.bosland/work/tmp/pup-9480/hosts',
}
host { 'dummy.ipv.6':
  ensure => 'present',
  ip     => '::2',
  target => '/Users/kris.bosland/work/tmp/pup-9480/hosts',
}
kris.bosland@kris:puppet % bx puppet apply ../tmp/pup-9480/apply.pp                                              Notice: Compiled catalog for kris.bosland-c02kf9eafft1 in environment production in 0.07 seconds
Notice: Applied catalog in 0.01 seconds
kris.bosland@kris:puppet % cat ../tmp/pup-9480/hosts                                                            
# HEADER: This file was autogenerated at 2019-08-26 10:53:44 -0700
# HEADER: This file was autogenerated at 2019-08-26 10:53:44 -0700
# HEADER: by puppet.  While it can still be managed manually, it
# HEADER: is definitely not recommended.
255.255.255.255 broadcasthost
127.0.0.1 localhost
::2 dummy.ipv.6
127.0.0.1 puppet.delivery.puppetlabs.net
127.0.0.1 kubernetes.docker.internal
192.168.2.1 dummy.ipv.4
kris.bosland@kris:puppet %

However, with the current host resource model, only one IP can be set for each host, so you cannot set both IPv4 and IPv6 addresses for the same hostname.

Kris Bosland (JIRA)

unread,
Aug 27, 2019, 3:28:03 PM8/27/19
to puppe...@googlegroups.com
Kris Bosland assigned an issue to Unassigned
 
Change By: Kris Bosland
Assignee: Kris Bosland

Jorie Tappa (JIRA)

unread,
Sep 6, 2019, 12:45:04 PM9/6/19
to puppe...@googlegroups.com
Jorie Tappa updated an issue
Change By: Jorie Tappa
Labels: IPv6
Sprint: Platform Core KANBAN Coremunity Hopper

Kris Bosland (JIRA)

unread,
Sep 6, 2019, 12:53:03 PM9/6/19
to puppe...@googlegroups.com
Kris Bosland commented on Improvement PUP-9480
 
Re: puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts

Jean Bond, is there some place that we are documenting IPv6 limitations and errata?  Because of existing limitations in the `host` type (unrelated to IPv6) this issue will not be fixed any time soon.

Jean Bond (JIRA)

unread,
Sep 6, 2019, 1:25:03 PM9/6/19
to puppe...@googlegroups.com
Jean Bond commented on Improvement PUP-9480

Kris Bosland, thanks for the heads up on this. We should add this as a known issue. If you could fill out the docs tab with a summary of the problem and what users should do about it, that would be very helpful.

Kris Bosland (JIRA)

unread,
Sep 6, 2019, 1:29:03 PM9/6/19
to puppe...@googlegroups.com
Kris Bosland updated an issue
 
Change By: Kris Bosland
Release Notes Summary: The host type only supports one IP address for each hostname.  Because of this, it does not support both an IPv4 and IPv6 address for the same hostname.
Release Notes: Known Issue

Kris Bosland (JIRA)

unread,
Sep 6, 2019, 1:30:04 PM9/6/19
to puppe...@googlegroups.com
Kris Bosland commented on Improvement PUP-9480
 
Re: puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts

Jean Bond updated.  I kept it pretty short, let me know if it needs more information.

Jean Bond (JIRA)

unread,
Sep 6, 2019, 3:51:04 PM9/6/19
to puppe...@googlegroups.com

Jean Bond (JIRA)

unread,
Sep 6, 2019, 3:52:04 PM9/6/19
to puppe...@googlegroups.com
Jean Bond commented on Improvement PUP-9480
 
Re: puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts

Looks pretty straightforward to me, thank you Kris Bosland!

Josh Cooper (JIRA)

unread,
Sep 13, 2019, 12:00:04 PM9/13/19
to puppe...@googlegroups.com

Rob Braden (JIRA)

unread,
Sep 24, 2019, 2:48:05 PM9/24/19
to puppe...@googlegroups.com

Austin Boyd (Jira)

unread,
Oct 12, 2020, 4:28:03 PM10/12/20
to puppe...@googlegroups.com
Austin Boyd updated an issue
Change By: Austin Boyd
Zendesk Ticket Count: 1
Zendesk Ticket IDs: 41481
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Austin Boyd (Jira)

unread,
Oct 12, 2020, 4:28:03 PM10/12/20
to puppe...@googlegroups.com
Austin Boyd updated an issue
Change By: Austin Boyd
Labels: jira_escalated known-issue-added

Josh Cooper (Jira)

unread,
Jun 14, 2021, 9:02:01 PM6/14/21
to puppe...@googlegroups.com
Josh Cooper commented on Improvement PUP-9480
 
Re: puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts

I'm moving this to the MODULES project because the host type and provider was removed in Puppet 6 and Puppet 5 is EOL.

This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages