Last modified: 2012-07-27 20:34:05 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 T40747, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 38747 - fix deployment-bastion instance
fix deployment-bastion instance
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
deployment-prep (beta) (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Peter Bena
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2012-07-27 08:58 UTC by Antoine "hashar" Musso (WMF)
Modified: 2012-07-27 20:34 UTC (History)
5 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Antoine "hashar" Musso (WMF) 2012-07-27 08:58:01 UTC 
Petr has setup deployment-bastion which is not functional (can't log on it). Need to be either sorted of or recreated :-)
Comment 1 Antoine "hashar" Musso (WMF) 2012-07-27 08:59:29 UTC 
Petr would you mind taking care of deployment-bastion ?  I think it got broken because you applied puppet classes on creation. If there is nothing specific on that instance, you might want to delete it, create a new one and once created apply the classes you need.
Comment 2 Antoine "hashar" Musso (WMF) 2012-07-27 20:34:05 UTC 
So apparently that was just me having an issue. J^ was able to connect on it.

Ryan fixed my connection issue by using tail -f auth.log.  He is so great that by just looking at an issue it magically fix.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links