Jira (PUP-1751) PR (2383): Suse chkconfig --check boot.service always returns 1 whether the service is enabled/disabled. - m4ce
Title: Message Title gepetto-bot created an issue Puppet / PUP-1751 PR (2383): Suse chkconfig --check boot.service always returns 1 whether the service is enabled/disabled. - m4ce Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 23/Feb/14 11:47 AM Labels: github Priority: Normal Reporter: gepetto-bot Suse chkconfig --check boot.service always returns 1 whether the service is enabled/disabled. Author: Matteo Company: Github ID: m4ce Pull Request 2383 Discussion Pull Request 2383 File Diff Pull Request Description
Jira (PUP-1752) notes_url cannot handle hash-tags (#) within URLs for anchors in html pages
Title: Message Title redmine.exporter created an issue Puppet / PUP-1752 notes_url cannot handle hash-tags (#) within URLs for anchors in html pages Issue Type: Bug Assignee: Unassigned Created: 23/Feb/14 12:57 PM Labels: redmine Priority: Normal Reporter: redmine.exporter We tried to add a notes URL to one of our checks like this: nagios_service { check_postgresql_cluster_connection: ensure = present, host_name = 'postgresql-cluster.example.com', service_description = 'Check PG-Cluster Connection', check_command = check_postgresql_cluster_connection!10.10.10.5, notes_url = 'http://bucardo.org/check_postgres/check_postgres.pl.html#connection', use = 'generic-service', } The notes_url is used correctly and i can click that URL in nagios and it works like expected but with EVERY puppet run the check is modified like this: notice: /Stage[main]/Nagios::Server/Nagios_service[check_postgresql_cluster_connection]/notes_url: notes_url changed 'http://bucardo.org/check_postgres/check_postgres.pl.html' to 'http://bucardo.org/check_postgres/check_postgres.pl.html#connection' info: /Stage[main]/Nagios::Server/Nagios_service[check_postgresql_cluster_connection]: Scheduling refresh of Service[omd] Can anyone help? I just tried to urlencode the # to %23 but then the Server returns a 404.
Jira (PUP-1055) invalid byte sequence with service provider upstart
Title: Message Title Patrick Hemmer updated an issue Puppet / PUP-1055 invalid byte sequence with service provider upstart Change By: Patrick Hemmer IamsometimesgettinginvalidbytesequenceinUS-ASCIIwhenusingtheServicetypewiththeupstartprovider.(Iamnotmanuallysetting`provider='upstart'`,itisbeingsetbasedonOSdetection).Theproblemseemstorandomlypopup,andthengoesawayonitsown.Ididmanagetocapturetheoutputof`agent--trace`duringonerunwhentheissueoccurred.ThisiswithUbuntu12.04.1andruby1.9.3-p0 pre {code}
Jira (PUP-1753) PR (2384): (pup-1505) Correct require - kylog
Title: Message Title gepetto-bot created an issue Puppet / PUP-1753 PR (2384): (pup-1505) Correct require - kylog Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 23/Feb/14 10:41 PM Labels: github Priority: Normal Reporter: gepetto-bot (pup-1505) Correct require Author: Kylo Ginsberg Company: Github ID: kylog Pull Request 2384 Discussion Pull Request 2384 File Diff Pull Request Description The previous patch for pup-1505 changes to use a facter top-level method (rather than one buried