State race when updating container config #5533
Labels
area/vsphere
Intergration and interoperation with vSphere
kind/defect
Behavior that is inconsistent with what's intended
priority/p2
source/customer
Reported by a customer, directly or via an intermediary
Comments
hickeng
added
area/vsphere
|
Bug1985862 may deal with this via other means - by preventing existing keys from becoming volatile irrespective of power state. |
|
bugzilla bug is resolved. we can close this. |
|
bug1898149 has been closed but it was closed as "not a bug" meaning vSphere is functioning as expected. That just means that the vSphere semantics do not match what we require for VIC, not that the problem has been resolved. I'm not reopening this bug for now but am noting the the root cause has not been fixed. |
hickeng
added a commit
to hickeng/vic
that referenced
this issue
May 13, 2020
The Name field was changed to be hidden from the guest in vmware#4134 to support docker rename. This was a compromise needed due to an ESX vigor bug, see vmware#5533. This *requires* that users be on a version of ESX that has the fix or bad things may happen to cVM configurations. I have not tracked down what build versions that entails and have not code a check mechanism. This change has the effect of the hostname of the VCH endpointVM being set to the name of the VCH. It also allows additional live reconfiguration such as hotadd to a bridge network, in general modification of all container configuration live is possible, if not necessarily applied.
ading007
pushed a commit
to ading007/vic
that referenced
this issue
Jun 1, 2020
The Name field was changed to be hidden from the guest in vmware#4134 to support docker rename. This was a compromise needed due to an ESX vigor bug, see vmware#5533. This *requires* that users be on a version of ESX that has the fix or bad things may happen to cVM configurations. I have not tracked down what build versions that entails and have not code a check mechanism. This change has the effect of the hostname of the VCH endpointVM being set to the name of the VCH. It also allows additional live reconfiguration such as hotadd to a bridge network, in general modification of all container configuration live is possible, if not necessarily applied.
ading007
pushed a commit
to ading007/vic
that referenced
this issue
Jun 1, 2020
The Name field was changed to be hidden from the guest in vmware#4134 to support docker rename. This was a compromise needed due to an ESX vigor bug, see vmware#5533. This *requires* that users be on a version of ESX that has the fix or bad things may happen to cVM configurations. I have not tracked down what build versions that entails and have not code a check mechanism. This change has the effect of the hostname of the VCH endpointVM being set to the name of the VCH. It also allows additional live reconfiguration such as hotadd to a bridge network, in general modification of all container configuration live is possible, if not necessarily applied.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Follow on from #5445
The work delivered for #5445 significantly reduces the probability of hitting this scenario, but requires a vSphere fix to completely resolve, or moving off guestinfo (probably to #4062 but that itself has a similar potential issue in #4064).
This issue is to track the eventual vSphere solution to the problem, bug1898149
Estimate set to 1 - should be revised if vSphere response is working as designed.
@mdubya66 We need a label or similar for tracking product issues that impact us, or would this be
product/vsphere?The text was updated successfully, but these errors were encountered: