I'll lock it today, and unlock it tomorrow. A balance_pool runs nightly and should take care of that.

I've locked it. However, this device is in pool:performance . That is not one of our managed pools, so balance_pool is not going to touch it. So, I don't think this is going to accomplish what you want.

Swapping out a device from the performance pool is not really something the deputy can help much with afaik. The devices in that pool are specialized and owned by the perf team.

How can we bump the DUT's firmware to 10833.0.0?

I can bump it up but I kinda want to leave it lying around to figure out the underlying issue...

->johndhong is working on this.

Well does someone from Infra want to investigate this?  Or should I just update it?

Interesting it thinks that the firmware is up to date...
https://stainless.corp.google.com/browse/chromeos-autotest-results/hosts/chromeos2-row3-rack8-host3/63871084-verify/
https://00e9e64bac34b0966970950b83df4696960623989497c31608-apidata.googleusercontent.com/download/storage/v1/b/chromeos-autotest-results/o/hosts%2Fchromeos2-row3-rack8-host3%2F63871084-verify%2Fdebug%2Fautoserv.DEBUG?qk=AD5uMEvC92nfpVEBEv4-6A0EmlZbPYK8btJqPKn3LLfswhcKqOCaLfHd6xe5kcrSoD2TvJN5s8f3zjST62PUcyfA8HDAUqQHwcE2NXqhKqRaWw4ERgyKKEX1xnw3icJ_pUNrvuHM5QJHZn5KyQDR3O6wDkYB8o9rln1xL3wz6kfHzbUDQQ34RjPmSLZKYOR7tAqxgrgE8_Qa7IKooKkiW4WjUvfto3V3tzqA672r8FF9XI8eMxvIrCHu3lSkD8ggIvpWvv8Uu7WF3Q285LGmeCLG4eyTKlyTXqSyRIlvfKKohXjmxoeg7w7exkjC8tv9VuMsw7ODjzeczXryzJ4xAl4uAW48lBcagOod4H9Vi93-MTF_lgMbPyrADQL-rHk-ZEC_b7E22urQcS7X5WkQBwHBFy1FdL2N3GWaxf0hFVavAxd_w8uC1KaQnXPqO9pblABgJajkOq4CLPS5I5WcCnN0TAqDWpO_isvA1lqV_R_8ix2enj071W4YZYfiyXz3Tqrvjn_lq7qqQD4Qha46HpGCHSTkDNKsGrWZPVEA5h0Fb-4Hw0t47YEYku7bj1ISVYIDDbhcPwx4C_4XUMAl51g1BKkGOdUnSYYs_ApGw3KH85W4uiS8jbgAqYCr2_6xIvzYRqW6_LiJHMnrFk3xpKcatOvf5YOdNusXMRr9HHF5AFhaUPQv8oQ7GNN_GZBeWWhCK5m0Lr6-fWx-24PyM9s4TIyXyBNR5OwYcdmzycrSxAz5NCjAheJ6ge7lTJdV0xsEhsTDfQXCaVGfY7W5C_88yRtmvMaJPQvCtFmVl74kbZQYzHJcvXmWjITk7-_nPnHslE6ezQFtsrC42Gy6U9Ye87UObEkwUg

07/09 13:57:03.958 INFO |            repair:0349| Verifying this condition: Firmware on this DUT is clean
07/09 13:57:03.959 INFO |        server_job:0216|       GOOD    ----    verify.fwstatus timestamp=1531169823    localtime=Jul 09 13:57:03       
07/09 13:57:03.959 INFO |            repair:0349| Verifying this condition: The firmware on this DUT is up-to-date
07/09 13:57:03.960 INFO |        server_job:0216|       GOOD    ----    verify.rwfw     timestamp=1531169823    localtime=Jul 09 13:57:03

> I've locked it. However, this device is in pool:performance .
> That is not one of our managed pools, so balance_pool is not
> going to touch it. So, I don't think this is going to
> accomplish what you want.

For this problem, balance_pools can, and should, be run manually.
That will solve the problem.

> I can bump it up but I kinda want to leave it lying around to
> figure out the underlying issue...

The underlying issue has already been explained:  That's  bug 861867 .

It got moved to pool:suites by someone

Anyway I updated it manually

localhost ~ # chromeos-firmwareupdate -m autoupdate
Model is grunt
Starting Google_Grunt firmware updater v4 (autoupdate)...
 - Updater package: [Google_Grunt.10833.0.0 / EC:grunt_v1.1.8730-dc5ef9e35]
 - Current system:  [RO:Google_Grunt.10750.0.0 , ACT:Google_Grunt.10750.0.0 / EC:grunt_v1.1.8540-4a0bd0ced]
 - Write protection: Hardware: ON, Software: Main=off
autoupdate(recovery): update RO+RW
 * invoke: flashrom -p host --fast-verify -w models/grunt/bios.bin
autoupdate(recovery): update ec/RO+RW
 * invoke: flashrom -p ec --fast-verify -w models/grunt/ec.bin
autoupdate(recovery): EC may be restored or updated in next boot.
Firmware update (autoupdate) completed.

johndhong@phobrz:~$ ssh chromeos2-row3-rack8-host3
localhost ~ # crossystem fwid
Google_Grunt.10833.0.0

FYI - it was moved back to pool:suites by the performance pool monitoring script as it was locked.