ReleaseOps - Update set promotion issues - Unable to send messages to start the operation remotely.

[NowMaestro]

Hello,

We are exploring the use of ReleaseOps application to manage our release.

We have configured the instance (3-instance config).

Has anyone run into this issue when processing the deployment request.

Error Message: Unable to send messages to start the operation remotely.

The deployment assessment playbook cannot run successfully because there appears to be some thing that prevents update set retrieval and deployment from dev to test instance.

[Anand__99]

@Uncle Rob , Could you please help?

[Uncle Rob]

Hey @NowMaestro - Product Manager for ReleaseOps here.  If you can send me an email at robert.fedoruk@servicenow.com I'm happy to find some time to look into this with you.

[Harm van Genese]

Hello @Uncle Rob, when i was searching for a solution for exactly the same error message i saw this post. If you find a solution can you post it?  

[Daniel Draes]

This sounds like a trust issue between the instances. 

I would start on the dev instances and compare the table ’Trusted Instances’ (sn_mif_instance_trusted_by_me).

It should look something like this:

 

If that is in place, look at your controller, same table. You should see all non-prod instances listed.

Next step would be the ReleaseOps Backend Tracker (sn_releaseopsbe_operation_tracker), maybe you can find more details there.

Worst case, create a support case. The root cause is most likely some changes on the Multi Instance Framework which is powering ReleaseOps.