Jira (PUP-2887) IPv6 failover using srv records doesn't work as expected

9 views
Skip to first unread message

Vladimir Kotal (JIRA)

unread,
Jan 12, 2016, 10:33:04 AM1/12/16
to puppe...@googlegroups.com
Vladimir Kotal commented on Bug PUP-2887
 
Re: IPv6 failover using srv records doesn't work as expected

Encountering the same on Solaris 11.3. The client has IPv4 and IPv6 addresses but broken IPv6 connectivity. What happens is this:

{{# puppet agent --test --server=puppet.foo.cz
Warning: Unable to fetch my node definition, but the agent run will continue:
Warning: execution expired
Info: Retrieving pluginfacts
Error: Could not retrieve pluginfacts: execution expired
Info: Retrieving plugin
...
}}

Ideally, the connect should be using something like Happy eyeballs algorithm (RFC 6555) so that it does not stall for too long.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Atlassian logo

Branan Riley (JIRA)

unread,
May 16, 2017, 3:25:04 PM5/16/17
to puppe...@googlegroups.com
Branan Riley updated an issue
 
Puppet / Bug PUP-2887
Change By: Branan Riley
Labels: IPv6 SRV  help_wanted
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Atlassian logo

Branan Riley (JIRA)

unread,
May 16, 2017, 3:26:03 PM5/16/17
to puppe...@googlegroups.com
Branan Riley commented on Bug PUP-2887
 
Re: IPv6 failover using srv records doesn't work as expected

We're unlikely to tackle this soon, but I'm leaving it open. PRs would be happily accepted.

Josh Cooper (JIRA)

unread,
May 16, 2017, 5:24:03 PM5/16/17
to puppe...@googlegroups.com
Josh Cooper updated an issue
 
Change By: Josh Cooper
Labels: IPv6  SRV  help_wanted

Josh Cooper (JIRA)

unread,
May 16, 2017, 5:24:04 PM5/16/17
to puppe...@googlegroups.com
Josh Cooper assigned an issue to Unassigned
Change By: Josh Cooper
Assignee: Kylo Ginsberg

Josh Cooper (JIRA)

unread,
May 16, 2017, 5:41:02 PM5/16/17
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Labels: IPv6 help_wanted  triaged

Moses Mendoza (JIRA)

unread,
May 18, 2017, 1:44:48 PM5/18/17
to puppe...@googlegroups.com
Moses Mendoza updated an issue
Change By: Moses Mendoza
Labels: IPv6 help_wanted  triaged

Jacob Helwig (JIRA)

unread,
Dec 5, 2017, 12:02:02 PM12/5/17
to puppe...@googlegroups.com
Jacob Helwig updated an issue
Change By: Jacob Helwig
Sub-team: Coremunity
This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)
Atlassian logo

Jorie Tappa (JIRA)

unread,
Jul 8, 2019, 2:41:04 PM7/8/19
to puppe...@googlegroups.com
Jorie Tappa updated an issue
Change By: Jorie Tappa
Sprint: Coremunity Hopper
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Josh Cooper (JIRA)

unread,
Sep 6, 2019, 1:09:04 PM9/6/19
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-2887
 
Re: IPv6 failover using srv records doesn't work as expected

One difficulty with implementing happy eyeballs is that Net::HTTP only accepts a hostname or IP to connect to, and always performs SSL verification against that value. If we pass a hostname, then ruby looks up the ipv6 or v4 address, and uses the first one it can connect to. If we pass the IP address, then verification of the server's SSL cert will likely fail. I say likely because it's possible to add the server's IP address as a subject alt name, but that's not very common.

To implement happy eyeballs we could either:

  • call Net::HTTP.start with both the IP address (v4 or v6) and fqdn, where SSL verification happens against the latter. This would require an upstream ruby PR.
  • override the SSL verification callback and do the post_connection_check ourselves.

Josh Cooper (JIRA)

unread,
Sep 13, 2019, 11:59:03 AM9/13/19
to puppe...@googlegroups.com

Josh Cooper (JIRA)

unread,
Sep 13, 2019, 12:02:05 PM9/13/19
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Sprint: Coremunity Hopper

Josh Cooper (Jira)

unread,
Feb 16, 2021, 2:06:03 PM2/16/21
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-2887
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages