Closed Bug 859162 Opened 12 years ago Closed 12 years ago

Set up talos-mtnlion-r5 which were foopies

Categories

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

x86_64
macOS

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: nthomas, Assigned: armenzg)

References

Details

(Whiteboard: [buildduty][buildslaves][capacity])

Attachments

(1 file)

Setup & imaging still pending.
Machines are available now.
Hardware: x86 → x86_64
Whiteboard: [buildduty][buildslaves][capacity]
Product: mozilla.org → Release Engineering
talos-mtnlion-r5-090.test.releng.scl3.mozilla.com is alive talos-mtnlion-r5-091.test.releng.scl3.mozilla.com is alive talos-mtnlion-r5-092.test.releng.scl3.mozilla.com is alive talos-mtnlion-r5-093.test.releng.scl3.mozilla.com is alive talos-mtnlion-r5-094.test.releng.scl3.mozilla.com is alive talos-mtnlion-r5-095.test.releng.scl3.mozilla.com is alive
Assignee: nobody → armenzg
QA Contact: other → armenzg
Attachment #8340492 - Flags: review?(bhearsum)
Attachment #8340492 - Flags: review?(bhearsum) → review+
I also added them to slavealloc. We need a reconfig before rebooting them into production.
Live in production.
Enabled on slavealloc. Rebooting them into production.
Disabling them. 14:48 philor: Callek|buildduty: https://tbpl.mozilla.org/php/getParsedLog.php?id=31511649&tree=Mozilla-Inbound - I don't really recognize the failure pattern, other than "something's graphically busted here"
Rebooting them into production after DCOps added the right cables.
Priority: -- → P3
I disabled these machines. I will put them through staging. I wish I had a way to VNC to see more.
These need to get added to the graph server, too.
Flags: needinfo?(armenzg)
Flags: needinfo?(armenzg)
So far I have discovered that they have different CPUs (2.5 Core i5 versus 2.0 Core i7). I don't think that is the reason for the graphics issue but this makes them unsuitable for talos testing. I will dig a bit more. [root@talos-mtnlion-r5-090.test.releng.scl3.mozilla.com ~]# sysctl -n machdep.cpu.brand_string Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz [root@talos-mtnlion-r5-089.test.releng.scl3.mozilla.com ~]# sysctl -n machdep.cpu.brand_string Intel(R) Core(TM) i7-2635QM CPU @ 2.00GHz
Hal, the 6 machines on this bug have different specs than the mtnlion testers. We could use them as Lion builders, however, they would also have different specs. If we did, should we name them differently than bld-lion-r5 to make sure that they will not get mixed up in the future?
Flags: needinfo?(hwine)
For some reason, these appear to be "non server" models: $ braindump/mac-related/get_mac_model.sh talos-mtnlion-r5-088 talos-mtnlion-r5-090 Macmini5,3 for talos-mtnlion-r5-088 Macmini5,2 for talos-mtnlion-r5-090 According to MacTracker, 5,3 is the server model. The 5,2 is a consumer model. For builds that is close enough, so no need to mess with naming. Amy: unsure why we ended up with consumer grade - does this need to get flagged in inventory?
Flags: needinfo?(hwine) → needinfo?(arich)
Yes, that means they're not r5's. A vague recollection is that we purchased some ad-hoc minis for those foopies, with no effort to match them to the r5 spec. So Bug 848995 was a pretty expensive mistake. The inventory history says that their description was changed to say r5 on Feb 28, 2013, but not by whom. I've fixed that data in inventory. I see "r5 server" in inventory, too. There's no such thing. I'll try to fix that.
Flags: needinfo?(arich)
bug 951842 should help a bit at least.
dustin, we are considering giving these mac minis to the a-team since they have a different configuration than the rest of our pools. Is this possible?
As far as I know, yes - they are rackmountable and already in scl3, so there's no reason not to connect them to the ateam VLAN.
I am giving these machines to the A-team through bug 957218.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
I will have to undo the prep work that I did in here.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Attachment #8340492 - Flags: checked-in+ → checked-in-
mysql> select name from slaves where name like 'talos-mtnlion-r5-09%'; +----------------------+ | name | +----------------------+ | talos-mtnlion-r5-090 | | talos-mtnlion-r5-091 | | talos-mtnlion-r5-092 | | talos-mtnlion-r5-093 | | talos-mtnlion-r5-094 | | talos-mtnlion-r5-095 | +----------------------+ 6 rows in set (0.00 sec) mysql> delete from slaves where name like 'talos-mtnlion-r5-09%'; Query OK, 6 rows affected (0.01 sec)
Summary: Set up talos-r5-mtnlion which were foopies → Set up talos-mtnlion-r5 which were foopies
See Also: → 961853
Filed bug 961853 to revert any IT changes that might be left. All of our changes have been reverted.
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → INVALID
in production
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.

Attachment

General

Created:
Updated:
Size: