The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Bug #12517

Puppet Master IPv6 Only

Added by Zachary Crownover over 2 years ago. Updated 8 months ago.

Status:InvestigatingStart date:02/08/2012
Priority:HighDue date:
Assignee:-% Done:

50%

Category:-
Target version:-
Affected Puppet version: Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket is now tracked at: https://tickets.puppetlabs.com/browse/PUP-1139


Description

I’m having a reproducible error, whereby my master listens on 8140 for IPv6 only and my agent is unable to see or communicate to it, and I’m not sure how to force the master to operate on IPv4 or on both IPv4 and IPv6 or to force the agent to operate on IPv6, but until they’re in sync with each other I’m having errors.

image001.png (4.57 KB) Zachary Crownover, 05/31/2012 04:50 pm

smime.p7s (5.23 KB) Zachary Crownover, 05/31/2012 04:50 pm

History

#1 Updated by Zachary Crownover over 2 years ago

  • % Done changed from 0 to 50

Quick fix I had to use was pass a ipv6.disabled=1 to the kernel through grub and reboot

#2 Updated by Matthaus Owens about 2 years ago

  • Status changed from Unreviewed to Investigating
  • Assignee set to Matthaus Owens

#3 Updated by Matthaus Owens about 2 years ago

Zachary, What OS are you seeing this problem on?

#4 Updated by Zachary Crownover about 2 years ago

Honestly I haven’t touched Puppet in months but it was seen on Redhat, CentOS, and Debian. I had it occurring on all 3.

Zach Crownover

Associate Engineer, Infrastructure Development

Yaana Technologies, LLC

Desk: 1-408-404-3516

Mobile: 1-408-890-8808

Zachary.crownover@yaanatech.com

Description: YaanaLogo-C-Standard

From: tickets@puppetlabs.com [mailto:tickets@puppetlabs.com] Sent: Thursday, May 31, 2012 4:26 PM To: nigel@puppetlabs.com; james@lovedthanlost.net; ken@puppetlabs.com; stahnma@puppetlabs.com; adrien@puppetlabs.com; f.meester@amaziqsource.com; Zachary Crownover Cc: peter.meier@immerda.ch Subject: [Puppet Enterprise (Public) – Bug #12517] Puppet Master IPv6 Only

Issue #12517 has been updated by Matthaus Litteken.

Zachary, What OS are you seeing this problem on?


Bug #12517: Puppet Master IPv6 Only

  • Author: Zachary Crownover
  • Status: Investigating
  • Priority: High
  • Assignee: Matthaus Litteken
  • Category:
  • Target version:
  • Keywords:
  • Branch:
  • Affected URL:
  • Affected PE version:

I’m having a reproducible error, whereby my master listens on 8140 for IPv6 only and my agent is unable to see or communicate to it, and I’m not sure how to force the master to operate on IPv4 or on both IPv4 and IPv6 or to force the agent to operate on IPv6, but until they’re in sync with each other I’m having errors.


You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account

Honestly I haven’t touched Puppet in months but it was seen on Redhat, CentOS, and Debian. I had it occurring on all 3. Zach CrownoverAssociate Engineer, Infrastructure DevelopmentYaana Technologies, LLCDesk: 1-408-404-3516Mobile: 1-408-890-8808Zachary.crownover@yaanatech.com From: tickets@puppetlabs.com [mailto:tickets@puppetlabs.com] Sent: Thursday, May 31, 2012 4:26 PMTo: nigel@puppetlabs.com; james@lovedthanlost.net; ken@puppetlabs.com; stahnma@puppetlabs.com; adrien@puppetlabs.com; f.meester@amaziqsource.com; Zachary CrownoverCc: peter.meier@immerda.chSubject: [Puppet Enterprise (Public) – Bug #12517] Puppet Master IPv6 Only Issue #12517 has been updated by Matthaus Litteken. Zachary, What OS are you seeing this problem on?Bug #12517: Puppet Master IPv6 OnlyAuthor: Zachary CrownoverStatus: InvestigatingPriority: HighAssignee: Matthaus LittekenCategory: Target version: Keywords: Branch: Affected URL: Affected PE version: I’m having a reproducible error, whereby my master listens on 8140 for IPv6 only and my agent is unable to see or communicate to it, and I’m not sure how to force the master to operate on IPv4 or on both IPv4 and IPv6 or to force the agent to operate on IPv6, but until they’re in sync with each other I’m having errors.You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account Attachment: image001.png Attachment: smime.p7s

#5 Updated by Michael Stahnke about 1 year ago

  • Project changed from Puppet Enterprise (Public) to Puppet

Moving to core. This came in through PE public tracker.

#6 Updated by Michael Stahnke about 1 year ago

  • Assignee deleted (Matthaus Owens)

#7 Updated by Anonymous 8 months ago

Redmine Issue #12517 has been migrated to JIRA:

https://tickets.puppetlabs.com/browse/PUP-1139

Also available in: Atom PDF