OneFlow/OneKE VM templates are incorrectly merged during "export" operation in vCenter
Description When you "export" the "Service OneKE 1.24 EE" (or "CE") marketplace app in vCenter, the "master" and "storage" VM templates are incorrectly merged. Basically all the important VM template content that should be in the "exported" template
{
"CONTEXT": {
"GROW_FS": "/",
"NETWORK": "YES",
"REPORT_READY": "YES",
"TOKEN": "YES",
"ONEAPP_VROUTER_ETH0_VIP0": "$ONEAPP_VROUTER_ETH0_VIP0",
"ONEAPP_VROUTER_ETH1_VIP0": "$ONEAPP_VROUTER_ETH1_VIP0",
"ONEAPP_VNF_HAPROXY_LB2_PORT": "$ONEAPP_VNF_HAPROXY_LB2_PORT",
"ONEAPP_VNF_HAPROXY_LB3_PORT": "$ONEAPP_VNF_HAPROXY_LB3_PORT",
"ONEAPP_K8S_EXTRA_SANS": "$ONEAPP_K8S_EXTRA_SANS",
"ONEAPP_K8S_LOADBALANCER_CONFIG": "$ONEAPP_K8S_LOADBALANCER_CONFIG",
"ONEAPP_K8S_LOADBALANCER_RANGE": "$ONEAPP_K8S_LOADBALANCER_RANGE",
"SSH_PUBLIC_KEY": "$USER[SSH_PUBLIC_KEY]"
},
"CPU": "2",
"VCPU": "2",
"GRAPHICS": {
"LISTEN": "0.0.0.0",
"TYPE": "vnc"
},
"INPUTS_ORDER": "",
"MEMORY": "3072",
"OS": {
"ARCH": "x86_64"
},
"USER_INPUTS": {}
}
is completely gone, instead we get something like this:
{
"DISK": {
"IMAGE_ID": "8"
},
"HOT_RESIZE": {
"CPU_HOT_ADD_ENABLED": "NO",
"MEMORY_HOT_ADD_ENABLED": "NO"
},
"HYPERVISOR": "vcenter",
"VCENTER_CCR_REF": "domain-c5012",
"VCENTER_INSTANCE_ID": "9f82ad22-7beb-404e-9595-bf73e9c672bc",
"VCENTER_TEMPLATE_REF": "vm-7003",
"VCENTER_VM_FOLDER": ""
}
which of course cannot really be used to deploy a cluster (please notice, there's no CPU or MEMORY setting for example, it will not deploy any VMs at all).
To Reproduce
You need a vCenter OpenNebula environment (this issue seems to be non-existent in KVM OpenNebula), then either use cli onemarketapp export "Service OneKE 1.24 EE" "Service OneKE 1.24 EE" -d <IMAGE_DS> or use the Storage->Apps->Service OneKE 1.24 EE->Import into Datastore button in Sunstone.
Expected behavior All VM templates related to any OneFlow service should be correctly merged with sources provided by the Marketplace.
Details
- Affected Component: OneFlow
- Hypervisor: vCenter
- Version: 6.4+
Additional context NA
Progress Status
- [ ] Code committed
- [ ] Testing - QA
- [ ] Documentation (Release notes - resolved issues, compatibility, known issues)