Page MenuHomePhabricator

deployment-parsoid06 puppet fails due to having role::parsoid::beta (requiring upstart) on jessie
Closed, DeclinedPublic

Description

@ssastry created this host around 9 hours ago
I noticed shinken was showing it as connection refused (doesn't have the rules for shinken-01?), logged in to find puppet was broken due to the exim issue. Updated packages to fix exim, but the next puppet error was this:

krenair@deployment-parsoid06:~$ sudo puppet agent -tv
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Info: Caching catalog for deployment-parsoid06.deployment-prep.eqiad.wmflabs
Info: Applying configuration version '1462239621'
Error: /Stage[main]/Role::Parsoid::Beta/Service[parsoid]: Provider upstart is not functional on this host
Notice: Finished catalog run in 15.22 seconds
krenair@deployment-parsoid06:~$ lsb_release -c
Codename:	jessie

Event Timeline

hashar added a subscriber: hashar.

Looks like production is still on Trusty as well.

In puppet one will have to change to base::service_unit() an example is 3b30e913eca304558391d73555ec5b44981c4b24

Krenair renamed this task from deployment-parsoid06 parsoid fails due to having role::parsoid::beta (requiring upstart) on jessie to deployment-parsoid06 puppet fails due to having role::parsoid::beta (requiring upstart) on jessie.May 7 2016, 3:50 AM

This is no longer relevant. We are in the process of migrating Parsoid to service-runner, jessie, and node v4.