Closed Bug 833956 Opened 11 years ago Closed 11 years ago

not all AWS slaves are accessible via ssh at all times

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED WONTFIX

People

(Reporter: hwine, Unassigned)

References

Details

During 19.0b3 release, various errors required access to AWS slaves to debug upload issues.

The slaves were not listening on port 22 - :nthomas had to enable something to allow that.

Production slaves should be accessible via ssh at all times.
Only if we have an infinite budget to keep AWS VMs running all the time. I suggest we bootstrap you on using the Amazon console.
Bug 834076 will make this process a little bit easier.
See Also: → 834076
Component: Release Engineering: Automation (Release Automation) → Release Engineering: Platform Support
QA Contact: bhearsum → coop
we don't want to keep them running all the time. we've beefed up our tooling so that buildduty can turn them on easily.

https://wiki.mozilla.org/ReleaseEngineering/How_To/Manage_AWS_slaves
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
wfm - they are accessible now
Status: RESOLVED → VERIFIED
Product: mozilla.org → Release Engineering
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.