Jira (FACT-629) ec2 facts should ignore proxy
Title: Message Title
Adrien Thebo commented on an issue
Re: ec2 facts should ignore proxy
Merged into master in 08f54af.
Add Comment
Facter / FACT-629
ec2 facts should ignore proxy
On an ec2 instance: {code}aj:~$ facter ec2_mac 06:6e:3c:a0:6d:78 aj:~$ http_proxy=http://nonexistent.invalid/ facter ec2_macaj:~${code} A change like the following should be made: https://github.com/alexjurkiewicz/facter/commit/902529ea32fecb0c45ea8628443d8f809695bf44#diff-5d468eb8d8ea9574dd2a2e00b3064cf7R81
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-2953) masterlog setting is dead code
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2953 masterlog setting is dead code Change By: Adrien Thebo Component/s: Community 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-2953) masterlog setting is dead code
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2953 masterlog setting is dead code Change By: Adrien Thebo Fix Version/s: 4.0.0 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 Adrien Thebo commented on an issue Re: puppet agent retry failed http requests Peter Drake as noted in my previous comment, when requesting a catalog a Puppet agent may either use a GET or a POST request. If we only retry GET and HEAD requests then this means that a Puppet agent may randomly stop retrying HTTP requests, which would be very surprising behavior if someone was depending on HTTP request retries. Are you proposing that this case isn't relevant? 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
Jira (PUP-2952) Puppet should only log facts in debug mode
Title: Message Title
Adrien Thebo commented on an issue
Re: Puppet should only log facts in debug mode
Merged in df7acc7.
Add Comment
Puppet / PUP-2952
Puppet should only log facts in debug mode
In environments with lots of facts puppet agent can fill the screen and log files with loading fact messages. This is only useful when debugging and should thus be only enabled when in debug mode. {code} rickon:~# puppet agent --test Info: Retrieving plugin Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb Info: Loading facts in /v...
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-398) Backslashify windows paths when appropriate
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-398 Backslashify windows paths when appropriate Change By: Adrien Thebo Fix Version/s: 3.7.0 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-398) Backslashify windows paths when appropriate
Title: Message Title Adrien Thebo commented on an issue Re: Backslashify windows paths when appropriate Merged in 8c80d5d. Add Comment Puppet / PUP-398 Backslashify windows paths when appropriate When installing an MSI, the windows package provider passes the package source parameter to msiexec.exe. Unfortunately, it bmust/b use backslashes, otherwise, msiexec thinks it's a command line argument and will fail with a cryptic error: preFailed to install: Fail on INT 24./pre The windows package provider should automatically convert the sourc... 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-398) Backslashify windows paths when appropriate
Title: Message Title Adrien Thebo commented on an issue Re: Backslashify windows paths when appropriate Moving to Needs Information pending contributor response on https://github.com/puppetlabs/puppet/pull/2880#discussion-diff-15471758 . Add Comment Puppet / PUP-398 Backslashify windows paths when appropriate When installing an MSI, the windows package provider passes the package source parameter to msiexec.exe. Unfortunately, it bmust/b use backslashes, otherwise, msiexec thinks it's a command line argument and will fail with a cryptic error: preFailed to install: Fail on INT 24./pre The windows package provider should automatically convert the sourc... 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-398) Backslashify windows paths when appropriate
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-398 Backslashify windows paths when appropriate Change By: Adrien Thebo Assignee: ChrisSpence 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 (FACT-633) Puppet loads ZFS module on FreeBSD when ZFS is not enabled
Title: Message Title Adrien Thebo moved an issue Facter / FACT-633 Puppet loads ZFS module on FreeBSD when ZFS is not enabled Change By: Adrien Thebo Affects Version/s: 3.4.3 Affects Version/s: 3.4.2 Affects Version/s: 3.3.1 Key: PUP FACT - 2707 633 Project: Puppet Facter 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
Jira (FACT-633) Puppet loads ZFS module on FreeBSD when ZFS is not enabled
Title: Message Title Adrien Thebo updated an issue Facter / FACT-633 Puppet loads ZFS module on FreeBSD when ZFS is not enabled Change By: Adrien Thebo Affects Version/s: 1.7.6 Affects Version/s: 2.1.0 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-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily Change By: Adrien Thebo Assignee: MatteoCerutti AdrienThebo 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-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Adrien Thebo commented on an issue Re: zypper should always be the default package provider for Suse osfamily I spoke with release engineering about our support for SLES 10, and it looks like we're only supporting SLES 10.4 which has zypper. In addition they said that we should always use zypper as a default, which means that we can remove rug as a default. Add Comment Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily zypper package manager should always be the default package provider for Suse osfamily. Additionally, this prevents puppet agent from moaning about the presence of multiple package providers if others are also installed (e.g. Yum) along with zypper. In this case, Puppet will default to the first provider it finds, which does not happen to be the same... 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
Jira (PUP-2946) FileUtils implementation broke compare_stream
Title: Message Title
Adrien Thebo commented on an issue
Re: FileUtils implementation broke compare_stream
Moving into failed review pending contributor response to https://github.com/puppetlabs/puppet/pull/2881#discussion_r15358663
Add Comment
Puppet / PUP-2946
FileUtils implementation broke compare_stream
{{FileUtils.compare_stream}} implementation in ruby 1.9.3 was doing something along the lines of {code:ruby} a = b = nil while something a = as.read size b = bs.read size return false if a != b end {code} {{FileUtils.compare_stream}} in 2.0 instead does this: {code:ruby} a = b = while some...
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-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Adrien Thebo commented on an issue Re: puppet master --compile right now unconditionally spews logs to standard output Kurt Wall I think the error from --logdest /tmp/jenny is a separate error; and this doesn't need to be run on a master in particular, it just needs to log to the provided logdest and not 5 other log destinations. Add Comment Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output 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-2946) FileUtils implementation broke compare_stream
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2946 FileUtils implementation broke compare_stream Change By: Adrien Thebo Assignee: MaksymMelnychok 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 (FACT-623) add BSD interface alias support
Title: Message Title
Adrien Thebo commented on an issue
Re: add BSD interface alias support
Marking as failed review pending changes from the contributor.
Add Comment
Facter / FACT-623
add BSD interface alias support
Output with patch: {noformat} # facter | grep -E 'ip|alias' ipaddress = 174.36.235.173 ipaddress_em0 = 10.24.8.72 ipaddress_em1 = 174.36.235.173 ipaddress_em1_alias0 = 208.43.110.204 ipaddress_em1_alias1 = 208.43.110.205 ipaddress_em1_alias2 = 208.43.110.206 ipaddress_em1_alias3 = 208.43.110.207 ipaddress_lo0 = 127.0.0.1 netmask_em1_a...
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-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Adrien Thebo commented on an issue Re: puppet master --compile right now unconditionally spews logs to standard output The catalog should always be printed to stdout; the logging should be the only thing redirected. Are we still seeing log messages leak to stdout when they should be directed to a file or syslog? Add Comment Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output 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-1541) Separate out hold state into a separate property
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-1541 Separate out hold state into a separate property Change By: Adrien Thebo Assignee: JesseHathaway AdrienThebo 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 Adrien Thebo commented on an issue Re: puppet agent retry failed http requests As the pull request for this issue has demonstrated, retrying agent HTTP requests is not a cut and dried problem; there are a number of different request types that we may (or may not) want to retry that have different behaviors. In addition there are a number of cases where retrying may be necessary, and in each one they have different retry rates and backoff periods. Retrying request types First off, we have any number of HTTP request endpoints that may need to be retried. file_metadata, file_content These are very straightforward; file metadata and content is read only and only fetched via GET so these are universally safe to retry. file_bucket_file File bucket contents are less straightforward. It's always safe to try to GET file_bucket_file files, but retrying a POST of a file_bucket_file is more up in the air - POST requests cannot automatically be retried, but this is done to back up files and so is something we probably want to ensure happens. I'm on the fence about this. catalog Retrying catalog requests is not as straightforward as you would think because fetching a catalog might use GET, or it might use POST. The reason for the different cases is the size of the facts being uploaded as part of the request. If all facts can fit as query parameters GET is used; otherwise POST is used. If we only retry GET requests, then we will be inconsistent in whether we retry catalog requests. And as a coworker pointed out, catalogs have a built in retry mechanism - if catalog retrieval fails and we need to retry in the future when the network is less congested/the master is less overloaded, the runinterval of the Puppet agent will mean we'll naturally retry the catalog compilation. report Reports should be POSTed at the end of of a catalog application, and since they contain the status of the run and so we probably want to make sure that's submitted. Once again though this is a POST, so by default we wouldn't retry this. Specific use cases that we want to handle I would like to know exactly what problems we're trying to solve here and solve those, rather than trying to implement a solution that will solve a number of non-specific cases. So far we have a handful of use cases, and each case warrants different configuration for request retries. AWS ELBs don't gracefully remove Puppet masters from the LB pool and active agent connections are forcefully reset at the TCP/IP level. In this sort of failure we do not receive anything as nice as a HTTP 503, but should immediately retry the given request. In this scenario that single retry should be sufficient and no backoff is really necessary. (From the original issue description.) (Additional note: it looks like Amazon added connection draining so this exact use case might be moot. https://aws.amazon.com/about-aws/whats-new/2014/03/20/elastic-load-balancing-supports-connection-draining/) Multiple Puppet masters are updated
Jira (PUP-1541) Separate out hold state into a separate property
Title: Message Title Adrien Thebo commented on an issue Re: Separate out hold state into a separate property Marking failed review pending contributor response. Add Comment Puppet / PUP-1541 Separate out hold state into a separate property h2. Separate out hold state into a separate property * Author: * Company: * Github ID: [lollipopman|https://github.com/lollipopman] * [Pull Request 2309 Discussion|https://github.com/puppetlabs/puppet/pull/2309] * [Pull Request 2309 File Diff|https://github.com/puppetlabs/puppet/pull/2309/files] h2. Pull Request Description Currently hol... 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-1541) Separate out hold state into a separate property
Title: Message Title Adrien Thebo assigned an issue to Unassigned Puppet / PUP-1541 Separate out hold state into a separate property Change By: Adrien Thebo Assignee: AdrienThebo 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 (HI-281) Add YAML output format to CLI
Title: Message Title Adrien Thebo updated an issue Hiera / HI-281 Add YAML output format to CLI Change By: Adrien Thebo Summary: PR(198): AddYAMLoutputformattoCLI 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 (HI-281) Add YAML output format to CLI
Title: Message Title Adrien Thebo updated an issue Hiera / HI-281 Add YAML output format to CLI Change By: Adrien Thebo Issue Type: Task NewFeature 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 (HI-281) Add YAML output format to CLI
Title: Message Title Adrien Thebo commented on an issue Re: Add YAML output format to CLI Merged in bf3cf75. Add Comment Hiera / HI-281 Add YAML output format to CLI * Author: Ahmet Demir ahmet2mir+git...@gmail.com * Github ID: [ahmet2mir|https://github.com/ahmet2mir] * [Pull Request 198 Discussion|https://github.com/puppetlabs/hiera/pull/198] * [Pull Request 198 File Diff|https://github.com/puppetlabs/hiera/pull/198/files] Just add YAML output to https://tickets.puppetlabs.com/browse/HI-129 I use hiera w... 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 (FACT-630) factor 2.1.0 errors out on Mavericks
Title: Message Title Adrien Thebo updated an issue Facter / FACT-630 factor 2.1.0 errors out on Mavericks Change By: Adrien Thebo Component/s: Community 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 (FACT-630) factor 2.1.0 errors out on Mavericks
Title: Message Title Adrien Thebo updated an issue Facter / FACT-630 factor 2.1.0 errors out on Mavericks Change By: Adrien Thebo Assignee: EricSorenson BrianWarsing 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 (FACT-630) factor 2.1.0 errors out on Mavericks
Title: Message Title Adrien Thebo commented on an issue Re: factor 2.1.0 errors out on Mavericks How did you install Facter? Is it possible you have facter installed via the .pkg as well as a gem? Add Comment Facter / FACT-630 factor 2.1.0 errors out on Mavericks Previous release 2.0.2 works. Running facter 2.1.0 on Mavericks 10.9.4, just dies with: [09:05:54]fry# facter /Library/Ruby/Site/facter/ec2/rest.rb:6: warning: already initialized constant Facter::EC2::CONNECTION_ERRORS /Library/Ruby/Site/facter/ec2/rest.rb:6: warning: previous definition of CONNECTION_ERRORS was here /Library/Ruby/Site/facter/ec2/... 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 (FACT-627) Boolean facts not printed with facter -p if fact value is false
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-627 Boolean facts not printed with facter -p if fact value is false Change By: Adrien Thebo Assignee: AdrienThebo 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 (FACT-627) Boolean facts not printed with facter -p if fact value is false
Title: Message Title Adrien Thebo updated an issue Facter / FACT-627 Boolean facts not printed with facter -p if fact value is false Change By: Adrien Thebo Affects Version/s: 1.7.6 Affects Version/s: 2.1.0 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 (FACT-627) Boolean facts not printed with facter -p if fact value is false
Title: Message Title Adrien Thebo updated an issue Facter / FACT-627 Boolean facts not printed with facter -p if fact value is false Change By: Adrien Thebo Component/s: Community 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 (FACT-627) Boolean facts not printed with facter -p if fact value is false
Title: Message Title
Adrien Thebo commented on an issue
Re: Boolean facts not printed with facter -p if fact value is false
I've added the community component so that this is tracked on the community board and subsequently sheparded through CI and FR.
Add Comment
Facter / FACT-627
Boolean facts not printed with facter -p if fact value is false
Boolean facts are not printed with facter -p if the fact value is false. Example (using a custom fact): {noformat} [root@cxdrun01 ~]# facter -p | grep is_cde is_cde = true [root@cxdrun01 ~]# facter -p is_cde true # fiddle the is_cde fact to be false here [root@cxdrun01 ~]# facter -p | grep is_cde is_cde = false [root@cxdrun01 ~]# facter -p i...
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-2871) Add :install_options and :uninstall_options to the pacman provider
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2871 Add :install_options and :uninstall_options to the pacman provider Change By: Adrien Thebo Component/s: Community 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-2946) FileUtils implementation broke compare_stream
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2946 FileUtils implementation broke compare_stream Change By: Adrien Thebo Component/s: Community 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 (FACT-597) facter needs a package dependency on net-tools on rhel7 for ifconfig
Title: Message Title Adrien Thebo updated an issue Facter / FACT-597 facter needs a package dependency on net-tools on rhel7 for ifconfig Change By: Adrien Thebo Fix Version/s: 2.2.0 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 (FACT-597) facter needs a package dependency on net-tools on rhel7 for ifconfig
Title: Message Title Adrien Thebo commented on an issue Re: facter needs a package dependency on net-tools on rhel7 for ifconfig Merged in 0d85a2c. Add Comment Facter / FACT-597 facter needs a package dependency on net-tools on rhel7 for ifconfig With RHEL 7, a minimal install doesn't even include an ifconfig binary. It's still available as /sbin/ifconfig if you install the net-tools package, but it's no longer required and guaranteed to be there. I've tried both facter 1.7.6 and facter 2.0.2, both from the PuppetLabs repo, and because neither package records a dependency on net-tools fo... 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 (FACT-622) changes to ordering in custom facts breaks things
Title: Message Title Adrien Thebo commented on an issue Re: changes to ordering in custom facts breaks things A gist would be fine, inline in the ticket would be fine as well. Add Comment Facter / FACT-622 changes to ordering in custom facts breaks things *edit* Looks like this also exists in 2.0.1 - so this may just mean that our custom facts aren't backwards compatible with the new loading logic. Is there a way to order facts if they are sourced from two different files, so that one depends correctly on the other, without filename precedence? *edit* We have a set of custom fact called node_type.rb whi... 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 (FACT-623) add BSD interface alias support
Title: Message Title Adrien Thebo created an issue Facter / FACT-623 add BSD interface alias support Issue Type: Bug Assignee: Eric Sorenson Components: Community Created: 17/Jul/14 2:35 PM Labels: bsd network alias Priority: Normal Reporter: Adrien Thebo Output with patch: # facter | grep -E 'ip|alias' ipaddress = 174.36.235.173 ipaddress_em0 = 10.24.8.72 ipaddress_em1 = 174.36.235.173 ipaddress_em1_alias0 = 208.43.110.204 ipaddress_em1_alias1 = 208.43.110.205 ipaddress_em1_alias2 = 208.43.110.206 ipaddress_em1_alias3 = 208.43.110.207 ipaddress_lo0 = 127.0.0.1 netmask_em1_alias0 = 255.255.255.0 netmask_em1_alias1 = 255.255.255.0 netmask_em1_alias2 = 255.255.255.0 netmask_em1_alias3 = 255.255.255.0 Output currently (no patch): # facter | grep -E 'ip|alias' ipaddress = 174.36.235.173 ipaddress_em0 = 10.24.8.72 ipaddress_em1 = 174.36.235.173 ipaddress_lo0 = 127.0.0.1
Jira (FACT-623) add BSD interface alias support
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-623 add BSD interface alias support Change By: Adrien Thebo Assignee: AdrienThebo 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 (FACT-617) Facter README.md should express semver/support
Title: Message Title Adrien Thebo updated an issue Facter / FACT-617 Facter README.md should express semver/support Change By: Adrien Thebo Component/s: Community 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 (HI-257) Dynamic hierarchy based on fact/variable
Title: Message Title Adrien Thebo updated an issue Hiera / HI-257 Dynamic hierarchy based on fact/variable Change By: Adrien Thebo Component/s: Community 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 (FACT-598) fqdn is concatenation of hostname -s and domainname instead of hostname -f
Title: Message Title
Adrien Thebo commented on an issue
Re: fqdn is concatenation of hostname -s and domainname instead of hostname -f
This works around a corner case that we don't want to support, closing this as wontfix.
Add Comment
Facter / FACT-598
fqdn is concatenation of hostname -s and domainname instead of hostname -f
Some systems have a hostname other than the concatenation of hostname and dnsdomainname. Or put differently, the {{hostname -s}} is not equal to {{hostname}}: {noformat} $ hostname -f systemX.locationY.domain.tld $ hostname domain-systemX {noformat} This keeps the local hostname short yet detailed enough. In that case, the right FQDN would b...
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 (FACT-598) fqdn is concatenation of hostname -s and domainname instead of hostname -f
Title: Message Title Adrien Thebo updated an issue Facter / FACT-598 fqdn is concatenation of hostname -s and domainname instead of hostname -f Change By: Adrien Thebo Component/s: Community 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 (FACT-603) Allow to configure acceptance using github mirror
Title: Message Title Adrien Thebo commented on an issue Re: Allow to configure acceptance using github mirror +1 for deferring on the acceptance test refactoring. Add Comment Facter / FACT-603 Allow to configure acceptance using github mirror In the same way that we do puppet. This should be done after Facter 2.1 has been released in stable... sometime meaning perhaps a few weeks after it is released. 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-2869) Puppet should be able to use authenticated proxies
Title: Message Title Adrien Thebo commented on an issue Re: Puppet should be able to use authenticated proxies Functional review courtesy of Brett Gray Basic config [root@master ~]# iptables -vnL Chain INPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 1600 332K ACCEPT all -- eth0 * 0.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 2 128 ACCEPT tcp -- eth0 * 0.0.0.0/00.0.0.0/0 tcp dpt:22 0 0 ACCEPT udp -- eth0 * 0.0.0.0/00.0.0.0/0 udp dpt:53 54 3419 LOGall -- * * 0.0.0.0/00.0.0.0/0 limit: avg 5/min burst 5 LOG flags 0 level 7 prefix `iptables input denied: ' 64 4019 DROP all -- * * 0.0.0.0/00.0.0.0/0 Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 989 186K ACCEPT all -- * eth00.0.0.0/00.0.0.0/0 state RELATED,ESTABLISHED 7 420 ACCEPT tcp -- * eth00.0.0.0/0192.168.62.184 tcp dpt:3128 5 349 ACCEPT udp -- * eth00.0.0.0/00.0.0.0/0 udp dpt:53 56 3360 LOGall -- * * 0.0.0.0/00.0.0.0/0 limit: avg 5/min burst 5 LOG flags 0 level 7 prefix `iptables output denied: ' 227 13620 DROP all -- * * 0.0.0.0/00.0.0.0/0 puppet.conf on master: [user] http_proxy_host = '192.168.62.184' http_proxy_port = 3128 http_proxy_user = 'user1' http_proxy_password = 'password' Puppet configured to use proxy, proxy not running [root@master ~]# puppet module install puppetlabs/acl Notice: Preparing to install into /etc/puppetlabs/puppet/modules ... Notice: Downloading from https://forgeapi.puppetlabs.com ... Error: Could not connect to https://forgeapi.puppetlabs.com There was a network communications problem The error we caught said 'Connection refused - connect(2)' Check your network connection and try again Puppet configured to use proxy, proxy running and doesn't require auth [root@master ~]# puppet module install puppetlabs/acl Notice: Preparing to install into /etc/puppetlabs/puppet/modules ... Notice: Downloading from https://forgeapi.puppetlabs.com ... Notice: Found at least one version of puppetlabs-acl compatible with PE (3.2.1); Notice: Skipping versions which don't express PE compatibility. To install the most recent version of the module regardless of compatibility with PE, use the '--ignore-requirements' flag. Notice: Installing -- do not interrupt ...
Jira (FACT-621) Add OpenBSD support for 'partitions' fact
Title: Message Title Adrien Thebo updated an issue Facter / FACT-621 Add OpenBSD support for 'partitions' fact Change By: Adrien Thebo Fix Version/s: 2.2.0 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 (FACT-621) Add OpenBSD support for 'partitions' fact
Title: Message Title Adrien Thebo updated an issue Facter / FACT-621 Add OpenBSD support for 'partitions' fact Change By: Adrien Thebo Component/s: Community 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 (FACT-621) Add OpenBSD support for 'partitions' fact
Title: Message Title Adrien Thebo commented on an issue Re: Add OpenBSD support for 'partitions' fact Merged in 66d54bf. Add Comment Facter / FACT-621 Add OpenBSD support for 'partitions' fact Currently the partitions fact only supports Linux, this PR adds support for OpenBSD too. 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 (FACT-621) Add OpenBSD support for 'partitions' fact
Title: Message Title Adrien Thebo updated an issue Facter / FACT-621 Add OpenBSD support for 'partitions' fact Change By: Adrien Thebo Labels: openbsdpartitions 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-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily Change By: Adrien Thebo Assignee: AdrienThebo 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-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Adrien Thebo commented on an issue Re: zypper should always be the default package provider for Suse osfamily For the sake of replication, how did you install yum on a SLES/OpenSuse system? Add Comment Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily zypper package manager should always be the default package provider for Suse osfamily. Additionally, this prevents puppet agent from moaning about the presence of multiple package providers if others are also installed (e.g. Yum) along with zypper. In this case, Puppet will default to the first provider it finds, which does not happen to be the same... 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-1177) sshkey creates /etc/ssh/ssh_known_hosts with mode 600
Title: Message Title Adrien Thebo commented on an issue Re: sshkey creates /etc/ssh/ssh_known_hosts with mode 600 Verified by removing /etc/ssh/ssh_known_hosts and creating an sshkey resource; the newly created file has permissions of 0644. Add Comment Puppet / PUP-1177 sshkey creates /etc/ssh/ssh_known_hosts with mode 600 Using the sshkey type /etc/ssh/ssh_known_hosts is created with mode 600 by default. This seems undesirable in most situations. I think the default should be 644. I didn't see anything obvious in the sshkey code that set it strictly on purpose. Does puppet default to 600 somewhere? And is there a simple way to tweak a type to use a different mode? Th... 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-1100) create_resources auto importing a manifest with a syntax error produce a bad error message
Title: Message Title
Adrien Thebo commented on an issue
Re: create_resources auto importing a manifest with a syntax error produce a bad error message
Verified in master.
Before:
â”” bundle exec puppet apply -e 'create_resources(kaboom, {foo = {}})'
Error: exception object expected at line 1 on node grey.somethingsinistral.net
Wrapped exception:
exception object expected
Error: exception object expected at line 1 on node grey.somethingsinistral.net
After:
â”” bundle exec puppet apply -e 'create_resources(kaboom, {foo = {}})'
Error: Syntax error at ','; expected '}' at /home/adrien/.puppet/modules/kaboom/manifests/init.pp:2 on node grey.somethingsinistral.net
Error: Syntax error at ','; expected '}' at /home/adrien/.puppet/modules/kaboom/manifests/init.pp:2 on node grey.somethingsinistral.net
Add Comment
Puppet / PUP-1100
create_resources auto importing a manifest with a syntax error produce a bad error message
Given a module with this structure: {noformat} x └── manifests ├── init.pp └── y.pp {noformat} init.pp: {noformat} class x { $r = {one = {foo = bar}} create_resources(x::y, $r) } {noformat} and y.pp which has an obvious syntax error: {code} define x::y { obvious error should be obvious } {code} ...
Jira (FACT-472) Sync facter-2 code with master
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-472 Sync facter-2 code with master Change By: Adrien Thebo Assignee: AdrienThebo 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-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Adrien Thebo commented on an issue Re: puppet master --compile right now unconditionally spews logs to standard output This causes a regression where invoking `puppet master --compile nodename` does not log anything by default, whereas before this change it would always log to the console as intended. We need to default to logging to the console when compiling a catalog for a single node. Add Comment Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output 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-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Adrien Thebo commented on an issue Re: puppet master --compile right now unconditionally spews logs to standard output Per a conversation with the other devs, we've decided that `puppet master - compile` and `puppet master --no-daemonize` should log to the console unless specified otherwise with ' logdest', and a daemonized webrick puppet master or puppet master running under webrick should log to syslog unless configured otherwise with ' -logdest'. Add Comment Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output 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-2553) Redhat service enable does not honour chkconfig or LSB Headers.
Title: Message Title Adrien Thebo commented on an issue Re: Redhat service enable does not honour chkconfig or LSB Headers. Note for posterity: changes to this need to take into account https://github.com/puppetlabs/puppet/commit/775d0dc7 when trying to add the requested functionality. Add Comment Puppet / PUP-2553 Redhat service enable does not honour chkconfig or LSB Headers. Using chkconfig service on blindly sets the service on in runlevel 2,3,4,5. puppet should use chkconfig service resetpriorities. when enabling services so that it honours the settings in the chkconfig and LSB Headers. 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-2878) puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2
Title: Message Title
Adrien Thebo updated an issue
Puppet / PUP-2878
puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2
Change By:
Adrien Thebo
{ { noformat} #apt-getinstallpuppetfacterpuppet-commonruby-rgenReadingpackagelists...DoneBuildingdependencytreeReadingstateinformation...DoneThefollowingextrapackageswillbeinstalled:hieralibjson-rubyruby-jsonvirt-whatSuggestedpackages:puppet-elvim-puppetruby-selinuxlibselinux-ruby1.8librrd-ruby1.9.1librrd-ruby1.8ThefollowingNEWpackageswillbeinstalledhieralibjson-rubyruby-jsonruby-rgenvirt-whatThefollowingpackageswillbeupgraded:facterpuppetpuppet-common3toupgrade,5tonewlyinstall,0toremoveand3nottoupgrade.Needtoget1,583kBofarchives.Afterthisoperation,2,330kBofadditionaldiskspacewillbeused.Doyouwanttocontinue[Y/n]?(Readingdatabase...97569filesanddirectoriescurrentlyinstalled.)Preparingtoreplacepuppet-common2.7.26-1puppetlabs1(using.../puppet-common_3.6.2-1puppetlabs1_all.deb)...Unpackingreplacementpuppet-common...dpkg:errorprocessing/var/cache/apt/archives/puppet-common_3.6.2-1puppetlabs1_all.deb(--unpack):tryingtooverwrite'/usr/share/man/man8/puppet-kick.8.gz',whichisalsoinpackagepuppet2.7.26-1puppetlabs1NoapportreportwrittenbecauseMaxReportshasalreadybeenreacheddpkg-deb:error:subprocesspastewaskilledbysignal(Brokenpipe)Preparingtoreplacepuppet2.7.26-1puppetlabs1(using.../puppet_3.6.2-1puppetlabs1_all.deb)...*Stoppingpuppetagent[OK]Unpackingreplacementpuppet...Selectingpreviouslyunselectedpackageruby-json.Unpackingruby-json(from.../ruby-json_1.6.3-1_i386.deb)...Selectingpreviouslyunselectedpackagelibjson-ruby.Unpackinglibjson-ruby(from.../libjson-ruby_1.6.3-1_all.deb)...Selectingpreviouslyunselectedpackagehiera.Unpackinghiera(from.../hiera_1.3.4-1puppetlabs1_all.deb)...Selectingpreviouslyunselectedpackageruby-rgen.Unpackingruby-rgen(from.../ruby-rgen_0.6.5-1puppetlabs1_all.deb)...Selectingpreviouslyunselectedpackagevirt-what.Unpackingvirt-what(from.../virt-what_1.11-1_i386.deb)...Preparingtoreplacefacter1.6.18-1puppetlabs1(using.../facter_2.0.2-1puppetlabs1_i386.deb)...Unpackingreplacementfacter...Processingtriggersforman-db...Processingtriggersforureadahead...Errorswereencounteredwhileprocessing:/var/cache/apt/archives/puppet-common_3.6.2-1puppetlabs1_all.debE:Sub-process/usr/bin/dpkgreturnedanerrorcode(1) {noformat } }
Add Comment
Jira (FACT-610) Change windows facter to return same hardware model as linux
Title: Message Title Adrien Thebo updated an issue Facter / FACT-610 Change windows facter to return same hardware model as linux Change By: Adrien Thebo Component/s: Community 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 (FACT-610) Change windows facter to return same hardware model as linux
Title: Message Title Adrien Thebo commented on an issue Re: Change windows facter to return same hardware model as linux Since this changes the value of an existing fact resolution this is backwards incompatible; we won't be able to release this change until Facter 3. Add Comment Facter / FACT-610 Change windows facter to return same hardware model as linux facter's fact hardwaremodel on windows is returned as x64 for 64 bit hardware systems. This is not the same as what is returned by Linux systems. On linux hardwaremodel is x86_64. This causes a separate hardwaremodel group to be created when they are actually the same thing. I am attaching the patched file hardwaremodel.rb but I'm not familiar w... 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 (FACT-610) Change windows facter to return same hardware model as linux
Title: Message Title Adrien Thebo updated an issue Facter / FACT-610 Change windows facter to return same hardware model as linux Change By: Adrien Thebo Fix Version/s: 3.0.0 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 (FACT-547) Limit the output of prtdiag on Solaris
Title: Message Title Adrien Thebo commented on an issue Re: Limit the output of prtdiag on Solaris Merged in bba2746. Add Comment Facter / FACT-547 Limit the output of prtdiag on Solaris prtdiag is used to determine manufacturer and productname on Solaris If you run it on a big box like a SPARC T5 it produces a lot of output, and might take some time. On a SPARC T5 this can cause timeouts. Will provide a PR 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 (FACT-547) Limit the output of prtdiag on Solaris
Title: Message Title Adrien Thebo updated an issue Facter / FACT-547 Limit the output of prtdiag on Solaris Change By: Adrien Thebo Fix Version/s: 2.2.0 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-2866) Read UID_MIN from /etc/logins.def (if available) instead of hardcoding minimum.
Title: Message Title Adrien Thebo commented on an issue Re: Read UID_MIN from /etc/logins.def (if available) instead of hardcoding minimum. Merged in bb7ec34. Add Comment Puppet / PUP-2866 Read UID_MIN from /etc/logins.def (if available) instead of hardcoding minimum. 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 (FACT-595) Unbreak {is_,}virtual fact for OpenBSD when running on KVM
Title: Message Title
Adrien Thebo commented on an issue
Re: Unbreak {is_,}virtual fact for OpenBSD when running on KVM
Merged into facter-2 in 53d39bd; this should be released in 2.2.0.
Add Comment
Facter / FACT-595
Unbreak {is_,}virtual fact for OpenBSD when running on KVM
It turned out the parse_virtualization method didn't account for KVM therefore at least OpenBSD wouldn't correctly set the virtual facts when running on KVM.
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 (FACT-595) Unbreak {is_,}virtual fact for OpenBSD when running on KVM
Title: Message Title
Adrien Thebo updated an issue
Facter / FACT-595
Unbreak {is_,}virtual fact for OpenBSD when running on KVM
Change By:
Adrien Thebo
Fix Version/s:
2.2.0
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-2869) Puppet should be able to use authenticated proxies
Title: Message Title Adrien Thebo commented on an issue Re: Puppet should be able to use authenticated proxies Merged in 9bff6f3. Add Comment Puppet / PUP-2869 Puppet should be able to use authenticated proxies Currently Puppet has the ability to use proxies when performing network communications. The current settings allow for a host and a port, but not for a username or a password. This limitation prevents tools such as PMT from being utilised from a Puppet master that is behind an authenticated proxy. 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-2869) Puppet should be able to use authenticated proxies
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2869 Puppet should be able to use authenticated proxies Change By: Adrien Thebo Fix Version/s: 3.7.0 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-1177) sshkey creates /etc/ssh/ssh_known_hosts with mode 600
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1177 sshkey creates /etc/ssh/ssh_known_hosts with mode 600 Change By: Adrien Thebo Fix Version/s: 3.7.0 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-1177) sshkey creates /etc/ssh/ssh_known_hosts with mode 600
Title: Message Title Adrien Thebo commented on an issue Re: sshkey creates /etc/ssh/ssh_known_hosts with mode 600 Merged in ae5f19e. Add Comment Puppet / PUP-1177 sshkey creates /etc/ssh/ssh_known_hosts with mode 600 Using the sshkey type /etc/ssh/ssh_known_hosts is created with mode 600 by default. This seems undesirable in most situations. I think the default should be 644. I didn't see anything obvious in the sshkey code that set it strictly on purpose. Does puppet default to 600 somewhere? And is there a simple way to tweak a type to use a different mode? Th... 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-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output Change By: Adrien Thebo Component/s: Server 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-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Adrien Thebo commented on an issue Re: puppet master --compile right now unconditionally spews logs to standard output Merged in e182038. Add Comment Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output 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-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output Change By: Adrien Thebo Fix Version/s: 3.7.0 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-2079) puppet module generate can't copy template files without parsing/renaming them
Title: Message Title Adrien Thebo commented on an issue Re: puppet module generate can't copy template files without parsing/renaming them Merged in 21267b7. Add Comment Puppet / PUP-2079 puppet module generate can't copy template files without parsing/renaming them When creating a new module with puppet module generate, any files in the skeleton dir named *.erb are parsed as Ruby erb templates and renamed, removing the file extension. This is a pain if you want to include template files in your skeleton directory. 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-2432) module skeleton is using deprecated way to configure spec_helper
Title: Message Title Adrien Thebo commented on an issue Re: module skeleton is using deprecated way to configure spec_helper garrett honeycutt now that PUP-2079 is merged does anything need to be updated to allow your PR to be merged? Add Comment Puppet / PUP-2432 module skeleton is using deprecated way to configure spec_helper [~josh] states that we are using a deprecated method for configuring rspec 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-2104) Make puppet able to configure a facter implementation to use
Title: Message Title Adrien Thebo commented on an issue Re: Make puppet able to configure a facter implementation to use Merged fixups in cac43b3. Add Comment Puppet / PUP-2104 Make puppet able to configure a facter implementation to use 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-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily Change By: Adrien Thebo Assignee: AdrienThebo 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-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Adrien Thebo commented on an issue Re: zypper should always be the default package provider for Suse osfamily Matteo Cerutti one thing I noticed is that on SLE* 10, both rug and zypper will both be default, in your opinion does this matter? Add Comment Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily zypper package manager should always be the default package provider for Suse osfamily. Additionally, this prevents puppet agent from moaning about the presence of multiple package providers if others are also installed (e.g. Yum) along with zypper. In this case, Puppet will default to the first provider it finds, which does not happen to be the same... 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-2737) user purge_ssh_keys cannot remove keys with spaces in the comment
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2737 user purge_ssh_keys cannot remove keys with spaces in the comment Change By: Adrien Thebo Fix Version/s: 3.6.3 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-2737) user purge_ssh_keys cannot remove keys with spaces in the comment
Title: Message Title
Adrien Thebo commented on an issue
Re: user purge_ssh_keys cannot remove keys with spaces in the comment
We don't plan on releasing a 3.6.3, so I'm retargeting this at 3.7.0.
Add Comment
Puppet / PUP-2737
user purge_ssh_keys cannot remove keys with spaces in the comment
Given the following: {noformat} # /root/.ssh/authorized_keys # HEADER: This file was autogenerated at Fri Jun 06 16:59:39 + 2014 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. ssh-rsa B3NzaC1yc2EBIwAAAQEA6NF8iallvQVp22WDkTkyrtvp9eWW6A8YVr+kz4TjGYe7gHzIw+niNltGEFHzD8+v1I2YJ6oXev...
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-2737) user purge_ssh_keys cannot remove keys with spaces in the comment
Title: Message Title
Adrien Thebo commented on an issue
Re: user purge_ssh_keys cannot remove keys with spaces in the comment
Merged in 4682445.
Add Comment
Puppet / PUP-2737
user purge_ssh_keys cannot remove keys with spaces in the comment
Given the following: {noformat} # /root/.ssh/authorized_keys # HEADER: This file was autogenerated at Fri Jun 06 16:59:39 + 2014 # HEADER: by puppet. While it can still be managed manually, it # HEADER: is definitely not recommended. ssh-rsa B3NzaC1yc2EBIwAAAQEA6NF8iallvQVp22WDkTkyrtvp9eWW6A8YVr+kz4TjGYe7gHzIw+niNltGEFHzD8+v1I2YJ6oXev...
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-2626) Accept module paths in Puppet::Parser::Functions.file()
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2626 Accept module paths in Puppet::Parser::Functions.file() Change By: Adrien Thebo Component/s: DSL Component/s: Community 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-2513) puppet module install fails when url includes basic auth
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2513 puppet module install fails when url includes basic auth Change By: Adrien Thebo Labels: github pupet puppetpuppet -module puppet 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-2513) puppet module install fails when url includes basic auth
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2513 puppet module install fails when url includes basic auth Change By: Adrien Thebo Component/s: Community 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-2432) module skeleton is using deprecated way to configure spec_helper
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2432 module skeleton is using deprecated way to configure spec_helper Change By: Adrien Thebo Component/s: Community 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-2432) module skeleton is using deprecated way to configure spec_helper
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2432 module skeleton is using deprecated way to configure spec_helper Change By: Adrien Thebo Assignee: PietervandeBruggen 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-2867) Support user home directories (Unix) in file resources
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2867 Support user home directories (Unix) in file resources Change By: Adrien Thebo Component/s: Community 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-2869) Puppet should be able to use authenticated proxies
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2869 Puppet should be able to use authenticated proxies Change By: Adrien Thebo Component/s: Community 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 (FACT-547) Limit the output of prtdiag on Solaris
Title: Message Title Adrien Thebo updated an issue Facter / FACT-547 Limit the output of prtdiag on Solaris Change By: Adrien Thebo Component/s: Community 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 (FACT-598) fqdn is concatenation of hostname -s and domainname instead of hostname -f
Title: Message Title Adrien Thebo updated an issue Facter / FACT-598 fqdn is concatenation of hostname -s and domainname instead of hostname -f Change By: Adrien Thebo Component/s: Community 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 (FACT-595) Unbreak {is_,}virtual fact for OpenBSD when running on KVM
Title: Message Title
Adrien Thebo updated an issue
Facter / FACT-595
Unbreak {is_,}virtual fact for OpenBSD when running on KVM
Change By:
Adrien Thebo
Component/s:
Community
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-2104) Make puppet able to configure a facter implementation to use
Title: Message Title Adrien Thebo commented on an issue Re: Make puppet able to configure a facter implementation to use Merged in 338db55. Add Comment Puppet / PUP-2104 Make puppet able to configure a facter implementation to use 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 (FACT-571) Error messages with IPv6-enabled interfaces.
Title: Message Title
Adrien Thebo updated an issue
Facter / FACT-571
Error messages with IPv6-enabled interfaces.
Change By:
Adrien Thebo
pre {noformat} cabbage~#facter--puppetnosuchfiletoload--ldapifconfig:status:SIOCGLIFFLAGS:bge0:1:nosuchinterfaceifconfig:status:SIOCGLIFFLAGS:bge0:1:nosuchinterfaceifconfig:status:SIOCGLIFFLAGS:bge0:1:nosuchinterfaceifconfig:status:SIOCGLIFFLAGS:bge0:1:nosuchinterfaceifconfig:status:SIOCGLIFFLAGS:bge0:1:nosuchinterface /pre {noformat} AworkaroundwouldbetoskiptheIPv6interfacenames: pre { code class=diff } index9fb7034..748bb1d100644---a/lib/facter/util/ip.rb+++b/lib/facter/util/ip.rb@@-59,7+59,7@@moduleFacter::Util::IPwhen'Linux','OpenBSD','NetBSD','FreeBSD','Darwin'output=%x{/sbin/ifconfig-a}when'SunOS'-output=%x{/usr/sbin/ifconfig-a}+output=%x{/usr/sbin/ifconfig-a4}endoutputend / { code /pre }
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 (FACT-345) IPv6 - interface missing
Title: Message Title Adrien Thebo commented on an issue Re: IPv6 - interface missing FACT-605 duplicates this issue but has more information and steps to fix than this issue, so I'm closing this issue as a duplicate in favor of FACT-605. Add Comment Facter / FACT-345 IPv6 - interface missing The IPv6 address facts are inconsistent: not all interfaces get a ipaddress6_interface fact. In my case I have eth0 and eth1, both with IP addresses, but facter creates facts ipaddress6_eth0 and ipaddress6 (with eth1's address). There should be an ipaddress_eth1 fact too. If I add a second IPv6 address to an interface the behavior is even more ... 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 (FACT-345) IPv6 - interface missing
Title: Message Title Adrien Thebo commented on an issue Re: IPv6 - interface missing On closer inspection this looks related but not identical, so I've reopened this issue. However to fully reproduce it we need the version of ifconfig/net-tools that demonstrates this issue as well as a fully copy of the output of `ifconfig` to properly nail down the problem and fix. Add Comment Facter / FACT-345 IPv6 - interface missing The IPv6 address facts are inconsistent: not all interfaces get a ipaddress6_interface fact. In my case I have eth0 and eth1, both with IP addresses, but facter creates facts ipaddress6_eth0 and ipaddress6 (with eth1's address). There should be an ipaddress_eth1 fact too. If I add a second IPv6 address to an interface the behavior is even more ... 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
Jira (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title
Adrien Thebo commented on an issue
Re: facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
What version of Ruby are you using with Facter? Could you provide the expected values of the missing facts?
Add Comment
Facter / FACT-605
facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Facter will use RFC 4193 addresses when creating the ipaddress6 fact, but ignores them when it tries to create interface-specific ipaddress6_$\{interface\} facts. It looks like in the latter case it is treating them the same as link-local addresses. Since these are usable, routable addresses within a LAN, they should be treated the same as any globall...
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 (FACT-605) facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts
Title: Message Title Adrien Thebo updated an issue Facter / FACT-605 facter ignores RFC 4193 ULAs when creating interface-specific ipaddress6 facts Change By: Adrien Thebo Assignee: EricSorenson MatthewPounsett 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-1177) sshkey creates /etc/ssh/ssh_known_hosts with mode 600
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-1177 sshkey creates /etc/ssh/ssh_known_hosts with mode 600 Change By: Adrien Thebo Component/s: TypesandProviders Component/s: Community 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-2732) Validation of Exec-Attribute user limits usability with non-root user.
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2732 Validation of Exec-Attribute user limits usability with non-root user. Change By: Adrien Thebo Component/s: Community 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-2737) user purge_ssh_keys cannot remove keys with spaces in the comment
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-2737 user purge_ssh_keys cannot remove keys with spaces in the comment Change By: Adrien Thebo Fix Version/s: 3.7.0 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.
