Closed Bug 588420 Opened 14 years ago Closed 14 years ago

build vpn can't resolve tools-staging-master.mv.mozilla.com

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: anodelman, Unassigned)

References

Details

This is so sendchanges can be sent from build masters to the new auto tools staging environment. From irc: catlee: I can telnet to both ports by IP catlee: so looks like just dns needs fixing up
Blocks: 586828
Summary: build vpn needs to be able to reach tools-staging-master.mv.mozilla.com → build vpn can't resolve tools-staging-master.mv.mozilla.com
This is holding up progress on a couple of projects. Do we have an ETA on this fix, or are y'all still investigating?
That it can't resolve is somewhat by design. Hosts that need to be resolvable in both locations are under build.mozilla.org. I crammed in a fix but the real fix is to move that hostname to build.mozilla.org.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Still having trouble getting sendchanges from build masters to the new tools staging master.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
@alice - I need more details. I need to know source and destination hosts.
This bug either needs to morph or be closed and spawn a new one. The original issue has been fixed.
Issue turned out to not be the dns problem (which was fixed) but that the tools-staging-master vm couldn't keep up with the load of sendchanges. Will file separate bug for that issue. Thanks for your patience, mrz.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.