Closed
Bug 829128
Opened 11 years ago
Closed 11 years ago
fakedevices support for SUT checks
Categories
(Testing Graveyard :: Mozpool, defect)
Testing Graveyard
Mozpool
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
References
Details
Attachments
(1 file)
4.91 KB,
patch
|
mcote
:
review+
|
Details | Diff | Splinter Review |
Now that we have mozpool talking to SUT, we'll need support for that in the fake devices.
Assignee | ||
Comment 1•11 years ago
|
||
On the staging server, I have all images configured with has_sut_agent=0 temporarily.
Assignee | ||
Comment 2•11 years ago
|
||
This uncovered two bugs. 1. When using SUT to reboot, the state machine was not setting up the PXE config first. This was easy to fix (the first hunk). 2. The PowerCycleMixin uses data.device_has_sut_agent to determine whether the device has a SUT agent. However, this is based on device.last_image_id, which was reset in on_please_image(). I think the fix for #2 is to add a next_image_id column to the devices table, and use *that* to store the desired image while retrying the reboot, rather than sticking it in (nominally incorrect) last_image_id column.
Assignee: nobody → dustin
Attachment #707267 -
Flags: review?(mcote)
Comment 3•11 years ago
|
||
Comment on attachment 707267 [details] [diff] [review] bug829128.patch Review of attachment 707267 [details] [diff] [review]: ----------------------------------------------------------------- Looks good. And yeah, I think it makes sense to have next_image_id.
Attachment #707267 -
Flags: review?(mcote) → review+
Assignee | ||
Comment 4•11 years ago
|
||
I'll land this after 2.0.2.
Assignee | ||
Comment 5•11 years ago
|
||
landed.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 7•11 years ago
|
||
That's getting rolled into what's turning out to be a big overhaul that will already cover several bugs, so no, I don't think so. Good catch though!
Updated•8 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•