Sunstone - Updating Service Template breaks the logic of the Service.

[alpeon]

Description
If you update the Service Template with some alterings (such as changing the template of a Role and cardinality) - the Service can't properly be instantiated and keeps itself in the DEPLOYING state. As I was looking into - there are parts of the template that are getting truncated and the VM comes with truncated context.

Tested with OneKE.

To Reproduce

1. Download OneKE 1.31 from the marketplace.
2. Duplicate the master template as worker template.
3. Navigate to the Service Template and using Update map the cloned VM Template to the worker Role.
4. Set the cardinality of storage role to 1.
5. Instantiate the Service.

To reproduce 1:1, make sure to map Public network to a network with the internet access and Private to a non-routed host-only or evpn type of a network.

From enabled OneKE features - enabled Longhorn and Traefik with their default config, rest is kept as is, no alterations.

Expected behavior
OneKE should work and service state must be in the RUNNING.

Details

• Affected Component: Sunstone
• Hypervisor: KVM
• Version: 7.0

Additional context
In the attachment there are two service templates to compare, one is altered and one is original. The 9.txt is the config of master VM of the successful deployment and 12.txt is from the faulty one.

9.txt
12.txt
original.txt
updated.txt

Progress Status

• Code committed
• Testing - QA
• Documentation (Release notes - resolved issues, compatibility, known issues)