Currently there is no resolution.
This issue will be fixed in VCF versions 3.10.2.2 & 3.11.x.x.
For more information about VCF Build Numbers, see
Correlating VMware Cloud Foundation version with the versions of its constituent products (52520)Workaround:
To workaround this issue, please follow the below steps:
- Get current workflow context into spec.json.
- Backup spec.json.
cp spec.json spec-bk.json
- Update spec.json.
--->Look for element with "vmkernelInterfaceToSegmentsMap"
Change it from:
"vmkernelInterfaceToSegmentsMap":{
"vmk4":"ls-aea17f68-3079-356f-a401-3efe6c8f2fe4-bb38936b0d73",
"vmk3":"ls-b310557d-d81d-323b-a473-e8854d8f3294-bb38936b0d73",
"vmk2":"ls-99bd09d7-14b8-3823-9ac2-55745bf53ccc-bb38936b0d73",
"vmk0":"ls-87f5531d-d32a-319b-a156-6963cafce1cc-bb38936b0d73"
}
To:
"vmkernelInterfaceToSegmentsMap":{
}
- Check json validity.
cat spec.json | json_pp
- Update spec.json with following command.
- Retry workflow.