addTempAction call required before saveTopology in newer releases.

[mharista]

When doing add and delete containers in 2016.1.2.1 the new version requires a 'provisioning/addTempAction.do' call before the '/provisioning/saveTopology.do' call, but the current methods only do the saveTopology.do.

[devrobo]

Hi Matt, Do you mean 2016.2 i.e. Clearlake? I tested on 2016.1.2.1 and how are the system tests passing? They add and delete a container. John

…

On Wed, Jan 25, 2017 at 12:47 PM, mharista ***@***.***> wrote: When doing add and delete containers in 2016.1.2.1 the new version requires a 'provisioning/addTempAction.do' call before the '/provisioning/saveTopology.do' call, but the current methods only do the saveTopology.do. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#17>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHXD8nd1BOlQx-pmW6i07HdrjJPgC9rnks5rV7TvgaJpZM4Lt-lk> .

[mharista]

Hi John,

I should have been more specific with the issue I am seeing on 2016.1.2.1. The container does get created but it never shows up on the network provisioning page even with saving and refreshing. The calls to add and delete do work so the system tests will still work. The container is also included when I get a list of all the containers in the system using the rest calls, so it appears to just be a bug in the GUI. Cheyne suggested trying to addTempAction before the saveTopology to see if that fixes the issue because that is what is being done in the python api.