Jira (PUP-9957) puppet apply command fails when external modules are installed
Title: Message Title Michael Watters commented on PUP-9957 Re: puppet apply command fails when external modules are installed Josh Cooper Unfortunately the trace option doesn't show very much. Attached is a screenshot for reference. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313933.1561476226000.14001.1584396420190%40Atlassian.JIRA.
Jira (PUP-9957) puppet apply command fails when external modules are installed
Title: Message Title Michael Watters updated an issue Puppet / PUP-9957 puppet apply command fails when external modules are installed Change By: Michael Watters Attachment: Capture.PNG Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313933.1561476226000.13992.1584396360030%40Atlassian.JIRA.
Jira (PUP-10161) Regresssion: puppet 6.11 can't manage selinux on centos/redhat 8
Title: Message Title Michael Watters commented on PUP-10161 Re: Regresssion: puppet 6.11 can't manage selinux on centos/redhat 8 I was able to correct this by downgrading the puppet-agent package to 6.10.1. ```dnf install puppet-agent-6.10.1``` This was done on a node running CentOS 8 with the puppet6-release package installed. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338022.1575566536000.310.1576510080399%40Atlassian.JIRA.
Jira (PUP-10161) Regresssion: puppet 6.11 can't manage selinux on centos/redhat 8
Title: Message Title Michael Watters commented on PUP-10161 Re: Regresssion: puppet 6.11 can't manage selinux on centos/redhat 8 This error can also cause management of resources that do not depend on selinux to fail as well. For example, on a node running CentOS 8 custom types are not applied due to the agent failures. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.338022.1575566536000.9396.1576257000423%40Atlassian.JIRA.
Jira (HI-578) Symbolized facts causes "ignore bad definition" error in hierarchy
Title: Message Title
Michael Watters commented on HI-578
Re: Symbolized facts causes "ignore bad definition" error in hierarchy
Has anybody found a solution for this issue? I have rspec tests failing because facts are not resolving properly. When rspec runs I see the same error as originally reported.
DEBUG: 2018-08-15 09:08:15 -0400: Hiera YAML backend starting
DEBUG: 2018-08-15 09:08:15 -0400: Looking up chrony::packages in YAML backend
DEBUG: 2018-08-15 09:08:15 -0400: Ignoring bad definition in :hierarchy: ''
hiera.yaml looks like this.
---
:backends:
- yaml
:hierarchy:
- "%{operatingsystem}"
- common
:yaml:
:datadir: 'data'
Jira (PUP-8045) Add support for Fedora 26 in the dnf provider
Title: Message Title Michael Watters created an issue Puppet / PUP-8045 Add support for Fedora 26 in the dnf provider Issue Type: Improvement Assignee: Unassigned Created: 2017/10/11 3:57 PM Priority: Normal Reporter: Michael Watters The dnf provider is only configured to be the default on Fedora 22-24. This provider should support all Fedora releases from 22 and up. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7419) man page for puppet is invalid
Title: Message Title Michael Watters created an issue Puppet / PUP-7419 man page for puppet is invalid Issue Type: Bug Affects Versions: PUP 4.9.4 Assignee: Unassigned Created: 2017/03/31 12:33 PM Environment: CentOS 7.3 x86_64 with puppet-agent 1.9.3 Priority: Normal Reporter: Michael Watters The man page for the puppet command appears to be invalid. The contents of /opt/puppetlabs/puppet/share/man/man8/puppet.8.gz appear as follows. .\" generated with Ronn/v0.7.3 .\" https://github.com/rtomayko/ronn/tree/0.7.3
Jira (FACT-1594) Operating system name is reported incorrectly in openSUSE Leap 42.2
Title: Message Title Michael Watters commented on FACT-1594 Re: Operating system name is reported incorrectly in openSUSE Leap 42.2 /etc/os-release contains the following info. linux-b1zb:~ # cat /etc/os-release NAME="openSUSE Leap" VERSION="42.2" ID=opensuse ID_LIKE="suse" VERSION_ID="42.2" PRETTY_NAME="openSUSE Leap 42.2" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:42.2" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 (FACT-1594) Operating system name is reported incorrectly in openSUSE Leap 42.2
Title: Message Title Michael Watters created an issue Facter / FACT-1594 Operating system name is reported incorrectly in openSUSE Leap 42.2 Issue Type: Bug Affects Versions: FACT 3.6.2 Assignee: Unassigned Created: 2017/03/24 6:04 AM Environment: NAME="openSUSE Leap" VERSION="42.2" ID=opensuse ID_LIKE="suse" VERSION_ID="42.2" PRETTY_NAME="openSUSE Leap 42.2" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:42.2" d861703@linux-b1zb:~$ rpm -qi puppet-agent Name : puppet-agent Version : 1.9.3 Release : 1.sles12 Architecture: x86_64 Install Date: Tue 21 Mar 2017 08:28:42 PM EDT Group : System Environment/Base Size : 173880556 License : See components Signature : RSA/SHA1, Thu 09 Mar 2017 05:32:33 PM EST, Key ID 7f438280ef8d349f Source RPM : puppet-agent-1.9.3-1.sles12.src.rpm Build Date : Thu 09 Mar 2017 02:06:21 PM EST Build Host : iivz48h08cc5xgd.delivery.puppetlabs.net Relocations : (not relocatable) Vendor : Puppet Labs URL : https://www.puppetlabs.com Summary : The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective. Description : The Puppet Agent package contains all of the elements needed to run puppet, including ruby, facter, hiera and mcollective. Contains the following components: augeas 1.4.0 cpp-hocon 0.1.4 cpp-pcp-client 1.4.0 curl 7.51.0 dmidecode 2.12 facter 3.6.2 hiera 3.3.1 leatherman 0.11.1 libxml2 2.9.4 libxslt 1.1.29 marionette-collective 2.10.2 openssl 1.0.2j puppet 4.9.4 puppet-ca-bundle 1.0.7 pxp-agent 1.4.1 ruby-2.1.9 2.1.9 ruby-augeas 0.5.0 ruby-shadow 2.3.3 ruby-stomp 1.3.3 rubygem-deep-merge 1.0.1 rubygem-fast_gettext 1.1.0 rubygem-gettext 3.2.2 rubygem-gettext-setup 0.10 rubygem-hocon 1.1.3 rubygem-locale 2.1.2-2 rubygem-net-ssh 2.9.2 rubygem-semantic_puppet 0.1.2 rubygem-text 1.3.1 runtime shellpath 2015-09-18 virt-what 1.14 Distribution: (none) Priority: Normal
Jira (PUP-7046) Update dnf provider to support future Fedora releases
Title: Message Title Michael Watters created an issue Puppet / PUP-7046 Update dnf provider to support future Fedora releases Issue Type: Improvement Assignee: Michael Watters Components: Types and Providers Created: 2016/12/22 10:06 AM Priority: Normal Reporter: Michael Watters The dnf provider is hard coded to support specific Fedora releases. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7029) dnf provider does not support Fedora 25
Title: Message Title Michael Watters created an issue Puppet / PUP-7029 dnf provider does not support Fedora 25 Issue Type: Bug Affects Versions: PUP 4.8.1 Assignee: Michael Watters Components: Types and Providers Created: 2016/12/16 1:43 PM Environment: Fedora 25 x86_64 Priority: Normal Reporter: Michael Watters The dnf provider uses a static list of release numbers and must be updated for each Fedora release. Add Comment
Jira (PUP-6861) [regression] Mount options not idempotent
Title: Message Title Michael Watters commented on PUP-6861 Re: [regression] Mount options not idempotent One thing I've noticed with bind mounts on a few servers is that the device name reported by the kernel is different than what's in fstab. For example: [root@tc-util ~]# grep git /etc/mtab /dev/vdb1 /srv/git_home xfs rw,seclabel,relatime,attr2,inode64,noquota 0 0 [root@tc-util ~]# grep git /etc/fstab /storage/git_home /srv/git_home none bind 0 0 As you can see the device names and the FS options are different. This may be confusing the agent depending on how it checks for mounted devices. cifs mounts also show a difference between what's reported by the kernel and fstab. [root@tc-util ~]# grep volumes /etc/fstab //mas-cad55/volumes /srv/mas-cad55-volumes cifs credentials=/etc/tc-credentials,dir_mode=0555 0 0 //mas-cad23/volumes /srv/mas-cad23-volumes cifs rw,uid=0,gid=54321,file_mode=0660,noperm,credentials=/etc/tc-credentials,dir_mode=0775 0 0 [root@tc-util ~]# mount | grep volume //mas-cad55/volumes on /srv/mas-cad55-volumes type cifs (rw,relatime,vers=1.0,cache=strict,username=user,domain=DOMAIND,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.0.5,file_mode=0755,dir_mode=0555,nounix,serverino,rsize=61440,wsize=65536,actimeo=1) //mas-cad23/volumes on /srv/mas-cad23-volumes type cifs (rw,relatime,vers=1.0,cache=strict,username=user,domain=DOMAIN,uid=0,forceuid,gid=54321,forcegid,addr=192.168.0.5,file_mode=0660,dir_mode=0775,nounix,serverino,noperm,rsize=61440,wsize=65536,actimeo=1) The options specified in fstab are correct, I've double checked against the mount.cifs man page and the options specified are valid. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop
Jira (PUP-6861) [regression] Mount options not idempotent
Title: Message Title Michael Watters updated an issue Puppet / PUP-6861 [regression] Mount options not idempotent Change By: Michael Watters Environment: Debian 8 , CentOS 7.2.1511 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
