The other day I successfully demonstrated the power of Code Stream at the UK North-West VMUG. The Management Pack for IT DevOps (codenamed “Houdini”) migrated blueprints between Development and Production, and at the end of the session I built a pipeline for deploying a WordPress application in development. Even though the audience wouldn’t have

time to see the pipeline complete I activated it and finished for the day. The next day I noticed it failed, with a nasty error:

“The following component requests failed: PHP_Service_1. Marking as ABORTED. A preceding component request has failed. PHP_Service_1. Marking as ABORTED. A preceding component request has failed. wp-loadbalancer. [Error code: 15012 ] – [Error Msg: Invalid IP Address input 172.17.50.12,172.17.50.11,172.17.50.10, for field addressGroups.addressGroups[0].secondaryAddresses.] WordPress_Database_1. Marking as ABORTED. A preceding component request has failed. WordPress_Services_1. Marking as ABORTED. A preceding component request has failed. WordPress_Services_1. Marking as ABORTED. A preceding component request has failed.”

Deployment of the blueprint had failed, along with subsequent pipeline tasks. On further investigation, it appeared the NSX Edge load-balancer had an issue applying IP addresses for each network interface.

TL;DR

The solution is to edit the JSON in the advanced properties of the pipeline and insert a value of null.

In Code Stream, edit your pipeline and click Stages >:

Select the deploy blueprint task and click Configure:

Under vRA Properties, click Advanced:

Scroll down and look for vip_address. In the above screenshot you can see the default is a pair of double quotation marks. Replace this with null:

Finally, save and activate the pipeline. It should now execute and deploy the blueprint successfully.

Thanks

I’d like to thank my colleague at VMware Vaidotas Ignatavicius for helping me with this one.