Instances based off of t-w10 base ami (base-g/t-w10-2016-06-02 (ami-cbc33fa6)) are unreachable

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
2 years ago
2 years ago

People

(Reporter: markco, Assigned: q)

Tracking

Details

(Whiteboard: [windows][aws])

Attachments

(1 attachment)

Comment hidden (empty)
(Reporter)

Updated

2 years ago
Blocks: 1304065
(Reporter)

Comment 1

2 years ago
Created attachment 8803415 [details] [diff] [review]
Bug1312044.patch

Commenting out of the cron until issue is resolved.
Attachment #8803415 - Flags: review?
(Reporter)

Updated

2 years ago
Attachment #8803415 - Flags: review? → review?(arich)
Comment on attachment 8803415 [details] [diff] [review]
Bug1312044.patch

You also need to manually remove the job from aws-manager2, since this doesn't do that.
Attachment #8803415 - Flags: review?(arich) → review+
Assignee: relops → q
Whiteboard: [windows][aws]
what is left to do in this bug?
The problem still hasn't been fixed, so all of it. Q is working on figuring out what the underlying issue is.
I think this is obsolete because of the work in bug 1330999
Yeah, going to wontfix this since we aren't going to support w10 buildbot.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.