Closed
Bug 994737
Opened 10 years ago
Closed 10 years ago
Spot instances don't have security group set properly
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: rail)
Details
Attachments
(1 file, 1 obsolete file)
|
9.80 KB,
patch
|
catlee
:
review+
rail
:
checked-in+
|
Details | Diff | Splinter Review |
All our spot instances are using the 'default' security group. They should be using the appropriate build/test security groups.
|
Assignee | |
Comment 1•10 years ago
|
||
The network interfaces have "default", we need to change that.
Assignee: nobody → rail
|
|
Assignee | |
Comment 2•10 years ago
|
||
Attachment #8406235 -
Flags: review?(catlee)
|
|
Assignee | |
Comment 3•10 years ago
|
||
Also for bld-linux64
Attachment #8406235 -
Attachment is obsolete: true
Attachment #8406235 -
Flags: review?(catlee)
Attachment #8406277 -
Flags: review?(catlee)
|
|
Assignee | |
Comment 4•10 years ago
|
||
The test slaves have been in the proper security group since yesterday and they look fine. I'm switching the build slaves to the corresponding security group ATM (I tested 2 slaves in different regions).
|
Reporter | |
Updated•10 years ago
|
Attachment #8406277 -
Flags: review?(catlee) → review+
|
|
Assignee | |
Comment 5•10 years ago
|
||
Comment on attachment 8406277 [details] [diff] [review] sg-cloud-tools-1.diff http://hg.mozilla.org/build/cloud-tools/rev/576b902a23e2
Attachment #8406277 -
Flags: checked-in+
|
|
Assignee | |
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
|
||
Updated•6 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•