Jira (FACT-152) Add type information to network interfaces
Title: Message Title Orion Poplawski commented on FACT-152 Re: Add type information to network interfaces And FWIW, I've switched to using ansible, so I don't need it any more. 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 (PUP-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Orion Poplawski commented on PUP-4512 Re: systemctl restart puppet fails to restart puppet Perhaps it is a Fedora issue. In any case, I'm moving away from using puppet so feel free to close as I won't be able to provide any more information. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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-3931) Upgrading Puppet package within Puppet agent run on EL7 results in bad package state
Title: Message Title Orion Poplawski commented on PUP-3931 Re: Upgrading Puppet package within Puppet agent run on EL7 results in bad package state Filed PUP-4512 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Orion Poplawski commented on PUP-4512 Re: systemctl restart puppet fails to restart puppet Actually, with Fedora 22, puppet 4.0.0, the restart completes fine, but the old child process sticks around: systemctl status puppet ● puppet.service - Puppet agent Loaded: loaded (/usr/lib/systemd/system/puppet.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2015-05-01 11:09:17 MDT; 2min 3s ago Main PID: 844 (start-puppet-ag) CGroup: /system.slice/puppet.service ├─844 /bin/sh /usr/bin/start-puppet-agent agent --no-daemonize └─849 /usr/bin/ruby-mri /usr/bin/puppet agent --no-daemonize systemctl restart puppet systemctl status puppet ● puppet.service - Puppet agent Loaded: loaded (/usr/lib/systemd/system/puppet.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2015-05-01 11:11:54 MDT; 16s ago Main PID: 1622 (start-puppet-ag) CGroup: /system.slice/puppet.service ├─ 849 /usr/bin/ruby-mri /usr/bin/puppet agent --no-daemonize ├─1622 /bin/sh /usr/bin/start-puppet-agent agent --no-daemonize └─1623 /usr/bin/ruby-mri /usr/bin/puppet agent --no-daemonize so now there are two puppet agents running. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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,
Jira (PUP-4512) systemctl restart puppet fails to restart puppet
Title: Message Title Orion Poplawski created an issue Puppet / PUP-4512 systemctl restart puppet fails to restart puppet Issue Type: Bug Affects Versions: PUP 4.0.0, PUP 3.7.5 Assignee: Unassigned Created: 2015/05/01 10:07 AM Environment: Fedora Linux Labels: systemd Priority: Critical Reporter: Orion Poplawski Adding KillMode=process to puppet.service to fix PUP-3931 appears to have broken systemctl restart puppet for me. systemctl status puppet ● puppet.service - Puppet agent Loaded: loaded (/usr/lib/systemd/system/puppet.service; enabled) Active: active (running) since Fri 2015-05-01 11:02:35 MDT; 11s ago Main PID: 18662 (start-puppet-ag) CGroup: /system.slice/puppet.service ├─18662 /bin/sh /usr/bin/start-puppet-agent agent
Jira (PUP-4512) systemctl restart puppet fails to restart puppet
Title: Message Title
Orion Poplawski updated an issue
Puppet / PUP-4512
systemctl restart puppet fails to restart puppet
Change By:
Orion Poplawski
AddingKillMode=processtopuppet.servicetofixPUP-3931appearstohavebrokensystemctlrestartpuppetforme. {noformat} #systemctlstatuspuppet●puppet.service-PuppetagentLoaded:loaded(/usr/lib/systemd/system/puppet.service;enabled)Active:active(running)sinceFri2015-05-0111:02:35MDT;11sagoMainPID:18662(start-puppet-ag)CGroup:/system.slice/puppet.service├─18662/bin/sh/usr/bin/start-puppet-agentagent--no-daemonize└─18665/usr/bin/ruby-mri/usr/bin/puppetagent--no-daemonize#systemctlrestartpuppet#systemctlstatuspuppet●puppet.service-PuppetagentLoaded:loaded(/usr/lib/systemd/system/puppet.service;enabled)Active:failed(Result:exit-code)sinceFri2015-05-0111:03:03MDT;4sagoProcess:19066ExecStart=/usr/bin/start-puppet-agentagent${PUPPET_EXTRA_OPTS}--no-daemonize(code=exited,status=1/FAILURE)MainPID:19066(code=exited,status=1/FAILURE)CGroup:/system.slice/puppet.service└─18665/usr/bin/ruby-mri/usr/bin/puppetagent--no-daemonize {noformat} Theoldchildpuppetprocessisstillaround.Straceshows: {noformat} 19199restart_syscall(...resuminginterruptedcall...unfinished...19245restart_syscall(...resuminginterruptedcall...unfinished...19198wait4(-1,unfinished...19199...restart_syscallresumed)=-1ETIMEDOUT(Connectiontimedout)19199futex(0xb556d0,FUTEX_WAKE_PRIVATE,1)=019199futex(0xb55654,FUTEX_WAIT_BITSET_PRIVATE,15,{359644,166273339},unfinished...19198...wait4resumed0x7ffc8ab93080,0,NULL)=?ERESTARTSYS(ToberestartedifSA_RESTARTisset)19198---SIGTERM{si_signo=SIGTERM,si_code=SI_USER,si_pid=1,si_uid=0}---19198+++killedbySIGTERM+++19199...futexresumed)=-1ETIMEDOUT(Connectiontimedout)19199futex(0xb556d0,FUTEX_WAKE_PRIVATE,1)=019199futex(0xb55654,FUTEX_WAIT_BITSET_PRIVATE,17,{359649,166794009},detached... {noformat} I'mseeingthiswithFedora21and3.7.5andFedora22w/4.0.0.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-3931) Upgrading Puppet package within Puppet agent run on EL7 results in bad package state
Title: Message Title Orion Poplawski commented on PUP-3931 Re: Upgrading Puppet package within Puppet agent run on EL7 results in bad package state The problem with this now is that a simple systemctl restart puppet fails because the child process refuses to die: ~ ps -fe | grep puppet root 21421 1 0 16:45 ? 00:00:00 /bin/sh /usr/bin/start-puppet-agent agent --no-daemonize root 21424 21421 0 16:45 ? 00:00:01 /usr/bin/ruby-mri /usr/bin/puppet agent --no-daemonize root 22536 2094 0 16:51 pts/4 00:00:00 grep --color=auto puppet systemctl restart puppet ps -fe | grep puppet root 21424 1 0 16:45 ? 00:00:01 /usr/bin/ruby-mri /usr/bin/puppet agent --no-daemonize ~ At least for me on Fedora 21. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-941) rspec spec fails
Title: Message Title Orion Poplawski created an issue Facter / FACT-941 rspec spec fails Issue Type: Bug Affects Versions: FACT 2.4.3 Assignee: Unassigned Created: 2015/04/02 6:39 PM Environment: Fedora Priority: Normal Reporter: Orion Poplawski + cd facter-2.4.3 + rspec spec /export/home/orion/fedora/facter/facter-2.4.3/spec/puppetlabs_spec/matchers.rb:8:in `alias_method': undefined method `should' for module `RSpec::Matchers::BlockAliases' (NameError) from /export/home/orion/fedora/facter/facter-2.4.3/spec/puppetlabs_spec/matchers.rb:8:in `module:BlockAliases' from /export/home/orion/fedora/facter/facter-2.4.3/spec/puppetlabs_spec/matchers.rb:7:in `module:Matchers' from /export/home/orion/fedora/facter/facter-2.4.3/spec/puppetlabs_spec/matchers.rb:6:in `module:RSpec' from /export/home/orion/fedora/facter/facter-2.4.3/spec/puppetlabs_spec/matchers.rb:5:in `top (required)' from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require' from /export/home/orion/fedora/facter/facter-2.4.3/spec/puppetlabs_spec_helper.rb:13:in `top (required)' from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require' from
Jira (PUP-3391) Delay puppet agent startup until after network is configured
Title: Message Title Orion Poplawski created an issue Puppet / PUP-3391 Delay puppet agent startup until after network is configured Issue Type: Bug Affects Versions: PUP 3.7.1, PUP 3.6.2 Assignee: Kylo Ginsberg Components: Client Created: 06/Oct/14 11:13 AM Environment: Fedora Priority: Normal Reporter: Orion Poplawski The puppet agent can be started prior to the network being configured. Due to ruby/dns resolution issues this will prevent puppet from being able to do DNS lookups until it is restarted. We should delay startup until the network is online if possible with: Wants=basic.target network-online.target After=basic.target network-online.target
