You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the HCL example as in the bottom of this issue, sometimes such error may occur during destroy operation:
Error: error removing vApp network: operation error: task did not complete successfully: [400:BAD_REQUEST] - [ 86acce78-d07e-4a3e-bba3-8d663d1aff15 ] Invalid NAT rule containing vAppScopedVmId 97cc3db5-6c74-41f3-b12e-45601fd28dfd and nic index 0. Either the VM is not connected to the network or it is configured with DHCP addressing mode. NAT rule cannot be configured for nics with DHCP addressing mode. - task error: [400 - BAD_REQUEST] [ 86acce78-d07e-4a3e-bba3-8d663d1aff15 ] Invalid NAT rule containing vAppScopedVmId 97cc3db5-6c74-41f3-b12e-45601fd28dfd and nic index 0. Either the VM is not connected to the network or it is configured with DHCP addressing mode. NAT rule cannot be configured for nics with DHCP addressing mode.
During investigation we proved that if vApp is actually powered off during removal - then deletion works fine (UI also does not allow to remove vApp networks if vApp is running). There is a need to evaluate a proper way to handle vApp state during network removal (evaluate if powering it off during network removal makes sense, or should be tackled somehow differently).
With the HCL example as in the bottom of this issue, sometimes such error may occur during
destroy
operation:During investigation we proved that if vApp is actually powered off during removal - then deletion works fine (UI also does not allow to remove vApp networks if vApp is running). There is a need to evaluate a proper way to handle vApp state during network removal (evaluate if powering it off during network removal makes sense, or should be tackled somehow differently).
The text was updated successfully, but these errors were encountered: