switch Ash to proxxy-node

RESOLVED WONTFIX

Status

RESOLVED WONTFIX
4 years ago
3 years ago

People

(Reporter: gmiroshnykov, Assigned: gmiroshnykov)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

First, we need to add the following entries to inventory:

  proxxy-node1.srv.releng.use1.mozilla.com => 10.134.100.38
*.proxxy-node1.srv.releng.use1.mozilla.com => 10.134.100.38
  proxxy-node1.srv.releng.usw2.mozilla.com => 10.132.100.4
*.proxxy-node1.srv.releng.usw2.mozilla.com => 10.132.100.4
(Assignee)

Comment 1

4 years ago
Created attachment 8524592 [details] [diff] [review]
proxxy-node.patch

We should apply this patch on Ash only.
Attachment #8524592 - Flags: review?(rail)
Attachment #8524592 - Flags: review?(catlee)
I added the inventory entries
(Assignee)

Comment 4

4 years ago
Created attachment 8531586 [details] [diff] [review]
proxxy.patch

Automatically sign S3 URLs when following redirects.

This adds new Python dependency: boto
Attachment #8524592 - Attachment is obsolete: true
Attachment #8531586 - Flags: review?(rail)
Attachment #8531586 - Flags: review?(catlee)
Comment on attachment 8531586 [details] [diff] [review]
proxxy.patch

I don't think you need to push to ash-mozharness after next recofig due to bug 791924. You can use your user hg repo and push to try.
Attachment #8531586 - Flags: review?(rail)
QA Contact: pmoore → mshal

Updated

3 years ago
Attachment #8531586 - Flags: review?(catlee)

Updated

3 years ago
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.