tfoks

I just updated to Rancher **2.6.9** and this behavior is still there. I.e. using the option "Use vApp to configure networks with network protocol profiles" leads to the above error...

I digged a little deeper and I think I found the problem. The issue don't seem to be a bug but the different way how nodes are provisioned. The main...