Closed
Bug 678992
Opened 13 years ago
Closed 13 years ago
remove /system/etc/hosts from tegras and check for it during cleanup/config
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jmaher, Assigned: bear)
References
Details
(Whiteboard: [android][tegra][talos])
Attachments
(1 file)
1.26 KB,
patch
|
mozilla
:
review+
bear
:
checked-in+
|
Details | Diff | Splinter Review |
as per:
https://bugzilla.mozilla.org/show_bug.cgi?id=662936#c64
we should remove /system/etc/hosts from the tegras. Lets do this in staging and get a few runs of all the tests first before rolling this out.
Ideally this would be a step added to imaging the tegras, but we can roll this out via SUTAgent also to fix our existing tegras.
Here is some sample code that handles the removal of the file:
import devicemanager
dm = devicemanager.DeviceManager('192.168.1.101', 20701)
if dm.fileExists('/system/etc/hosts'):
dm.sendCMD(['exec mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system'])
dm.sendCMD(['exec rm /system/etc/hosts'])
if dm.fileExists('/system/etc/hosts'):
print "failed to remove /system/etc/hosts"
else:
print "successfully removed hosts file, we can test!!!"
dm.reboot()
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → bear
Whiteboard: [android][tegra][talos]
Reporter | ||
Comment 1•13 years ago
|
||
we should be able to throw a check into our cleanup.py/config.py if this file exists. If so, we can delete and reboot, otherwise we just continue on.
This would result in a one time hit on all our tegras, then after that about 1 second of overhead while we check for the file.
We should still adjust our tegra imaging documents to include removing this file.
Summary: remove /system/etc/hosts from tegras → remove /system/etc/hosts from tegras and check for it during cleanup/config
Assignee | ||
Comment 2•13 years ago
|
||
assigning to aki so he can "sanity check" our thought that this is something to do across all of the tegras via the cleanup step.
Assignee: bear → aki
Assignee | ||
Comment 3•13 years ago
|
||
realized I should just give aki a patch to review instead of relying oh his paranormal powers to read my mind
Assignee: aki → bear
Attachment #553608 -
Flags: review?(aki)
Comment 4•13 years ago
|
||
Comment on attachment 553608 [details] [diff] [review]
add hosts file removal to cleanup step
I think we do after a resolution change (though it's in an if statement so may not always run) and after installation by default (though it's assumed it'll happen).
As long as one of those two things (or something else after this step) reboots, this looks good.
Attachment #553608 -
Flags: review?(aki) → review+
Assignee | ||
Comment 5•13 years ago
|
||
Comment on attachment 553608 [details] [diff] [review]
add hosts file removal to cleanup step
committed changeset 1726:983b1cca058e
Attachment #553608 -
Flags: checked-in+
Assignee | ||
Comment 6•13 years ago
|
||
deployed to all of the foopies and watched tegra-032 have a good cleanup.py run
Assignee | ||
Comment 7•13 years ago
|
||
except for "normal" tegra environment related purples, it's been a solid green for the most part.
closing bug as FIXED
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•