... and restarts it. I discovered this while I was looking at the signing worker logs in papertrail. Additionally, signing-linux-1 generated ~1.3M events vs ~20K generated by others. Probably related to the initial setup?
Oct 14 00:57:01 signing-linux-1.srv.releng.use1.mozilla.com CROND: (root) CMD (. /usr/local/bin/proxy_reset_env.sh && /usr/bin/puppet agent --enable >/dev/null 2>/dev/null && /usr/bin/puppet agent --onetime --no-daemonize --logdest=syslog >/dev/null 2>&1)
Oct 14 00:57:01 signing-linux-1.srv.releng.use1.mozilla.com puppet-agent: Enabling Puppet.
Oct 14 00:57:40 signing-linux-1.srv.releng.use1.mozilla.com crontab: (root) LIST (root)
Oct 14 00:57:47 signing-linux-1.srv.releng.use1.mozilla.com puppet-agent: (/Stage[main]/Signing_scriptworker/Python35::Virtualenv[/builds/scriptworker]/Python35::Virtualenv::Package[/builds/scriptworker||frozendict==1.0]/Exec[pip /builds/scriptworker||frozendict==1.0]/returns) executed successfully
Oct 14 00:57:57 signing-linux-1.srv.releng.use1.mozilla.com puppet-agent: (/Stage[main]/Signing_scriptworker/Python35::Virtualenv[/builds/scriptworker]/Python35::Virtualenv::Package[/builds/scriptworker||slugid==1.0.7]/Exec[pip /builds/scriptworker||slugid==1.0.7]/returns) executed successfully
Oct 14 00:58:00 signing-linux-1.srv.releng.use1.mozilla.com puppet-agent: (/Stage[main]/Signing_scriptworker::Services/Exec[restart-scriptworker]) Triggered 'refresh' from 1 events
Oct 14 00:58:01 signing-linux-1.srv.releng.use1.mozilla.com puppet-agent: Finished catalog run in 28.40 seconds
re: 1.3m vs 20k, I've been using signing-linux-1 as my debugging ground since signing scriptworker isn't tier1 yet, and it's been alive for longer. Unless you mean that's within the last week or 24hrs or something.
However, reinstalling scriptworker every run is wrong, and should be fixed.
bug 1310120 - puppet reinstalls scriptworker on every run. r=rail
Created attachment 8801933 [details] [diff] [review]
Use the python3-compatible version of pip-check in the python35 module.
(In reply to Aki Sasaki [:aki] from comment #3)
> Created attachment 8801933 [details] [diff] [review]
> Use the python3-compatible version of pip-check in the python35 module.
Just to confirm, the fix is working great ;)
I was working on my beetmover puppet patches this morning and hit this problem as the python pip check would not install any dep packages in my virtualenv. After tweaking on my local environment with Aki's patch, it worked like a charm.
bug 1310120 - use the py3 compatible pip_check in py35 virtualenv. r=mtabara
Awesome. Fix is rolled out!