Right after installation, we wanted to edit the template network range.
This was not possible as long as that range was assigned to the vm-pool.
Problem was:
You cannot save vm-pool without nw range being assigned.
Workaround:
We had to create a temporary nw range, assign that to the vm-pool.
Then we could edit the original template nw range, reassign it to the vm-pool and delete the temp. nw range.
The whole thing is user unfriendly.
The vm-subnet should not be locked when it's not really being used, even when it's assigned to a vm-pool.
Or alternatively you should be able to save vm-pool with no nw-range, if the vm-pool is not being used.
Log in to post a comment.
