Is it necessary to ever lock that field? I find it irritating that I can't change the build when cloning.

+ntang

The lock on image is to prevent some unexpected behavior when image in that text box is different from the control file. That might be changed though. Michael was working on a similar change.

I fixed the  issue 485813 , when the image/build field is locked and empty when cloning a job. With the fix, in theory we are able to change the image/build now since it is passed as parameter to the server now. However, for saftey, we still lock it.

In this case when you create a new job, if validation failed, I would assume no new job created in the databsae. We should not lock any fields. Maybe you could add the specific steps to reproduce the issue. 

I don't think we will do job editing though.

I believe this is a chromeos infra issue?

Justin, can you add in steps to reproduce? 

Justin, can you add steps to repro?

1) Go to the Create Job form
2) Enter a name
3) Select Server side tests
4) Select test_suite:dummy
5) Fill in a bogus build such as 'foo/bar/LATEST'

This bug has not been touched in over a year.  It is probably no longer relevant.