715219 - tegra recovery

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Mike Taylor [:bear]]

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

multiple PDU hits and they still are offline

Comment 1

[Jake Watkins [:dividehex]]

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

Comment 2

[Mike Taylor [:bear]]

this should have been done by me - I'll knock it out in the morning

Comment 3

[Mike Taylor [:bear]]

tegras.json change and foopy19 updating done

committed changeset 2119:68d9f03adb0f

Comment 4

[Aki Sasaki (not active)]

Please add the tegra to the *config.py so tegra-287 stops trying to connect without the buildmaster knowing about it.

Comment 5

[Mike Taylor [:bear]]

Attachment: off by one fix for tegra range in *_config.py

Comment 6

[Mike Taylor [:bear]]

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

committed changeset 5311:a14143c88f24

Comment 7

[[e-mail] (:bhearsum)]

tegra-268 still won't stay up, do we need a new bug for it at this point?

Comment 8

[Mike Taylor [:bear]]

tegra 268 needs to be marked for recovery - placing into the buildduty queue

Comment 9

[Mike Taylor [:bear]]

closing - tegra-268 is up and running