{% raw %}

Problem Description:

The Custom Naming machineRequested workflow runs for a long time and eventually fails with this error:


This assumes 


If using the default BT Diamond SSL certificate, your vRO server may not accept the certificate, resulting in failed connections from vRO to the BT Diamond API.



When the vRO workflow DNS MachineBuilding attempts to add a DNS record, the workflow fails, and the log contains something like this:

item: ‘DNS machineBuilding/item13’, state: ‘failed’, business state: ‘null’, exception: ‘Unable to add DNS entry to bluecat8 : InternalError: 500 : Internal Server Error

BlueCat’s API throws the 500 Internal Server error for multiple errors.

Possible causes:

1.  Bad credentials – check the credentials in the Item in vRA for your BlueCat Endpoint.

2.  Quick Deploys allowance exceeded

If the number of Quick Deploys BlueCat can execute is exceeded, it can cause this error.  To check if this is the problem,

Go to DNS, and click Actions, and choose Quick Deploy.

If this action displays an error that says the number of Quick Deploys has exceeded the allowed number, force a full deploy, and then try again.

To force a full deploy, go to Servers -> click on the correct bluecat server.

Select Deploy from the Action menu and check the  “Force DNS Full Deployment” checkbox” and hit the
“Yes” button.

{% raw %}

Here we have a property definition called My.RequestForm.Prop, and the possible values for it are A, B and C.  We want to set a group of 5 other properties based on that selection as follows:


In the world of Linux and server management, SSH (Secure Shell) is a critical tool for secure communication between machines. SSH keys provides a more secure alternative compared to password-based logins. In this guide, we will walk you through the process of setting up and using an SSH private key for logging into a Linux server.

What You Need to SSH with Private Key 

Step 1: Generating Your SSH Key Pair

The first step is to create a pair of SSH keys on your local machine. This pair consists of a public key and a private key.

  1. Open a terminal on your local machine.
  2. Type the command `ssh-keygen -t rsa -b 4096` to generate a new SSH key pair.
  3. When prompted, enter a file in which to save the key. Press Enter to accept the default location.
  4. Enter a secure passphrase when prompted; this adds an extra layer of security.

Step 2: Copying Your Public Key to the Server

Once your SSH key pair is generated, you need to place the public key on the server.

  1. Use the command `ssh-copy-id user@your_server_ip` to copy the public key. Replace `user` with your username and `your_server_ip` with your server’s IP address.
  2. Enter your password when prompted.

Step 3: Logging in Using Your SSH Key

Now that your public key is on the server, you can log in using your SSH key.

  1. To connect to the server, use the command `ssh user@your_server_ip`.
  2. If you set a passphrase for your private key, enter it when prompted.


If you encounter issues, check the following:


Using SSH keys for logging into your Linux server is a more secure and convenient method than using traditional passwords. Once set up, it simplifies your workflow and enhances your system’s security.

Remember, always keep your private key secure and never share it with anyone.


On Wednesday, May 22, SovLabs teamed up with Red Hat Ansible to offer a deep dive technical webinar, “Best Practices for Integrating vRealize Automation and Ansible Tower.” You can watch webinar in its entirety on the Red Hat Ansible website here and read our summary of the webinar here. Below is a summary of the brief Q&A session at the end of the webinar.



With over 20 years of experience and hundreds of thousands of mortgages issued, this leading mortgage originator attributes their success in this highly competitive business to a relentless focus on a customer experience that makes getting a mortgage as simple as possible.


VMware has announced an arrival date for the next version of vRealize Automation, version 8. Alongside version 8, VMware is rolling out what used to be known as “Cloud Automation Systems” (aka CAS), but they’ve changed the name to vRealize Automation Cloud (vRAC for short). On 12/17/2019, VMware is ending general support for vRA 7.3/7.3.1, and we expect that VMware will continue this trend of ending support for subsequent versions of vRealize Automation on a regular schedule as they roll out more v8.x upgrades and updates.  Will you upgrade from v7.x to v8.0? Before you do, we’d like to bring a few things up for consideration.