Member-only story

Ansible troubleshooting — Error 106: Role Name Rules

How to solve the Ansible Error 106: Role Name Rules

Luca Berton
4 min readOct 31, 2023

Introduction

Ansible, a popular automation tool, simplifies the orchestration and management of infrastructure, configurations, and applications. It employs a modular structure, including roles, to organize and reuse automation tasks. However, to ensure consistency and prevent errors in your Ansible playbooks, it’s crucial to follow best practices and guidelines. In this article, we’ll explore Ansible Error 106, “role-name,” which enforces specific rules for naming roles. We’ll dive into why adhering to these naming conventions is important and how to create role names that comply with Ansible standards.

The Problem: Non-compliant Role Names

Ansible Error 106, “role-name,” focuses on enforcing a set of rules regarding role names. These rules are designed to ensure uniformity and clarity in role naming conventions. Non-compliant role names can create confusion, reduce maintainability, and lead to issues when working with Ansible playbooks. Here are the key requirements for role names:

  1. Lowercase Alphanumeric Characters: Role names should contain only lowercase alphanumeric characters, which are letters (a-z) and digits (0–9).

--

--

Luca Berton
Luca Berton

Written by Luca Berton

I help creative Automation DevOps, Cloud Engineer, System Administrator, and IT Professional to succeed with Ansible Technology to automate more things everyday

No responses yet