I am having trouble with assigned attributes which are lost during an update of the service template.
I encountered this problem when assigend public addresses of compute node templates have been lost.
Greetings
Miles
Steps
Here is a minimal service template that should be deployed.
However, if we update the service template with service-template.v2.yaml, then the assigned attribute ist lost even tho node_first should not be "touched" since its state is started.
Interestingly, when we add the node template node_second directly to the currently deployed service template service-template.yaml and resume the deployment, then the attribute assignment is obtained.
$ opera deploy --resume --force
[Worker_0] Deploying node_second_0
[Worker_0] Executing create on node_second_0
[Worker_0] Deployment of node_second_0 complete
Expected Behaviour
I expect that assigned attributes of node templates, which are already deployed and are not touched during the update, are still assigned after the service template has been successfully updated.
Description
Hey,
I am having trouble with assigned attributes which are lost during an update of the service template. I encountered this problem when assigend public addresses of compute node templates have been lost.
Greetings Miles
Steps
Here is a minimal service template that should be deployed.
The deployment works as expected.
And we can see in
.opera/instances/node_first_0
that the attributesome_attribute
of the node templatenode_first
has the valuesome_value
.However, if we update the service template with
service-template.v2.yaml
, then the assigned attribute ist lost even thonode_first
should not be "touched" since its state isstarted
.The update command.
The new content of
.opera/instances/node_first_0
which has no value assigned tosome_attribute
.The attribute has been assigned at
node_second
as exepcted.Interestingly, when we add the node template
node_second
directly to the currently deployed service templateservice-template.yaml
and resume the deployment, then the attribute assignment is obtained.Expected Behaviour
I expect that assigned attributes of node templates, which are already deployed and are not touched during the update, are still assigned after the service template has been successfully updated.