Closed Bug 703619 Opened 13 years ago Closed 12 years ago

Return these slaves to production: moz2-linux-slave04 & moz2-linux64-slave07

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

x86
macOS

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Unassigned)

References

Details

These 3 slaves came back from a loan in bug 681328:
* moz2-darwin10-slave10 (10.2.90.140)
* moz2-linux-slave04 (10.2.71.18)
* moz2-linux64-slave07 (10.2.90.73)

Thanks!
Assignee: server-ops-releng → jwatkins
colo-trip: --- → sjc1
Assignee: jwatkins → mlarrain
moz2-darwin10-slave10 is being reimaged right now and the other two are VM's I will start them shortly.
Status: NEW → ASSIGNED
colo-trip: sjc1 → ---
Powered down old VM and renamed to moz2-linux64-slave07-old

Deploying image from template - moz2-linux64-template

moz2-linux64-slave07 

Will update mac address in svn as soon as it finishes deploying and will power up to verify success.
moz2-linux64-slave07 has been reimaged and DHCP has been updated. This VM now needs releng to update its hostname and let me know that I can delete the old one. Starting on moz2-linux-slave04 now.
moz2-linux-slave04 is imaged and needs releng to configure its hostname and verify.
Assignee: mlarrain → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: zandr → release
I can't have access to moz2-darwin10-slave10. Could you please have a look at it?
The image for these machines is very old.  I gave armen the correct (old) cltbld pw.
I tried syncing it up for one of the interns but it seems that they are good.

I tried this but did not work:
moz2-darwin10-slave10:~ cltbld$ sudo puppetd --test --server mpt-production-puppet.build.mozilla.org
warning: peer certificate won't be verified in this SSL session
notice: Got signed certificate
warning: Certificate validation failed; consider using the certname configuration option
err: Could not retrieve catalog: Certificates were not trusted: hostname was not match with the server certificate
warning: Not using cache on failed catalog

I will leave this for now.
Status: ASSIGNED → NEW
Summary: Please re-image these slaves → Return these slaves to production: moz2-darwin10-slave10, moz2-linux-slave04 & moz2-linux64-slave07
Priority: -- → P3
(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #7)
> I tried syncing it up for one of the interns but it seems that they are good.
> 
> I tried this but did not work:
> moz2-darwin10-slave10:~ cltbld$ sudo puppetd --test --server
> mpt-production-puppet.build.mozilla.org

DUH! Because it is not a production slave! This is done now. Removing from subject.
Summary: Return these slaves to production: moz2-darwin10-slave10, moz2-linux-slave04 & moz2-linux64-slave07 → Return these slaves to production: moz2-linux-slave04 & moz2-linux64-slave07
found in triage.
Component: Release Engineering → Release Engineering: Machine Management
QA Contact: release → armenzg
None of these hosts even exist anymore.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.