Comment 1 for bug 1650396

Hi Sam,

Thanks for filing the bug report. We are aware of the limited and it was placed intentionally until the use case arises.

The way this is meant to work is:

1. 'allocate' machine
2. make network config changes
3. deploy
4. Once machine is not needed, 'release'.
5. Network changes in (2) get rolled-back to how the machine was before (1).

This approach is currently applied for storage (i.e. if you make changes for storage when the machine is allocated to an admin, once released, it will be rolled back to how it was before), and it is meant to ensure the machine can be re-used and to allow each different user to make its own configuration when using the specific machine.

So, this would allow you to:

'Acquire' -> (configure interface) -> 'Deploy'