Last modified: 2014-10-01 13:39:46 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T73411, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 71411 - wikidata-jenkins* instances needs puppet update
wikidata-jenkins* instances needs puppet update
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Continuous integration (Other open bugs)
wmf-deployment
All All
: Unprioritized normal (vote)
: ---
Assigned To: Addshore
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-09-29 12:56 UTC by Antoine "hashar" Musso (WMF)
Modified: 2014-10-01 13:39 UTC (History)
9 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Antoine "hashar" Musso (WMF) 2014-09-29 12:56:36 UTC
Labs op Andrew Bogott merged a few changes in operations/puppet.git to point instances to a new LDAP server. See announcement on labs-l:

https://lists.wikimedia.org/pipermail/labs-l/2014-September/002955.html

Unfortunately a few Wikidata Jenkins slaves instances are using role::puppet::self and thus are not self updating. The whole list can be found at https://wikitech.wikimedia.org/wiki/Ldap_rename#Instances_in_Danger

Among others:

wikidata-builder3
wikidata-jenkins1
wikidata-jenkins2
wikidata-jenkins3


Addshore is probably the most qualified since he has set up the instances originally.


A rebase of the local puppet repo would be needed to have them updated.  Might want to do them one after the other to make sure nothing breaks.
Comment 1 Addshore 2014-09-29 14:01:31 UTC
If I don't appear to do this within the week please give this ticket a poke! :)
Comment 2 Jan Zerebecki 2014-09-29 15:22:13 UTC
What blocks these from being on the normal puppet master?
Comment 3 Addshore 2014-09-29 15:26:23 UTC
The builder instances use:
https://github.com/wmde/puppet-builder
The jenkins instances use:
https://github.com/wmde/puppet-composer
(also has class ci::slave::labs applied)

See docs at https://wikitech.wikimedia.org/wiki/Nova_Resource:Wikidata-build

Simply pulling everything else from master shouldn't be an issue,everything custom we use are in these pretty modules that don't really rely on other things!
Comment 4 Jan Zerebecki 2014-09-29 22:16:20 UTC
Those puppet failures after trying with an updated operations/puppet.git ( see https://bugzilla.wikimedia.org/show_bug.cgi?id=71419#c3 for the error ) on wikidata-builder3.eqiad.wmflabs are now solved. The problem was probably that old package versions of puppet and puppetmaster were not working well with the current puppet code.

Solved this by removing manifests/role/mariadb.pp and manifests/role/phabricator.pp . Then after a half working run it failed after puppet changed /etc/puppet/auth.conf . Tweaking that file made the next run go through. After a few more runs there was no change anymore. Then did an apt-get upgrade and another two puppet runs.

Perhaps first doing an apt-get upgrade and only after that running puppet with the updated repo will work better?

(Warning!: During apt-get upgrade the ldap config will become incorrect which would mean not being able to log in anymore until it gets corrected by running puppet, so take care.)
Comment 5 Jan Zerebecki 2014-09-30 17:38:26 UTC
All updated now.
Comment 6 Antoine "hashar" Musso (WMF) 2014-10-01 13:39:46 UTC
And https://wikitech.wikimedia.org/wiki/Ldap_rename#Instances_in_Danger has been updated.  Thank you Jan!

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links