Closed
Bug 905142
Opened 11 years ago
Closed 11 years ago
Mozmill ESX Windows Vista machines not reachable anymore due to hostname change
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: whimboo, Assigned: afernandez)
References
Details
As of today I have noticed that the following hosts have the same hostname setup: mm-win-vista-1.qa.scl3.mozilla.com -> windows_vista (10.22.73.19) mm-win-vista-2.qa.scl3.mozilla.com -> windows_vista (10.22.73.20) mm-win-vista-3.qa.scl3.mozilla.com -> windows_vista (10.22.73.21) So I have changed the hostnames for -2 and -3 to the right one. But now after a reboot the machines are no longer accessible. Most likely they got a new IP assigned. We will have to do the same hostname change for -1 but I'm not going to do that now given that we have active tests to run. So whenever the machine is free and someone from IT is around I would appreciate the additional hostname change. Thanks.
Reporter | ||
Updated•11 years ago
|
Summary: Vista machines not reachable anymore due to hostname change → Mozmill ESX Windows Vista machines not reachable anymore due to hostname change
Assignee | ||
Comment 1•11 years ago
|
||
We chatted irc and issue was related to a previous issue with your local desktop. reminna had cert issues and was not reporting them. You cleared the cert issues and now you are able to connect.
Assignee: server-ops → afernandez
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 2•11 years ago
|
||
Yes, all is working fine now. I will also update Mana to check for proper machine names if those are getting distributed via DHCP, if not (in case of at least Windows) the name has to be adjusted manually. Thanks
Status: RESOLVED → VERIFIED
Reporter | ||
Updated•11 years ago
|
Whiteboard: [qa-automation-blocked]
Updated•9 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•