Closed Bug 1011334 Opened 8 years ago Closed 8 years ago

Switch in house try builds to S3 for sccache

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: glandium, Assigned: glandium)

References

Details

Attachments

(1 file)

After bug 1007976, we're using a reverse-proxy in front of S3. That reverse-proxy appears to be suffering from hard drive problems, so until we have a really production ready server, we need to switch off it. We also want to phase out ceph, so switching back to ceph by backing out bug 1007976 is not an option.
Removing the entire config besides credentials makes us switch to use S3 directly.
Attachment #8423508 - Flags: review?(bugspam.Callek)
Assignee: nobody → mh+mozilla
Status: NEW → ASSIGNED
Blocks: 1008015
Comment on attachment 8423508 [details] [diff] [review]
Switch in house try builds to S3 for sccache

Review of attachment 8423508 [details] [diff] [review]:
-----------------------------------------------------------------

puppet wise I have no objections, r?->mshal for sanity with what you're actually trying to do.
Attachment #8423508 - Flags: review?(mshal)
Attachment #8423508 - Flags: review?(bugspam.Callek)
Attachment #8423508 - Flags: review+
Interesting, while that works on Linux, it doesn't on Mac. I'll have to check why, because it doesn't make sense, both are using the same config.
OS: Linux → All
Hardware: x86_64 → All
It could be, though, that mac try builders are not allowed to reach S3.
Attachment #8423508 - Flags: review?(mshal) → review+
(In reply to Mike Hommey [:glandium] from comment #4)
> It could be, though, that mac try builders are not allowed to reach S3.

It was just my test script that was broken. Once the sed invocation is fixed, it works.
Blocks: 1013060
Attachment #8423508 - Flags: checked-in+
Checking whether the change has propagated...
This propagated to all puppet hosts:

$ echo; for host in releng-puppet1.srv.releng.scl3.mozilla.com releng-puppet2.srv.releng.scl3.mozilla.com releng-puppet1.srv.releng.use1.mozilla.com releng-puppet1.srv.releng.usw2.mozilla.com releng-puppet2.srv.releng.use1.mozilla.com releng-puppet2.srv.releng.usw2.mozilla.com releng-puppet2.build.scl1.mozilla.com; do ssh '-oStrictHostKeyChecking no' root@${host} 'hostname; hg -R /etc/puppet/production summary | head -1' 2>/dev/null; done

releng-puppet1.srv.releng.scl3.mozilla.com
parent: 1742:4940db99d64c tip
releng-puppet2.srv.releng.scl3.mozilla.com
parent: 2352:4940db99d64c tip
releng-puppet1.srv.releng.use1.mozilla.com
parent: 2352:4940db99d64c tip
releng-puppet1.srv.releng.usw2.mozilla.com
parent: 2352:4940db99d64c tip
releng-puppet2.srv.releng.use1.mozilla.com
parent: 2352:4940db99d64c tip
releng-puppet2.srv.releng.usw2.mozilla.com
parent: 2352:4940db99d64c tip
releng-puppet2.build.scl1.mozilla.com
parent: 2352:4940db99d64c tip
In production.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.