Closed
Bug 703619
Opened 13 years ago
Closed 13 years ago
Return these slaves to production: moz2-linux-slave04 & moz2-linux64-slave07
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P3)
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!
Updated•13 years ago
|
Assignee: server-ops-releng → jwatkins
colo-trip: --- → sjc1
Updated•13 years ago
|
Assignee: jwatkins → mlarrain
Comment 1•13 years ago
|
||
moz2-darwin10-slave10 is being reimaged right now and the other two are VM's I will start them shortly.
Status: NEW → ASSIGNED
Updated•13 years ago
|
colo-trip: sjc1 → ---
Comment 2•13 years ago
|
||
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.
Comment 3•13 years ago
|
||
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.
Comment 4•13 years ago
|
||
moz2-linux-slave04 is imaged and needs releng to configure its hostname and verify.
Updated•13 years ago
|
Assignee: mlarrain → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: zandr → release
| Reporter | ||
Comment 5•13 years ago
|
||
I can't have access to moz2-darwin10-slave10. Could you please have a look at it?
Comment 6•13 years ago
|
||
The image for these machines is very old. I gave armen the correct (old) cltbld pw.
| Reporter | ||
Comment 7•13 years ago
|
||
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
| Reporter | ||
Updated•13 years ago
|
Summary: Please re-image these slaves → Return these slaves to production: moz2-darwin10-slave10, moz2-linux-slave04 & moz2-linux64-slave07
Updated•13 years ago
|
Priority: -- → P3
| Reporter | ||
Comment 8•13 years ago
|
||
(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
Comment 10•13 years ago
|
||
found in triage.
Component: Release Engineering → Release Engineering: Machine Management
QA Contact: release → armenzg
Has this been fixed?
Comment 12•13 years ago
|
||
None of these hosts even exist anymore.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Updated•7 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•