Jira (PUP-9012) SELinux bindings not found.
Title: Message Title Edwin Wiles commented on PUP-9012 Re: SELinux bindings not found. Additional Information: On RedHat 7.5 systems, with Puppet Enterprise 2017.3.x installed, it does not matter whether the libselinux-ruby package is installed on the agents or not. The checks for whether or not selinux is accessible: /opt/puppetlabs/puppet/bin/ruby -e "require 'puppet'; puts Puppet.features.selinux?" always return true, even on agents where libselinux-ruby is not installed. This suggests that there was a change in the puppet-agent installation in 2018, which removed ruby support for selinux; and inadvertently damaged access to the system copy of libselinux-ruby. 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-9012) SELinux bindings not found.
Title: Message Title Edwin Wiles commented on PUP-9012 Re: SELinux bindings not found. Re-Ping? 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 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-9012) SELinux bindings not found.
Title: Message Title Edwin Wiles commented on PUP-9012 Re: SELinux bindings not found. Ping? 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 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-9012) SELinux bindings not found.
Title: Message Title Edwin Wiles commented on PUP-9012 Re: SELinux bindings not found. And I just now tried PE 2017.3.8, and it does not have the issue. The ruby/require/puts command responds 'true', so it shoudl work. I'm going to continue our installation procedure and see if it works with the actual puppet code we use. 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 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-9012) SELinux bindings not found.
Title: Message Title Edwin Wiles commented on PUP-9012 Re: SELinux bindings not found. Had a thought that the issue might be isolated to 2018.1.0, so I tried upgrading to 2018.1.2. The ruby/require/puts command reacts the same way, so it's not just 2018.1.0 that has the problem. 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 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-9012) SELinux bindings not found.
Title: Message Title
Edwin Wiles commented on PUP-9012
Re: SELinux bindings not found.
On Puppet Server Installation of libselinux-ruby I have already installed libselinux-ruby: [root@dev01puppet public]# yum install libselinux-ruby Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager This system is not registered with an entitlement server. You can use subscription-manager to register. ops_repo | 2.9 kB 00:00:00 Package libselinux-ruby-2.5-12.el7.x86_64 already installed and latest version Nothing to do Checking for what is actually installed: [root@dev01puppet public]# yum list installed | grep selinux container-selinux.noarch 2:2.21-2.gitba103ac.el7 @ops_repo libselinux.x86_64 2.5-12.el7 @anaconda/7.5 libselinux-python.x86_64 2.5-12.el7 @anaconda/7.5 libselinux-ruby.x86_64 2.5-12.el7 @InstallMedia libselinux-utils.x86_64 2.5-12.el7 @anaconda/7.5 selinux-policy.noarch 3.13.1-192.el7 @anaconda/7.5 selinux-policy-targeted.noarch 3.13.1-192.el7 @anaconda/7.5 Checklist comparing what I have to what was shown in your installation list:
[X] libselinux-ruby.x86_64 0:2.5-12.el7
[–] libselinux.x86_64
[ ] 0:2.5-11.el7
[X] 0:2.5-12.el7
[–] libselinux-utils.x86_64
[ ] 0:2.5-11.el7
[X] 0:2.5-12.el7
[–] libselinux-python.x86-64
[ ] 0:2.5-11.el7
[X] 0:2.5-12.el7
Accessibility of libselinux-ruby to puppet [root@dev01puppet public]# setenforce 1 [root@dev01puppet public]# getenforce Enforcing [root@dev01puppet public]# /opt/puppetlabs/puppet/bin/ruby -e "require 'puppet'; puts Puppet.features.selinux?" true [root@dev01puppet public]# setenforce 0 [root@dev01puppet public]# getenforce Permissive [root@dev01puppet public]# /opt/puppetlabs/puppet/bin/ruby -e "require 'puppet'; puts Puppet.features.selinux?" true On Puppet Agent Installation of libselinux-ruby Already installed: [root@dev01dpwpup ~]# yum install libselinux-ruby {{ Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager}} {{ This system is not registered with an entitlement server. You can use subscription-manager to register.}} {{ Package libselinux-ruby-2.5-12.el7.x86_64 already installed and latest version}} {{ Nothing to do}} Checking: [root@dev01dpwpup ~]# yum list installed | grep selinux {{ container-selinux.noarch 2:2.21-2.gitba103ac.el7 @ops_repo }} {{ libselinux.x86_64 2.5-12.el7 @anaconda/7.5}} {{ libselinux-python.x86_64 2.5-12.el7 @anaconda/7.5}} {{ libselinux-ruby.x86_64 2.5-12.el7 @media }} {{ libselinux-utils.x86_64 2.5-12.el7 @anaconda/7.5}} {{
Jira (BOLT-246) Bolt should ignore editor backup files.
Title: Message Title Edwin Wiles assigned an issue to Edwin Wiles Closed the issue as it is no longer relevant. Puppet Task Runner / BOLT-246 Bolt should ignore editor backup files. Change By: Edwin Wiles Resolution: Won't Do Assignee: Edwin Wiles Status: Needs Information Closed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you
Jira (BOLT-246) Bolt should ignore editor backup files.
Title: Message Title Edwin Wiles commented on BOLT-246 Re: Bolt should ignore editor backup files. I believe this issue may be closed. Since tasks are now a part of Puppet Enterprise, and appear to be working correctly, I no longer require a solution to this issue. 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 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-9012) SELinux bindings not found.
Title: Message Title Edwin Wiles created an issue Puppet / PUP-9012 SELinux bindings not found. Issue Type: Bug Affects Versions: PUP 5.5.2 Assignee: Unassigned Components: PE Created: 2018/07/23 12:02 PM Priority: Major Reporter: Edwin Wiles Puppet Version: 5.5.2 Puppet Server Version: 2018.1.0.54 OS Name/Version: RedHat 7.5 After a fresh install of the O/S, and installation of Puppet Enterprise 2018.1.2, I'm now seeing the following error messages: Debug: /Stage[main]/Gcssj::Configuration::Files/File[/var/gcssj]/seltype: SELinux bindings not found. Ignoring parameter. After searching for some time, I found that this apparently refers to not having the SELinux Ruby bindings installed. So I installed 'libselinux-ruby' (version 2.5-12.el7, it was the only version available) from the DVD used to install the O/S. Despite doing so on both the puppet server and the agent, and rebooting them, I'm still getting the same error message. Please Note: It is not possible to simply add a remote repo to the system. The system must install without any internet access. The customer requires this. Desired Behavior: Puppet should be able to install itself without difficulty, and should be able to do so without having any additional repos available. At the least, a complete list of all dependencies required for full support of all features, that are not included in the PE bundle, must be provided. Actual Behavior: Despite installing the apparently required package, puppet still fails with the same message.
Jira (PUP-7238) Yum package provider should support reinstall
Title: Message Title Edwin Wiles commented on PUP-7238 Re: Yum package provider should support reinstall I'm curious, why is this not yet fixed? I looked at 6735 and 8157, and there doesn't appear to be any explanation as to why this issue has not been fixed; just a comment in 8157 that it was removed from the epic. What am I missing? Thanks! 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 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-7808) puppet resource <...> --to_yaml mishandles structured resource values
Title: Message Title
Edwin Wiles commented on PUP-7808
Re: puppet resource <...> --to_yaml mishandles structured resource values
The gist links are identical? What I'm getting from a custom resource is the following, which is a reasonable translation into a .pp format. dpw_wsendpointremoterewriterules { 'BAR:FOO_WEBSERVICE': {{ ensure => 'present',}} {{ domain => 'BAR',}} {{ rules => [}} {{ {}} {{ 'ServicePortMatchRegexp' => '^{https://foo/webservice/}barGet$',}} {{ 'RemoteEndpointProtocol' => 'https',}} {{ 'RemoteEndpointHostname' => 'mock',}} {{ 'RemoteEndpointPort' => 8443,}} {{ 'RemoteEndpointURI' => '/webservice/bar.asmx',}} {{ 'RemoteMQQM' => '',}} {{ 'RemoteTibcoEMS' => '',}} {{ 'RemoteWebSphereJMS' => ''}} {{ }, ...}} But when I specify --to_yaml, I'm getting this half/n/half translation. The rules, which are an array of hashes are not being translated correctly. dpw_wsendpointremoterewriterules: BAR:FOO_WEBSERVICE: ensure: 'present' domain: 'BAR' rules : [ { 'ServicePortMatchRegexp' => '^{https://foo/webservice/}barGet$', 'RemoteEndpointProtocol' => 'https', 'RemoteEndpointHostname' => 'mock', 'RemoteEndpointPort' => 8443, 'RemoteEndpointURI' => '/webservice/bar.asmx', 'RemoteMQQM' => '', 'RemoteTibcoEMS' => '', 'RemoteWebSphereJMS' => '' }, ... I would instead expect to see the following: dpw_wsendpointremoterewriterules: BAR:FOO_WEBSERVICE: ensure: 'present' domain: 'BAR' rules: - 'ServicePortMatchRegexp' => '^{https://foo/webservice/}barGet$', 'RemoteEndpointProtocol' => 'https', 'RemoteEndpointHostname' => 'mock', 'RemoteEndpointPort' => 8443, 'RemoteEndpointURI' => '/webservice/bar.asmx', 'RemoteMQQM' => '', 'RemoteTibcoEMS' => '', 'RemoteWebSphereJMS' => '' - ...
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-1329) composite namevars should be more robust
Title: Message Title Edwin Wiles commented on PUP-1329 Re: composite namevars should be more robust Doesn't ":name" have to be unique? If not, then many thanks for the solution. If so, then the solution provided in the code you reference assumes that the portion being selected for by the regexp is in fact unique. But what if the title is unique only when complete? E.g. "://[/]/", where no sub-portion is guaranteed unique, but the complete title is unique. As it happens, I did manage to code around the issue, without using title_patterns, but the solution is less than optimal, as it requires an additional parameter to set the 'DOMAIN' value. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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 (BOLT-278) Bolt does not error on conflicting task files
Title: Message Title Edwin Wiles commented on BOLT-278 Re: Bolt does not error on conflicting task files Finally got around to updating. Now running version 0.16.1, and I do get the error message instead of the backup file running. Many Thanks! (Work got really busy and I didn't have time to get back to it until just recently.) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- 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-1329) composite namevars should be more robust
Title: Message Title Edwin Wiles commented on PUP-1329 Re: composite namevars should be more robust I will admit that I have no idea how to solve this, but it does need some sort of solution. If we cannot use title_patterns and "name" namevar at the same time, then there needs to be a published workaround, referenced from this ticket. I did have one thought for a workaround, but I don't know enough about ruby, or puppet, to know how to make it work. What follows is a bit of pseudo-code to at least try to get the idea across. newproperty(:parta, namevar: true) do end newproperty(:partb, namevar: true) do end newproperty(:partc, namevar: true) do end
Jira (BOLT-246) Bolt should ignore editor backup files.
Title: Message Title Edwin Wiles commented on BOLT-246 Re: Bolt should ignore editor backup files. That's definitely better than using the backup file. Many thanks! Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (BOLT-246) Bolt should ignore editor backup files.
Title: Message Title Edwin Wiles commented on BOLT-246 Re: Bolt should ignore editor backup files. No. Emacs creates a backup file with a tilde appended to the original filename. Foo.sh Is copied to Foo.sh~ To preserve the original file contents. Bolt is using the ~ file instead of the correct one. This can be very confusing as you wonder why your changes are not being used. This happens when you're trying to execute a task. Bolt task run Bar::Foo -n host1 I'm not sure why it happens. It may be due to the lexical sort order, or it may be due to the position of the file in the directory structure. In any case, common editor backup schemes should all be ignored when selecting the actual file to execute. I suppose a .boltignore file could be used, but it would still need default patterns to ignore if the user didn't create the file with an explicit list. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (BOLT-246) Bolt should ignore editor backup files.
Title: Message Title
Edwin Wiles updated an issue
Puppet Task Runner / BOLT-246
Bolt should ignore editor backup files.
Change By:
Edwin Wiles
Environment:
* Source System: CentOS 7 and Ruby 2.1.0* Target Node: RedHat 7.3 and Ruby 2.0.0p648
Acceptance Criteria:
The result must change If a file with a tilde (~) exists -- or any other backup extensions that other well known editors use appended to match the new script name -- it should be ignored .
Summary:
Remote copies of tasks Bolt should update when the local copy changes ignore editor backup files .
Issue Type:
Bug Improvement
- Write a task When an editor , I've done this in both perl and bash.File: .../myname/test_connection.sh```sh#!/usr/bin/env bashecho "Completed!"```File: .../myname/test_connection.json```json{ "description": "Test the bolt connection. Just echos Completed! upon success." like Emacs , "input_method": "environment"}```- Run the task on leaves a node.```shbolt task run myname::test_connection -n nodename -u root```Output:```Started on nodname...2017-12-09T22:02:12.368279 ERROR net.ssh.authentication.agent..."/run/user/1000/keyring/ssh"Finished on nodename: Connected! { }Ran on 1 node backup file in 0.86 seconds```- Modify the task in a way that will produce visibly different output.File: .../myname/test_connection.sh```sh#!/usr/bin/env bashecho "Completed! Two!"```- Run the task again.Output:```Started on nodename...2017-12-09T22:09:44.487621 ERROR net.ssh.authentication.agent..."/run/user/1000/keyring/ssh"Finished on nodename: Connected! { }Ran on 1 node in 0.81 seconds```- The output does not change directory , and Bolt should ignore it .
Jira (BOLT-246) Bolt should ignore editor backup files.
Title: Message Title Edwin Wiles updated an issue Puppet Task Runner / BOLT-246 Bolt should ignore editor backup files. Change By: Edwin Wiles Comment: *CORRECTION:* The real problem is that bolt does not ignore editor backup files as it should. When Emacs edits a file, it makes a copy of the original with a tilde appended. Bolt should ignore the file with the tilde. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (BOLT-246) Bolt should ignore editor backup files.
Title: Message Title Edwin Wiles updated an issue Puppet Task Runner / BOLT-246 Bolt should ignore editor backup files. Change By: Edwin Wiles Acceptance Criteria: If a file with a tilde (~) appended to the name exists -- or any other backup extensions that other well known editors use appended to the name -- it should be ignored. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (BOLT-246) Remote copies of tasks should update when the local copy changes.
Title: Message Title Edwin Wiles commented on BOLT-246 Re: Remote copies of tasks should update when the local copy changes. CORRECTION: The real problem is that bolt does not ignore editor backup files as it should. When Emacs edits a file, it makes a copy of the original with a tilde appended. Bolt should ignore the file with the tilde. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- 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 (BOLT-246) Remote copies of tasks should update when the local copy changes.
Title: Message Title
Edwin Wiles created an issue
Puppet Task Runner / BOLT-246
Remote copies of tasks should update when the local copy changes.
Issue Type:
Bug
Affects Versions:
BOLT 0.10.0
Assignee:
Unassigned
Created:
2017/12/10 9:21 AM
Environment:
Source System: CentOS 7 and Ruby 2.1.0
Target Node: RedHat 7.3 and Ruby 2.0.0p648
Priority:
Normal
Reporter:
Edwin Wiles
Write a task, I've done this in both perl and bash.
File: .../myname/test_connection.sh ```sh #!/usr/bin/env bash echo "Completed!" ``` File: .../myname/test_connection.json ```json { "description": "Test the bolt connection. Just echos Completed! upon success.", "input_method": "environment" }
```
