Jira (PUP-1796) File resource fails for root(/) directory.
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-1796 File resource fails for root(/) directory. Change By: Hailee Kenney Assignee: qa Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6557) Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6557 Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading Change By: Henrik Lindberg Acceptance Criteria: Tests pass in a local dev environment. Solution does not cause performance degradation on non Windows platforms. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6558) Regression: Puppet unable to load PE Trapperkeeper::Orchestrator type, breaking PE installation
Title: Message Title Henrik Lindberg commented on PUP-6558 Re: Regression: Puppet unable to load PE Trapperkeeper::Orchestrator type, breaking PE installation I need a bit of help. Where is the code for the installer? Need to understand if it is doing something different than running a standard puppet apply. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2911) PDB upgrade_oldest tests failing on Centos 6.
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2911 PDB upgrade_oldest tests failing on Centos 6. Issue Type: Bug Assignee: Unassigned Created: 2016/07/28 5:57 AM Priority: Normal Reporter: Wyatt Alt This started happening the morning of 7/27, and has affected every test run since then. Looking at the boxes it appears that the 2.3.8 package is completely broken, but I haven't dug into it enough for a clear picture. Reproduce the problem and coordinate with releng if necessary. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2910) puppetserver / puppetdb ship with empty pid file
Title: Message Title
Geoff Nichols updated an issue
PuppetDB / PDB-2910
puppetserver / puppetdb ship with empty pid file
Change By:
Geoff Nichols
Reported by [~faker] in EZ-84: After installing puppetserver or puppetdb on CentOS 6 a pid file is automatically created although the service is not being started.Example:{code}[root@centos6 vagrant]# yum -y install puppetserver(...)Complete![root@centos6 vagrant]# service puppetserver statuspuppetserver dead but pid file exists[root@centos6 vagrant]# cat /var/run/puppetlabs/puppetserver/puppetserver [root@centos6 vagrant]#{code}The pid file should not get automatically created, only the folder containing it.Same is happening with puppetdb.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6560) Master puppet CI pipeline fails becuase gettext gem is not found
Title: Message Title Sean Griffin created an issue Puppet / PUP-6560 Master puppet CI pipeline fails becuase gettext gem is not found Issue Type: CI Blocker Assignee: Unassigned Created: 2016/07/28 7:08 AM Priority: Normal Reporter: Sean Griffin All platforms are failing in step 2. Here is one example: https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/puppet/job/platform_puppet_unit-ruby_master/RUBY_VER=1.9.3-p484,UNEEDED=UNEEDED,label=unit/371/console It appear this resulted from this PR for PUP-6474: https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/puppet/job/platform_puppet_unit-ruby_master/RUBY_VER=1.9.3-p484,UNEEDED=UNEEDED,label=unit/371/console Add Comment
Jira (PUP-6561) PUP-6099 breaks mounted filesystem permissions
Title: Message Title
Paul Anderson created an issue
Puppet / PUP-6561
PUP-6099 breaks mounted filesystem permissions
Issue Type:
Bug
Affects Versions:
PUP 4.5.2
Assignee:
Kylo Ginsberg
Components:
Client
Created:
2016/07/28 7:30 AM
Priority:
Normal
Reporter:
Paul Anderson
Because one can only manage a file resource ONCE,
PUP-6099
causes scenarios with mounted filesystems to break.
Consider the following scenario:
{{
include lvm
file { ['/apps'] : ensure => directory, owner => nobody, group => nobody, mode => '0700', }
physical_volume { '/dev/sdb': ensure => present, }
volume_group { 'vg0': ensure => present, physical_volumes => '/dev/sdb', }
lvm::logical_volume { 'apps': volume_group => 'vg0', size => '1G', fs_type => 'ext3', mountpath_require => false, before => File['/apps'], { }
}} With the above code, the permissions on /apps are not set correctly as described in the file resource u
Jira (PUP-6561) PUP-6099 breaks mounted filesystem permissions
Title: Message Title
Jeremy Adams updated an issue
Puppet / PUP-6561
PUP-6099 breaks mounted filesystem permissions
Change By:
Jeremy Adams
Because one can only manage a file resource ONCE, PUP-6099 causes scenarios with mounted filesystems to break.Consider the following scenario:{{include lvmfile { ['/apps'] :ensure => directory,owner => nobody,group => nobody,mode => '0700',}physical_volume { '/dev/sdb':ensure => present,}volume_group { 'vg0':ensure => present,physical_volumes => '/dev/sdb',}lvm::logical_volume { 'apps':volume_group => 'vg0',size => '1G',fs_type => 'ext3',mountpath_require => false,before => File['/apps'],{}}}With the above code, the permissions on /apps are not set correctly as described in the file resource until the next puppet run, in which case /apps may be unavailable or have security issues or ??? for half an hour by default.To address the issue, the customer user may feel the need to do silly things, such as this:{{lvm::logical_volume { 'apps':volume_group => 'vg0',size => '1G',fs_type => 'ext3',mountpath_require => false,} ->exec { '/bin/chown nobody /apps' : } ->exec { '/bin/chgrp nobody /apps' : } ->exec { '/bin/chmod 0700 /apps' : }}}I would therefore suggest we come up with a solution that allows us to intelligently address this situation:create directory -> mount filesystem -> manage ownership/permissionsThe puppetlabs-lvm module avoids this by using an exec to create the directory, which would then allow a file resource to manage the directory ownership/permissions afterwards.Perhaps we could add a parameter that defaults to current behavior, that if toggled would not auto require the parent directory?
Add Comment
Jira (HI-526) Ruby 1.9.3 and json_pure 2.0.2
Title: Message Title Matt Schuchard created an issue Hiera / HI-526 Ruby 1.9.3 and json_pure 2.0.2 Issue Type: Bug Affects Versions: HI 3.2.0 Assignee: Unassigned Created: 2016/07/28 8:33 AM Environment: All using Ruby 1.9.3 Labels: hiera Priority: Normal Reporter: Matt Schuchard Hiera has a dependency on json_pure of >= 0: https://github.com/puppetlabs/hiera/blob/master/.gemspec json_pure 2.0.2 dropped support for Ruby 1.9.3, so installs of Hiera, and therefore also Puppet, now fail on environments with Ruby 1.9.3. Something needs to be added that restricts the version of json_pure to <= 2.0.1 if ruby is 1.9.3. Kylo has mentioned in a PR to me that there are no plans to up the minimum ruby requirement for Puppet prior to 5.0 I believe, so I think this is the path of least resistance here.
Jira (HI-526) Ruby 1.9.3 and json_pure 2.0.2
Title: Message Title Matt Schuchard updated an issue Hiera / HI-526 Ruby 1.9.3 and json_pure 2.0.2 Change By: Matt Schuchard Hiera has a dependency on json_pure of >= 0: https://github.com/puppetlabs/hiera/blob/master/.gemspecjson_pure 2.0.2 dropped support for Ruby 1.9.3, so installs of Hiera, and therefore also Puppet, now fail on environments with Ruby 1.9.3.Something needs to be added that restricts the version of json_pure to <= 2.0.1 if ruby is 1.9.3. Kylo has mentioned to me in a PR to me that there are no plans to up the minimum ruby requirement for Puppet prior to 5.0 I believe, so I think this is the path of least resistance here. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6527) hiera_include() fails when compiling an environment catalog
Title: Message Title Zach Reichert updated an issue Puppet / PUP-6527 hiera_include() fails when compiling an environment catalog Change By: Zach Reichert QA Risk Assessment: Low QA Risk Probability: Low QA Risk Severity: Low QA Status: Reviewed QA Contact: Zach Reichert Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving ema
Jira (PUP-6562) Limit transaction.failed_dependencies? verbosity
Title: Message Title Curtis Ruck created an issue Puppet / PUP-6562 Limit transaction.failed_dependencies? verbosity Issue Type: Improvement Affects Versions: PUP 4.5.3 Assignee: Unassigned Components: Performance Created: 2016/07/28 8:35 AM Environment: Puppet Agent 4.5.3 Priority: Critical Reporter: Curtis Ruck In transaction.rb's failed_dependencies? function, the transaction logs each parent dependency that failed. This causes a significant issue in certain cases where there are a large number of items in the graph and participating in dependencies. In my case, we have a significant number of custom types/providers for managing database items. Below I put in a simple example. If there are 200 tables, and 200 objects, it generates 4 notices if Exec['create foo objects'] fails. I can realize that I need to fix the Exec failure, but my intent of this actual issue is that the Puppet agent captures all 4 notices in th
Jira (HI-526) Ruby 1.9.3 and json_pure 2.0.2
Title: Message Title Matt Schuchard updated an issue Hiera / HI-526 Ruby 1.9.3 and json_pure 2.0.2 Change By: Matt Schuchard Hiera has a dependency on json_pure of >= 0: https://github.com/puppetlabs/hiera/blob/master/.gemspecjson_pure 2.0.2 dropped support for Ruby 1.9.3, so installs of Hiera, and therefore also Puppet, now fail on environments with Ruby 1.9.3.Something needs to be added that restricts the version of json_pure to <= 2.0.1 if ruby is 1.9.3. I believe Kylo has mentioned to me in a PR that there are no plans to up the minimum ruby requirement for Puppet prior to 5.0 I believe , so I think this is the path of least resistance here. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6558) Regression: Puppet unable to load PE Trapperkeeper::Orchestrator type, breaking PE installation
Title: Message Title
William Hopper commented on PUP-6558
Re: Regression: Puppet unable to load PE Trapperkeeper::Orchestrator type, breaking PE installation
Henrik Lindberg there are a few installer bits at play. First, the puppetlabs-pe_manager module which actually does the apply as part of the puppet enterprise configure face, as seen here.
This uses the puppetlabs-pe_install module to determine which profiles should be applied, which in turn uses the module code in puppetlabs-puppet_enterprise to actually do the work. The bits in pe_install that are involved with this are:
1) Here, in install.pp in pe_install, when coordinating the inclusion of puppet_enterprise profile classes. This is where the puppet_enterprise::profile::orchestrator: class is being used.
2) Here, in {{puppet_enterprise/manifests/profiles/orchestrator.pp where we actually setup the dependency, where we fail to find the Puppet_enterprise::Trapperkeeper::Orchestrator class:
before => Puppet_enterprise::Trapperkeeper::Orchestrator[$container]
This class is defined in here: https://github.com/puppetlabs/puppetlabs-puppet_enterprise/blob/2016.3.x/manifests/trapperkeeper/orchestrator.pp
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are sub
Jira (PUP-6087) Multiple contradictory 'consumes' annotation do not lead to an error
Title: Message Title Zach Reichert updated an issue Puppet / PUP-6087 Multiple contradictory 'consumes' annotation do not lead to an error Change By: Zach Reichert QA Risk Assessment: Low QA Risk Probability: Low QA Risk Severity: Low QA Status: Reviewed QA Contact: Zach Reichert Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop rece
Jira (PUP-6558) Regression: Puppet unable to load PE Trapperkeeper::Orchestrator type, breaking PE installation
Title: Message Title Henrik Lindberg commented on PUP-6558 Re: Regression: Puppet unable to load PE Trapperkeeper::Orchestrator type, breaking PE installation Thanks William Hopper - that gives me something to start drilling into. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6182) Application declarations don't properly validate component mappings
Title: Message Title Zach Reichert updated an issue Puppet / PUP-6182 Application declarations don't properly validate component mappings Change By: Zach Reichert QA Risk Assessment: Low QA Risk Probability: Low QA Risk Severity: Low QA Status: Reviewed QA Contact: Zach Reichert Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop recei
Jira (PUP-1796) File resource fails for root(/) directory.
Title: Message Title
Hailee Kenney commented on PUP-1796
Re: File resource fails for root(/) directory.
On SHA 7c51b6b0649c9a8206ac684e36624506941ca42f (before the fix):
[root@cfbtk6c3v3tdxkt puppet]# cat test.pp
file { '/': ensure => directory }
[root@cfbtk6c3v3tdxkt puppet]# bundle exec puppet apply test.pp
Notice: Compiled catalog for cfbtk6c3v3tdxkt.delivery.puppetlabs.net in environment production in 0.07 seconds
Error: Parameter path failed on File[/]: File paths must be fully qualified, not '' at /root/puppet/test.pp:1
And on the latest version of master (SHA 7943fcbf9b094b7e435d8dde2b0a3539b506d886):
[root@cfbtk6c3v3tdxkt puppet]# cat test.pp
file { '/': ensure => directory }
[root@cfbtk6c3v3tdxkt puppet]# bundle exec puppet apply test.pp
Jira (PUP-6497) CapabilityFinder says a capability couldn't be found if there are multiple versions of it
Title: Message Title Zach Reichert updated an issue Puppet / PUP-6497 CapabilityFinder says a capability couldn't be found if there are multiple versions of it Change By: Zach Reichert QA Risk Assessment: Low QA Risk Probability: Low QA Risk Severity: Low QA Status: Reviewed QA Contact: Zach Reichert Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from thi
Jira (PUP-6562) Limit transaction.failed_dependencies? verbosity
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6562 Limit transaction.failed_dependencies? verbosity Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6561) PUP-6099 breaks mounted filesystem permissions
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6561 PUP-6099 breaks mounted filesystem permissions Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6561) PUP-6099 breaks mounted filesystem permissions
Title: Message Title
Paul Anderson updated an issue
Puppet / PUP-6561
PUP-6099 breaks mounted filesystem permissions
Change By:
Paul Anderson
Because one can only manage a file resource ONCE, PUP-6099 causes scenarios with mounted filesystems to break.Consider the following scenario:{{include lvmfile { ['/apps'] :ensure => directory,owner => nobody,group => nobody,mode => '0700',}physical_volume { '/dev/sdb':ensure => present,}volume_group { 'vg0':ensure => present,physical_volumes => '/dev/sdb',}lvm::logical_volume { 'apps':volume_group => 'vg0',size => '1G',fs_type => 'ext3',mountpath_require => false, # before => File['/apps'], #This is the desired effect, but causes a cyclical dependency. {}}}With the above code, the permissions on /apps are not set correctly as described in the file resource until the next puppet run, in which case /apps may be unavailable or have security issues or ??? for half an hour by default.To address the issue, the user may feel the need to do silly things, such as this:{{lvm::logical_volume { 'apps':volume_group => 'vg0',size => '1G',fs_type => 'ext3',mountpath_require => false,} ->exec { '/bin/chown nobody /apps' : } ->exec { '/bin/chgrp nobody /apps' : } ->exec { '/bin/chmod 0700 /apps' : }}}I would therefore suggest we come up with a solution that allows us to intelligently address this situation:create directory -> mount filesystem -> manage ownership/permissionsThe puppetlabs-lvm module avoids this by using an exec to create the directory, which would then allow a file resource to manage the directory ownership/permissions afterwards.Perhaps we could add a parameter that defaults to current behavior, that if toggled would not auto require the parent directory?
Add Comment
Jira (PUP-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title James Stocks commented on PUP-6459 Re: puppet resource service fails on Windows 10 Pro (x64) I think we are also seeing this in pxp-agent's acceptance tests on windows-10ent-32 (32bit) When I log into the host, any use of "puppet agent resource ..." results in WARNING: Failed to retreive description for the XboxNetApiSvc service. Error: Could not run: No such device or address - QueryServiceConfig2: The handle is invalid.> Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6561) PUP-6099 breaks mounted filesystem permissions
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6561 PUP-6099 breaks mounted filesystem permissions Change By: Kylo Ginsberg Sprint: Client Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6397) File autorequire in Mount causes dependency loops
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6397 File autorequire in Mount causes dependency loops Change By: Kylo Ginsberg Sprint: Client Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2912) (maint) fix ruby json_pure related spec test breakage
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2912 (maint) fix ruby json_pure related spec test breakage Issue Type: Bug Assignee: Unassigned Created: 2016/07/28 10:08 AM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://gr
Jira (PUP-6561) PUP-6099 breaks mounted filesystem permissions
Title: Message Title Paul Anderson commented on PUP-6561 Re: PUP-6099 breaks mounted filesystem permissions Hat tip to Ben Ford Explicitly specifying a relationship seems to address the autrequires issue: Mount['/apps'] -> File['/apps'] That said, one still needs to make sure /apps exists. In our case, it is being taken care of by the LVM module's exec. I still think we need an intelligent solution with respect to mount that: Creates mountpoint if missing -> Mounts file system -> Manages mountpoint ownership/permissions I will open a doc ticket to publicize Ben Ford's elegant solution. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6099) Additional file and mount autorequire
Title: Message Title Kylo Ginsberg commented on PUP-6099 Re: Additional file and mount autorequire Crud, two tickets are now reporting regressions from this work. I've linked them both to this ticket, but for clicking convenience: PUP-6397 PUP-6561 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2911) PDB upgrade_oldest tests failing on Centos 6.
Title: Message Title Wyatt Alt commented on PDB-2911 Re: PDB upgrade_oldest tests failing on Centos 6. This results from Centos 6 updating to openjdk 1.7.0-111. It can be worked around on the PuppetDB side by installing java 8 and modifying /etc/sysconfig/puppetdb. Ryan Senior is investigating a better workaround. RE-7688 has more discussion on the release end/PE implications. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2911) PDB upgrade_oldest tests failing on Centos 6.
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-2911 PDB upgrade_oldest tests failing on Centos 6. Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2911) PDB upgrade_oldest tests failing on Centos 6.
Title: Message Title Wyatt Alt assigned an issue to Ryan Senior PuppetDB / PDB-2911 PDB upgrade_oldest tests failing on Centos 6. Change By: Wyatt Alt Assignee: Wyatt Alt Ryan Senior Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6562) Limit transaction.failed_dependencies? verbosity
Title: Message Title Curtis Ruck commented on PUP-6562 Re: Limit transaction.failed_dependencies? verbosity Additionally, when trying to troubleshoot the failure in the above cases, having multiple stages cause issues; especially if your doing significant amount of work in the follow on stages to a failure. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6397) File autorequire in Mount causes dependency loops
Title: Message Title Matt Schuchard commented on PUP-6397 Re: File autorequire in Mount causes dependency loops The issue reported by Mikhail is apparently something we all missed at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/mount.rb#L307. That regexp needs to be tightened and maybe a new spec test added for that situation he described. As for the File[/x] -> Mount[/x]# Forced by PUP-6099 Mountpoint[/x] -> Mount[/x] -> File[/x] # What we would want to do that is a good idea to me. Puppet needs something to differentiate between creating a directory and applying permissions to it since mount occurs between the two and the same File resource cannot be declared twice. Maybe add a new attribute to Mount that creates a directory if it is missing like with the managehome attribute in the User type? Either way, funny how PUP-6099 ended up revealing both the gap in autorequire/autbefore spec testing and now the gap in file ensure vs. permissions and the relationship between directory creation, mounting, and directory permissions in Linux versus the expectations of Puppet. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6397) File autorequire in Mount causes dependency loops
Title: Message Title Matt Schuchard commented on PUP-6397 Re: File autorequire in Mount causes dependency loops Proposal: 1. Remove the File['/foo'] -> Mount['/foo'] autorequire and its corresponding doc in favor of... 2. Add an attribute to the Mount type that creates the mountpoint directory if it does not exist, add doc for that attribute, and add spec test for that attribute. 3. Tighten the regexp on the Mount['/foo'] -> File['/foo/bar'] autobefore and add a spec test for the issue Mikhail identified. Let me know how this sounds and I can start going after it. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6435) Replace sensitive data marker type with resource metadata after catalog compilation
Title: Message Title Adrien Thebo assigned an issue to Branan Riley Puppet / PUP-6435 Replace sensitive data marker type with resource metadata after catalog compilation Change By: Adrien Thebo Assignee: Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6527) hiera_include() fails when compiling an environment catalog
Title: Message Title Henrik Lindberg commented on PUP-6527 Re: hiera_include() fails when compiling an environment catalog Merged to master: 38cedb0 Solution was to add a dummy hiera_include (that does not except logging the fact it does nothing) in the startup of the environment compiler. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6563) Windows gem install requires quotes around versions with ~> while linux does not
Title: Message Title Chris Matteson moved an issue Puppet / PUP-6563 Windows gem install requires quotes around versions with ~> while linux does not Change By: Chris Matteson Key: PE PUP - 16567 6563 Project: Puppet Enterprise [Internal] Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-527) Hiera not passing data to erb template file
Title: Message Title Lanre created an issue Hiera / HI-527 Hiera not passing data to erb template file Issue Type: CI Blocker Affects Versions: HI 3.2.0 Assignee: Aaron Armstrong Components: PE Created: 2016/07/28 1:39 PM Environment: PE 4.5.2, Ubuntu 14.04 server edition Priority: Normal Reporter: Lanre We are having this issue where Component/module template file is not being update by hiera data content. This works on our current puppet 3.8 version, we are migrating our modules but this is looking like a blocker at the moment. We have a template file named file.conf.py.erb which has variable entries. The variable entries are updated by whatever we have in file2.yaml hiera data
Jira (HI-527) Hiera not passing data to erb template file
Title: Message Title
Lanre updated an issue
Hiera / HI-527
Hiera not passing data to erb template file
Change By:
Lanre
We are having this issue where Component/module template file is not being update by hiera data content. This works on our current puppet 3.8 version, we are migrating our modules but this is looking like a blocker at the moment.* We have a template file named {{file.conf.py.erb}} which has variable entries. * The variable entries are updated by whatever we have in {{file2.yaml}} hiera dataSample content of{{ file.conf.py.erb}} ` {{ DATABASES = { 'default': { 'ENGINE': 'sentry.db.postgres', 'NAME': '<%= @db_name %>', 'USER': '<%= @db_user %>', 'PASSWORD': '<%= @db_password %>', 'HOST': '<%= @db_host %>', 'PORT': '<%= @db_port %>', }} ` }} Sample content of {{ file2.yaml }}hiera file {{ `db_name: 'name'db_user: 'useroi'db_password: 'my_password'db_host: 'abc.com'db_port: '8964'` }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-527) Hiera not passing data to erb template file
Title: Message Title
Lanre updated an issue
Hiera / HI-527
Hiera not passing data to erb template file
Change By:
Lanre
We are having this issue where Component/module template file is not being update by hiera data content. This works on our current puppet 3.8 version, we are migrating our modules but this is looking like a blocker at the moment.* We have a template file named {{file.conf.py.erb}} which has variable entries. * The variable entries are updated by whatever we have in {{file2.yaml}} hiera dataSample content of{{ file.conf.py.erb}}{{DATABASES = { 'default': { 'ENGINE': 'sentry.db.postgres', 'NAME': '<%= @db_name %>', 'USER': '<%= @db_user %>', 'PASSWORD': '<%= @db_password %>', 'HOST': '<%= @db_host %>', 'PORT': '<%= @db_port %>', }} }}Sample content of {{ file2.yaml }}hiera file{{`db_name: 'name'db_user: 'useroi'db_password: 'my_password'db_host: 'abc.com'db_port: '8964'`}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-527) Hiera not passing data to erb template file
Title: Message Title Aaron Armstrong assigned an issue to Unassigned Hiera / HI-527 Hiera not passing data to erb template file Change By: Aaron Armstrong Assignee: Aaron Armstrong Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-527) Hiera not passing data to erb template file
Title: Message Title
Lanre updated an issue
Hiera / HI-527
Hiera not passing data to erb template file
Change By:
Lanre
We are having this issue where Component/module template file is not being update by hiera data content. This works on our current puppet 3.8 version, we are migrating our modules but this is looking like a blocker at the moment.* We have a template file named {{file.conf.py.erb}} which has variable entries. * The variable entries are updated by whatever we have in {{file2.yaml}} hiera dataSample content of{{ file.conf.py.erb}}{ { color:red} DATABASES = { 'default': { 'ENGINE': 'sentry.db.postgres', 'NAME': '<%= @db_name %>', 'USER': '<%= @db_user %>', 'PASSWORD': '<%= @db_password %>', 'HOST': '<%= @db_host %>', 'PORT': '<%= @db_port %>', }} {color } } Sample content of {{ file2.yaml }}hiera file{ {` color:red} db_name: 'name'db_user: 'useroi'db_password: 'my_password'db_host: 'abc.com'db_port: '8964' ` {color } }
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-527) Hiera not passing data to erb template file
Title: Message Title Aaron Armstrong updated an issue Hiera / HI-527 Hiera not passing data to erb template file Change By: Aaron Armstrong CI Pipeline/s: puppet-enterprise Issue Type: CI Blocker Bug Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-527) Hiera not passing data to erb template file
Title: Message Title Lanre updated an issue Hiera / HI-527 Hiera not passing data to erb template file Change By: Lanre Priority: Normal Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-527) Hiera not passing data to erb template file
Title: Message Title
Lanre updated an issue
Hiera / HI-527
Hiera not passing data to erb template file
Change By:
Lanre
We are having this issue where Component/module template file is not being update by hiera data content. This works on our current puppet 3.8 version, we are migrating our modules but this is looking like a blocker at the moment.* We have a template file named {{file.conf.py.erb}} which has variable entries. * The variable entries are updated by whatever we have in {{file2.yaml}} hiera dataSample content of{{ file.conf.py.erb}}{color:red}DATABASES = { 'default': { 'ENGINE': 'sentry.db.postgres', 'NAME': '<%= @db_name %>', 'USER': '<%= @db_user %>', 'PASSWORD': '<%= @db_password %>', 'HOST': '<%= @db_host %>', 'PORT': '<%= @db_port %>', }}{color}Sample content of {{ file2.yaml }}hiera file{color:red}db_name: 'name'db_user: 'useroi'db_password: 'my_password'db_host: 'abc.com'db_port: '8964'{color}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2913) (maint) ensure nss is up to date
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2913 (maint) ensure nss is up to date Issue Type: Bug Assignee: Unassigned Created: 2016/07/28 3:31 PM Priority: Normal Reporter: gepetto-bot An out of date nss can cause issues with openjdk. Ensure it's up to date on both the database and the master. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6564) Support Ruby 2.3.x with Puppet 4.5.2
Title: Message Title Ravi Shankar created an issue Puppet / PUP-6564 Support Ruby 2.3.x with Puppet 4.5.2 Issue Type: Bug Affects Versions: PUP 4.5.2 Assignee: Unassigned Created: 2016/07/28 3:44 PM Environment: Linux, Windows, Unix Fix Versions: PUP 4.5.2 Priority: Normal Reporter: Ravi Shankar Ruby 2.1.9 is the highest version tested and supported for Puppet 4.5.2. Please support the recent version of Ruby 2.3.x which is supported for longer term.
Jira (PUP-6557) Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6557 Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading Change By: Ethan Brown Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6551) Pin json_pure dependency to < 2
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6551 Pin json_pure dependency to < 2 Change By: Ethan Brown Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6483 "puppet resource user", when run in Windows creates a login attempt. Change By: Ethan Brown Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6545) Ruby 2.3 fails spec tests on Appveyor in Windows
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6545 Ruby 2.3 fails spec tests on Appveyor in Windows Change By: Ethan Brown Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6459 puppet resource service fails on Windows 10 Pro (x64) Change By: Ethan Brown Sprint: Windows 2016-08-10 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6459 puppet resource service fails on Windows 10 Pro (x64) Change By: Ethan Brown Fix Version/s: PUP 4.6.0 Fix Version/s: PUP 4.5.4 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title Ethan Brown assigned an issue to Glenn Sarti Puppet / PUP-6459 puppet resource service fails on Windows 10 Pro (x64) Change By: Ethan Brown Assignee: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title Ethan Brown commented on PUP-6459 Re: puppet resource service fails on Windows 10 Pro (x64) Sorry this one slipped through the cracks. I have also validated that the win32-service gem is at fault. C:\Users\Parity\Documents\source\00 - Puppet\puppet [master...origin/master]> irb irb(main):001:0> require 'win32/service' => true irb(main):002:0> Win32::Service.services WARNING: Failed to retreive description for the pvhdparser service. Errno::ENXIO: No such device or address - QueryServiceConfig2: The handle is invalid. from C:/tools/ruby21/lib/ruby/gems/2.1.0/gems/win32-service-0.8.7/lib/win32/windows/helper.rb:36:in `raise_windows_error' from C:/tools/ruby21/lib/ruby/gems/2.1.0/gems/win32-service-0.8.7/lib/win32/service.rb:1380:in `get_config2_info' from C:/tools/ruby21/lib/ruby/gems/2.1.0/gems/win32-service-0.8.7/lib/win32/service.rb:1092:in `block in services'
Jira (PUP-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6459 puppet resource service fails on Windows 10 Pro (x64) Change By: Ethan Brown Priority: Normal Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6459 puppet resource service fails on Windows 10 Pro (x64) Change By: Ethan Brown Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title Ethan Brown commented on PUP-6459 Re: puppet resource service fails on Windows 10 Pro (x64) Also note that when we get the puppet-win32-ruby PRs merged, we should tag new 2.1.x tags for packaging purposes (more necessary if we end up using the old MSI building mechanism instead of Vanagon) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
