So, it appears most of our new tegras are being brought up now, I already see a good chunk nagios-alerting on me. To do this part of the work, I need PDU info, is that data in inventory, or should I call out for an explicit csv of the PDU info for each of these new tegras?
The data is in inventory, yes.
Created attachment 651169 [details] [diff] [review] [tools] v1 So, this adds them all to tegras.json I still need to finish my verification of all these PDU's, but I stopped that temporarily since I might need to change the info pending outcome of Bug 782099
Assignee: nobody → bugspam.Callek
Status: NEW → ASSIGNED
Attachment #651169 - Flags: review?(coop)
Comment on attachment 651169 [details] [diff] [review] [tools] v1 Also note, tegra-303 is missing from the json, since it was DOA, will mark it as Decom in slavealloc if you want though.
Created attachment 652499 [details] slavealloc adds [csv] This includes the 4 decomm tegras as listed in Bug 767447
Attachment #652499 - Flags: review?(coop)
Comment on attachment 652499 [details] slavealloc adds [csv] Everything up to tegra-316 has already been added. You'll want to double-check the info in the db for them, but the rest of the additions look OK.
Attachment #652499 - Flags: review?(coop) → review+
Done... I had to manually adjust the earlier tegras to account for all this data, and add notes to "staging/new" and remove "enabled" from all the newly added ones from webUI though
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
removed dependence on bug 767447, as it "masks" a number of still-open bugs in the Bugzilla dependency tree view.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.