Jira (PUP-3318) Puppet prints warning when environment is set using classifier rather than local puppet.conf
Title: Message Title Marc Seeger commented on PUP-3318 Re: Puppet prints warning when environment is set using classifier rather than local puppet.conf Hey Gilson Jose Montanha Junior , the ticket is marked as needs information Is there anything in addition to the description that I can provide? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3318) Puppet prints warning when environment is set using classifier rather than local puppet.conf
Title: Message Title Marc Seeger updated an issue Puppet / PUP-3318 Puppet prints warning when environment is set using classifier rather than local puppet.conf Change By: Marc Seeger Summary: Puppetprintswarningwhen local environment isn't is set usingclassifierratherthanlocalpuppet.conf Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3318) Puppet prints warning when local environment isn't set
Title: Message Title Marc Seeger created an issue Puppet / PUP-3318 Puppet prints warning when local environment isn't set Issue Type: Bug Affects Versions: 3.x Assignee: Unassigned Created: 19/Sep/14 11:24 AM Environment: puppet 3.5.1 Priority: Normal Reporter: Marc Seeger We set the environment in the external node classifier and don't have one set locally. Puppet seems to default to the 'production' environment in case you don't have one set and it turns into: Warning: Local environment: production doesn't match server specified node environment devel, switching agent to devel. devel is the environment currently set for this node. We didn't specify production anywhere manually. I think that when a user DOESN'T specify any environment in the puppet.conf file but sets it in the classifier, this warning seems superfluous.
Jira (PUP-3318) Puppet prints warning when environment is set using classifier rather than local puppet.conf
Title: Message Title
Marc Seeger updated an issue
Puppet / PUP-3318
Puppet prints warning when environment is set using classifier rather than local puppet.conf
Change By:
Marc Seeger
Wesettheenvironmentintheexternalnodeclassifieranddon'thaveonesetlocally.Puppetseemstodefaulttothe'production'environmentincaseyoudon'thaveonesetanditturnsinto:{noformat}Warning:Localenvironment:productiondoesn'tmatchserverspecifiednodeenvironmentdevel,switchingagenttodevel.{noformat}develistheenvironmentcurrentlysetforthisnode.Wedidn'tspecifyproductionanywheremanually.IthinkthatwhenauserDOESN'Tspecifyanyenvironmentinthepuppet.conffilebutsetsitintheclassifier,thiswarningseemssuperfluous.Thisisthelocalpuppet.conf:{noformat}[main]logdir=/var/log/puppetvardir=/var/lib/puppetssldir=/var/lib/puppet/sslrundir=/var/run/puppet #ThisisrequiredforRuby2.1.1,duetoabuginPuppet.Inreality,we#alwayscompressedtheresponsedatawithmod_deflateforcertainfiletypes.#Now,Rubywilladdit'sownAccept-Encodingheader,anddecodetheresponse#foryou.Unfortunately,Puppetwillalsotrytodecodethatresponse.#See:https://tickets.puppetlabs.com/browse/PUP-1680 http_compression=true[agent]server=master.e.some.thing.comcertname=srv-13.some.thing.com{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3318) Puppet prints warning when environment is set using classifier rather than local puppet.conf
Title: Message Title
Marc Seeger updated an issue
Puppet / PUP-3318
Puppet prints warning when environment is set using classifier rather than local puppet.conf
Change By:
Marc Seeger
Wesettheenvironmentintheexternalnodeclassifieranddon'thaveonesetlocally.Puppetseemstodefaulttothe'production'environmentincaseyoudon'thaveonesetanditturnsinto:{noformat}Warning:Localenvironment:productiondoesn'tmatchserverspecifiednodeenvironmentdevel,switchingagenttodevel.{noformat}develistheenvironmentcurrentlysetforthisnode.Wedidn'tspecifyproductionanywheremanually.IthinkthatwhenauserDOESN'Tspecifyanyenvironmentinthepuppet.conffilebutsetsitintheclassifier,thiswarningseemssuperfluous. Thisisthelocalpuppet.conf:{noformat}[main]logdir=/var/log/puppetvardir=/var/lib/puppetssldir=/var/lib/puppet/sslrundir=/var/run/puppet#ThisisrequiredforRuby2.1.1,duetoabuginPuppet.Inreality,we#alwayscompressedtheresponsedatawithmod_deflateforcertainfiletypes.#Now,Rubywilladdit'sownAccept-Encodingheader,anddecodetheresponse#foryou.Unfortunately,Puppetwillalsotrytodecodethatresponse.#See:https://tickets.puppetlabs.com/browse/PUP-1680http_compression=true[agent]server=master.e.some.thing.comcertname=srv-13.some.thing.com{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2526) puppet agent retry failed http requests
Title: Message Title Marc Seeger commented on an issue Re: puppet agent retry failed http requests Any networking problem during a puppet run (dropped packets, routing issues, DNS issues, ...) can lead to failures like these: web-7638: 2014-01-10T11:24:12+00:00 daemon.err web- puppet-agent[28071]: (/Stage[main]/Apt/File[sources.list]) Could not evaluate: Connection timed out - connect(2) Could not retrieve file metadata for puppet:///modules//.../eu-west-1.sources.list-lucid: Connection timed out - connect(2) Since puppet doesn't currently retry these failures, the rest of the run will error out with a failed dependency. Especially when pushing out a combination of new binary and new config file, this can get annoying. Among lots of other events, this could for example happen whenever Amazon does something like this: 10:22 AM PDT We are investigating network connectivity issues for some instances in the US-EAST-1 Region. 11:09 AM PDT Between 10:03 AM and 10:18 AM PDT we experienced connectivity issues for some instances in the US-EAST-1 Region. The issue has been resolved and the service is operating normally. Add Comment Puppet / PUP-2526 puppet agent retry failed http requests It would be nice if puppet agent had the ability had the ability to retry failed http requests to the puppet master. I have multiple puppet masters sitting behind a load balancer in AWS (ELB). Whenever we update a puppet master, the node is removed from the load balancer while the update occurs. Unfortunately the AWS ELB does not allow quiescent remova...
Jira (PUP-2526) puppet agent retry failed http requests
Title: Message Title Marc Seeger commented on an issue Re: puppet agent retry failed http requests reliable network You hit number one on the list Add Comment Puppet / PUP-2526 puppet agent retry failed http requests It would be nice if puppet agent had the ability had the ability to retry failed http requests to the puppet master. I have multiple puppet masters sitting behind a load balancer in AWS (ELB). Whenever we update a puppet master, the node is removed from the load balancer while the update occurs. Unfortunately the AWS ELB does not allow quiescent remova... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2526) puppet agent retry failed http requests
Title: Message Title Marc Seeger commented on an issue Re: puppet agent retry failed http requests Here is some copypasta from the PR: I would love to see this in as well. We run thousands of machines per puppet master and see this almost on every release. Some things that caused these failures in the past: Machines being in a different region and having a bit of a flaky connection (e.g. machines from Asia calling to a US puppet master) Security groups being rewritten in EC2 and network connections just dropping network connectivity issues in AWS Running releases on too many machines in parallel and thus putting too much load on the puppet master Some of these issues can be resolved by upsizing/load balancing the instance of the puppet master, but all of the network failures are something that a user might not be able to control and it's usually network problems so it's arbitrary requests that fail (file_metadata. file_metadatas, file_content, ...) Add Comment Puppet / PUP-2526 puppet agent retry failed http requests It would be nice if puppet agent had the ability had the ability to retry failed http requests to the puppet master. I have multiple puppet masters sitting behind a load balancer in AWS (ELB). Whenever we update a puppet master, the node is removed from the load balancer while the update occurs. Unfortunately the AWS ELB does not allow quiescent remova...
Jira (PUP-1680) incorrect header check using Ruby 2.1.0
Title: Message Title
Marc Seeger commented on an issue
Re: incorrect header check using Ruby 2.1.0
We had to switch our testing back to Ruby 1.9.3 because of this (and other little annoyances). WIth Ruby 2.1.1., they redid the HTTP encoding detection, so this might be solved by upgrading Ruby.
I will try to reproduce this, but it will probably take a while If anyone else has the stacktrace, feel free to post
Add Comment
Puppet / PUP-1680
incorrect header check using Ruby 2.1.0
I haven't found anything out there so far, so I thought I'd just document it while I'm at it. We ran into some other problem with the changes in net/http Ruby 2.1.0 introduced around the handling of gzip/deflate encoded content. This MIGHT be related. So far we haven't been able to fix it. {code} Error: incorrect header check Error: /Stage[main]/...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To
