Migrated 6.2 to 7.2 and vRO stub workflows don't work

[DLally]

Is there anything I'm missing that would cause my stub workflows not to work?  My endpoints are all configured.  I can browse my vRo server in XaaS and I can even call an event broker workflow.  The Event broker workflow failed since I don't have any workflows setup to use the new payloads yet.

Logs show this error:

Workflow Complete:  1017187 - Failed: Error executing vRealize Orchestrator workflow: TypeError: Cannot read property "hostId" from null (Workflow:Prepare Workflow run / Get host (item4)#1).

I'm not even seeing it hit my orchestrator server, there is no failure of the workflow.

[bdamian · Accepted solution]

I strongly recommend you to migrate your stub workflows to Event-Broker subscriptions.

If you migrate from 6.2 to 7.2 then probably you need to execute the "Install vCO customization" workflow, but I don't recommend this. Event-Broker is a great new feature.

[DLally]

I'm definitely not against using the event broker, however that will be a decent amount of work.  I have a different thread on here on how to even use the new event broker and payloads, so i'm not even ready for that yet.

I would like to get working with everything using the old workflow stubs and then work on modifying my current workflows to use the new payload system.

Is there anything negative that could impact me if i install the VCO customization? Or are you just saying that because you'd recommend to use the new event broker?

[bdamian]

I'm also responding to you in the other thread.

I haven't tested it myself, but there is also an "uninstall vco customization" Workflow so you can "undo" this if anything happens. Anyway, when you know how to use it, is very easy to implement the new (and great) Event-Broker.

[DLally]

Yes, thanks for your help!

i didn't even think about the uninstall portion ... thanks, i'll give that a shot