Wednesday Tidbit: Fix missing Puppet attributes on vRealize Automation blueprints

Occasionally you come across an issue which bugs the hell out of you. Despite wanting needing to resolve it badly, you know it’s going to be a case of trial and error, and it’s going to consume a lot of your time. The other day I came across one these issues, and just as I suspected, the majority of an evening would be spent trying to resolve it.

At both my current customer and here in HobbitCloud we use Puppet for our configuration management needs. Both platforms offer unmanaged and managed workloads, the latter employing Puppet Enterprise to reduce configuration drift.

With the introduction of vRealize Automation 7.3, Puppet has become a first class citizen, enabling configuration management attributes to be dragged onto the blueprint canvass. After the initial configuration, it’s as simple as selecting your Puppet Master, environment and role.

Or so I thought…

Once I had my environment setup exactly how I wanted it, I came to add Puppet to a newly built blueprint only to find the Puppet Master drop-down box wouldn’t populate:

Hmmm… something’s not right there

The vRO plugin had been installed, and the endpoint created correctly. However no matter what I tried nothing worked.

When I looked into the issue, there were plenty of fellow vExperts/bloggers who had managed to configure the Puppet endpoint without issue – so something was clearly different with my environment.

Finally it occurred to me that when configuring lab environments, a lot of people grant their accounts “God like” permissions – something I avoid like the plague in my environment. Convinced this was a permissions issue, I set about adding various roles. Finally I figured out that my architect group required the Tenant Administrator role:

The missing link

Once this role was applied and I had logged off/back on again, I was able to select the appropriate Puppet Master, environment and role:

Voila!

TL;DR: make sure your account in vRA has the Tenant Administrator role when designing blueprints which use Puppet.

If you’re interested in running Puppet Enterprise in your lab environment, don’t forget it comes with a free 10-agent licence. This is a great way to get to grips with the fully-functioning version of the product without spending thousands.

One thought on “Wednesday Tidbit: Fix missing Puppet attributes on vRealize Automation blueprints

  1. Pingback: Newsletter: September 30, 2017 | Notes from MWhite

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s