If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Status

Release Engineering
General
RESOLVED FIXED
6 years ago
4 years ago

People

(Reporter: bear, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [buildduty][tegra])

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
tegra-230 and tegra-268 are refusing to play nice with the others.

multiple PDU hits and they still are offline
(Reporter)

Updated

6 years ago
colo-trip: --- → mtv1
Whiteboard: [buildduty][tegra]
Assignee: server-ops-releng → jwatkins
tegra-268 come up after a pdu cycle
tegra-230 has unpredictable results during boot up.  sometimes it boots, sometimes it doesn't. So I have replaced tegra-230 with tegra-287
Assignee: jwatkins → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: zandr → release

Updated

6 years ago
Priority: -- → P3
(Reporter)

Comment 2

6 years ago
this should have been done by me - I'll knock it out in the morning
Assignee: nobody → bear
(Reporter)

Comment 3

6 years ago
tegras.json change and foopy19 updating done

committed changeset 2119:68d9f03adb0f
(Reporter)

Updated

6 years ago
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED

Comment 4

6 years ago
Please add the tegra to the *config.py so tegra-287 stops trying to connect without the buildmaster knowing about it.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Reporter)

Comment 5

6 years ago
Created attachment 589575 [details] [diff] [review]
off by one fix for tegra range in *_config.py
Attachment #589575 - Flags: review?(aki)

Updated

6 years ago
Attachment #589575 - Flags: review?(aki) → review+
(Reporter)

Comment 6

6 years ago
Comment on attachment 589575 [details] [diff] [review]
off by one fix for tegra range in *_config.py

committed changeset 5311:a14143c88f24
Attachment #589575 - Flags: checked-in+
tegra-268 still won't stay up, do we need a new bug for it at this point?
(Reporter)

Comment 8

6 years ago
tegra 268 needs to be marked for recovery - placing into the buildduty queue
Assignee: bear → nobody
Priority: P3 → --
(Reporter)

Comment 9

6 years ago
closing - tegra-268 is up and running
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.