Can't create a vCloud Director notification subscription (Server.setCustomProperty routing key)

[GHUser911]

Hi,

I'm having an issue when using the vCloud Director notification subscription workflow,

When trying to add an AMQP Broker using the Workflow "Create a vCloud Director notification subscription" I'm getting the error messages: "Value cannot be holded by custom property".

The broker and listener are both created.

After doing some digging I see that the error is happening at the end of the workflow at the scriptable task "Set custom prop" when getting to:

if (routingKeyAtt != null) Server.setCustomProperty(subscription, "routingKey", routingKeyAtt);

Any idea why I can't set this specific CustomProperty?

any idea's who to work around this issue?

Thanks!

[mcfadyenj]

I had a similar issue and found that there are different versions of the notifications package.

make sure you are using the one for the appropriate version of vCD you are running. The various versions seem to handle the routing key slightly differently as well as a few other items.

there is a notifications package 5.1 and one without a version which i think is 5.0. not sure about a 5.5 one yet as I have not tried looking for it. The AMQP versions are important as well make sure you have the latest version of the AMQP plugin too. I found a few issues with that also (but the remediation code is in the activities) but commented out.

[GHUser911]

Hi,

I'm working with vCO 5.5 & vCD 5.5 and the latest version of RabbitMQ and Earlang.

I'v imported the com.vmware.coe.vcd51.notifications Package (didn't see a package for vCD 5.5),

I guess that It's some kind of a compatibility issue.

Any Ideas on how I can work around this issue? Maybe using other workflow to setup the listener?

Maybe I can manually set the listener to capture that specific routing key?

Thanks,

Nimrod

[maxiepax]

Hi,

I'm getting the same error, running vCD 5.5, vCO 5.5, vCloud VCO integration plugin 5.5.0, and Notification package 5.1.

Can't figure out whats going wrong but i've read some threads that a 5.5 beta package seems to be available?

[cdecanini_]

It seems there is an issue with Server.setCustomProperty with either vCO 5.5 or vCD 5.5. In the past I have got a similar issue that was because of the cutom property database record length that was too short. Unfortunately I have been working on other projects and did not have time to look into the notification package issues with vCO 5.5 and vCD 5.5. I would suggest to open a support request with a sample workflow just doing the Server.setCustomProperty with the parameter as a string so GSS can reproduce it and have engineering looking at it.

[igaydajiev]

Hi

not an expert in vCD but if you provide sample workflow demonstrating the issue with Server.setCustomProperty as described by  cdecanini_ will take a look.

[qc4vmware]

Looking at the release notes of the AMQP plugin I only see 5.1 listed as a supported vCO.  Can I install this plugin in 5.5?  Does the documentation just need to be updated?  It also does not show up in the list of plugins to download with vSphere 5.5 .  I'm just getting ready to setup a listener to some RabbitMQ services here but if this is not supported I'll need to figure something else out.

[igaydajiev]

there is scheduled updated for vCO  5.5.1 that  should be available at the end of this week.

It also includes updated version of AMQP plugin.

[Burke- · Accepted solution]

All - I have updated the Notifications package for 5.1 file found here: vCloud Director 5.1 blocking tasks and notification package using AMQP -- Please try this version, it should now allow successful creation of the subscription as well as adding the custom properties.

UPDATE March 11th, 2014: Updated "Create a vCloud Director Notification subscription" workflow to work with vCloud Director 5.5. The change IS backward compatible with vCloud Director 5.1.