Ok. I have re-created this problem in devstack on trunk. What I am seeing is:
- I can boot an instance with config drive. The config drive has configuration information in it.
- I block migrate that instance to another hypervisor node. The config drive is now an invalid filesystem.
Can I confirm this is the error that you are seeing?
Ok. I have re-created this problem in devstack on trunk. What I am seeing is:
- I can boot an instance with config drive. The config drive has configuration information in it.
- I block migrate that instance to another hypervisor node. The config drive is now an invalid filesystem.
Can I confirm this is the error that you are seeing?