Last modified: 2014-03-31 15:40:15 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 T65141, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 63141 - Project 'catgraph' migration
Project 'catgraph' migration
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
Infrastructure (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 62042
  Show dependency treegraph
 
Reported: 2014-03-26 20:28 UTC by Johannes Kroll (WMDE)
Modified: 2014-03-31 15:40 UTC (History)
2 users (show)

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


Attachments

Description Johannes Kroll (WMDE) 2014-03-26 20:28:11 UTC
Hello there, 

the VMs in the catgraph project haven't been migrated yet and are currently mothballed. Could somebody please "un-mothball" the data and copy the VMs to eqiad. 

The instances sylvester and tom should be copied. 'puppettests' was just for trying things out, it can be deleted.

Thanks.
Comment 1 Andrew Bogott 2014-03-26 20:49:27 UTC
OK, I've brought up those two instances and gotten puppet running again.  I've also set up a new IP and hostname so that sylvester.wmflabs.org points to the new sylvester instance.

You may need to do some salvage work to get stuff out of your old home or /data/project dirs.  Copies of the old directories can be reached on the new instances in the 'glustercopy' or 'pmtpa_nfs_copy' subdirs of the shared volumes /home and /data/project.
Comment 2 Johannes Kroll (WMDE) 2014-03-28 17:11:37 UTC
Yesterday I had trouble with sudo, which gave an error similar to:
	sudo: ldap_start_tls_s(): Connect error
then asking for a password. With no password set on the accounts, and no root password set, it seemed I had no way to do instance-wide changes... 

Strangely, when I logged in today, sudo worked normally. Did anybody see this before?

Anyway, the data seems to be all there. I guess this can be closed. Thanks.

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


Navigation
Links