RH294 - ch09s02

Bookmark this page

Guided Exercise: Managing Software and Subscriptions

In this exercise, you configure a new Yum repository and install packages from it on your managed hosts.

Outcomes

Configure a Yum repository using the ansible.builtin.yum_repository module.
Manage RPM GPG keys using the ansible.builtin.rpm_key module.
Obtain information about the installed packages on a host using the ansible.builtin.package_facts module.

As the student user on the workstation machine, use the lab command to prepare your system for this exercise.

This command prepares your environment and ensures that all required resources are available.

[student@workstation ~]$ lab start system-software

Procedure 9.1. Instructions

Your organization requires that the simple-agent RPM package be installed on all hosts. This package is provided by an internal Yum repository maintained by your organization to host its internally developed software packages.

You need to write a playbook to ensure that the simple-agent package is installed on all managed hosts. The playbook must also ensure that all managed hosts are configured to use the internal Yum repository.

The repository is located at http://materials.example.com/yum/repository. All RPM packages in the repository are signed with a GPG key pair. The GPG public key for the repository packages is available at http://materials.example.com/yum/repository/RPM-GPG-KEY-example.

Change to the /home/student/system-software directory.

[student@workstation ~]$ cd ~/system-software
[student@workstation system-software]$

Begin writing the repo_playbook.yml playbook. Define a single play in the playbook that targets all hosts. Add a vars clause to the play that defines a single variable, custom_pkg, with the value simple-agent (the name of the RPM package that needs to be installed everywhere.) Add an empty tasks clause to the play.
The playbook should consist of the following content:
```
---
- name: Repository Configuration
  hosts: all
  vars:
    custom_pkg: simple-agent
  tasks:
```
Add two tasks to the tasks clause of the play in the repo_playbook.yml file.
Use the ansible.builtin.package_facts module in the first task to gather information about installed packages on the managed hosts. This task populates the ansible_facts.packages fact.
Use the ansible.builtin.debug module in the second task to print the installed version of the package referenced by the custom_pkg variable. Only run this task if the custom package is found in the ansible_facts.packages fact.
Run the repo_playbook.yml playbook.
1. Add the first task to the play. Set the value of the manager keyword to auto for the ansible.builtin.package_facts module.
  The first task should consist of the following content:
```
    - name: Gather Package Facts
      ansible.builtin.package_facts:
        manager: auto
```
2. Add a second task to the play that uses the ansible.builtin.debug module to display the value of the ansible_facts.packages[custom_pkg] variable. Add a when clause to the task to verify that the value of the custom_pkg variable is contained in the ansible_facts['packages'] variable.
  The second task should consist of the following content:
```
    - name: Show Package Facts for the custom package
      ansible.builtin.debug:
        var: ansible_facts['packages'][custom_pkg]
      when: custom_pkg in ansible_facts['packages']
```
3. Run the playbook:
```
[student@workstation system-software]$ ansible-navigator run \
> -m stdout repo_playbook.yml

PLAY [Repository Configuration] **********************************************

TASK [Gathering Facts] *******************************************************
ok: [servera.lab.example.com]

TASK [Gather Package Facts] **************************************************
ok: [servera.lab.example.com]

TASK [Show Package Facts for the custom package] *****************************
skipping: [servera.lab.example.com]

PLAY RECAP *******************************************************************
servera.lab.example.com    : ok=2    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0
```
  The Show Package Facts for the custom package task is skipped because the simple-agent package is not installed on the managed hosts.
Add a third task to the play that uses the ansible.builtin.yum_repository module to ensure the internal Yum repository is configured on the managed hosts. This task has the following requirements:
- The repository configuration is stored in the file /etc/yum.repos.d/example.repo
- The repository ID is example-internal
- The repository base URL is http://materials.example.com/yum/repository
- The repository is configured to check RPM GPG signatures
- The repository description is Example Inc. Internal YUM repo
The third task should consist of the following content:
```
    - name: Ensure Example Repo exists
      ansible.builtin.yum_repository:
        name: example-internal
        description: Example Inc. Internal YUM repo
        file: example
        baseurl: http://materials.example.com/yum/repository/
        gpgcheck: yes
```
Add a fourth task to the play that uses the ansible.builtin.rpm_key module to ensure that the repository's public key is present on the managed hosts. The repository's public key is available at http://materials.example.com/yum/repository/RPM-GPG-KEY-example.
The fourth task should consist of the following content:
```
    - name: Ensure Repo RPM Key is Installed
      ansible.builtin.rpm_key:
        key: http://materials.example.com/yum/repository/RPM-GPG-KEY-example
        state: present
```
Add a fifth task to the play that ensures that the package referenced by the custom_pkg variable is installed on the managed hosts.
The fifth task should consist of the following content:
```
    - name: Install Example package
      ansible.builtin.dnf:
        name: "{{ custom_pkg }}"
        state: present
```

The ansible_facts['packages'] fact is not automatically updated when a new package is installed on a managed host. This step demonstrates that this is true.

Copy the second task and add it as the sixth task in the play. Run the playbook and verify that the ansible_facts['packages'] fact does not contain information about the simple-agent package installed on the managed hosts.

The sixth task contains a copy of the second task:

    - name: Show Package Facts for the custom package
      ansible.builtin.debug:
        var: ansible_facts['packages'][custom_pkg]
      when: custom_pkg in ansible_facts['packages']

The entire repo_playbook.yml playbook should now consist of the following content:

---
- name: Repository Configuration
  hosts: all
  vars:
    custom_pkg: simple-agent
  tasks:
    - name: Gather Package Facts
      ansible.builtin.package_facts:
        manager: auto

    - name: Show Package Facts for the custom package
      ansible.builtin.debug:
        var: ansible_facts['packages'][custom_pkg]
      when: custom_pkg in ansible_facts['packages']

    - name: Ensure Example Repo exists
      ansible.builtin.yum_repository:
        name: example-internal
        description: Example Inc. Internal YUM repo
        file: example
        baseurl: http://materials.example.com/yum/repository/
        gpgcheck: yes

    - name: Ensure Repo RPM Key is Installed
      ansible.builtin.rpm_key:
        key: http://materials.example.com/yum/repository/RPM-GPG-KEY-example
        state: present

    - name: Install Example package
      ansible.builtin.dnf:
        name: "{{ custom_pkg }}"
        state: present

    - name: Show Package Facts for the custom package
      ansible.builtin.debug:
        var: ansible_facts['packages'][custom_pkg]
      when: custom_pkg in ansible_facts['packages']

Run the playbook.

[student@workstation system-software]$ ansible-navigator run \
> -m stdout repo_playbook.yml

PLAY [Repository Configuration] **********************************************

TASK [Gathering Facts] *******************************************************
ok: [servera.lab.example.com]

TASK [Gather Package Facts] **************************************************
ok: [servera.lab.example.com]

TASK [Show Package Facts for the custom package] *****************************
skipping: [servera.lab.example.com]

TASK [Ensure Example Repo exists] ********************************************
changed: [servera.lab.example.com]

TASK [Ensure Repo RPM Key is Installed] **************************************
changed: [servera.lab.example.com]

TASK [Install Example package] ******************************************
changed: [servera.lab.example.com]

TASK [Show Package Facts for the custom package] *****************************
skipping: [servera.lab.example.com]

PLAY RECAP *******************************************************************
servera.lab.example.com    : ok=5    changed=3    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0

	The `Gather Package Facts` task determines the data contained in the `ansible_facts['packages']` fact.
	The task is skipped because the `simple-agent` package is installed after the `Gather Package Facts` task.

Update the package facts in your play by inserting a task immediately after the Install Example package task. Write the new task so that it runs the ansible.builtin.package_facts module. Set the module's manager attribute to auto.

The complete playbook should consist of the following content:

---
- name: Repository Configuration
  hosts: all
  vars:
    custom_pkg: simple-agent
  tasks:
    - name: Gather Package Facts
      ansible.builtin.package_facts:
        manager: auto

    - name: Show Package Facts for the custom package
      ansible.builtin.debug:
        var: ansible_facts['packages'][custom_pkg]
      when: custom_pkg in ansible_facts['packages']

    - name: Ensure Example Repo exists
      ansible.builtin.yum_repository:
        name: example-internal
        description: Example Inc. Internal YUM repo
        file: example
        baseurl: http://materials.example.com/yum/repository/
        gpgcheck: yes

    - name: Ensure Repo RPM Key is Installed
      ansible.builtin.rpm_key:
        key: http://materials.example.com/yum/repository/RPM-GPG-KEY-example
        state: present

    - name: Install Example package
      ansible.builtin.dnf:
        name: "{{ custom_pkg }}"
        state: present

    - name: Gather Package Facts
      ansible.builtin.package_facts:
        manager: auto

    - name: Show Package Facts for the custom package
      ansible.builtin.debug:
        var: ansible_facts['packages'][custom_pkg]
      when: custom_pkg in ansible_facts['packages']

Use an Ansible ad hoc command to remove the simple-agent package installed during the previous execution of the playbook. Run the playbook with the inserted ansible.builtin.package_facts task and use the output to verify the installation of the simple-agent package.

To remove the simple-agent package from all hosts, use the ansible all command with the -m ansible.builtin.dnf and -a 'name=simple-agent state=absent' options.

[student@workstation system-software]$ ansible all -m ansible.builtin.dnf \
> -a 'name=simple-agent state=absent'
servera.lab.example.com | CHANGED => {
...output omitted...
    "changed": true,
    "msg": "",
    "rc": 0,
    "results": [
        "Removed: simple-agent-1.0-1.el9.x86_64"
    ]
...output omitted...

Run the repo_playbook.yml playbook.

[student@workstation system-software]$ ansible-navigator run \
> -m stdout repo_playbook.yml

PLAY [Repository Configuration] **********************************************

TASK [Gathering Facts] *******************************************************
ok: [servera.lab.example.com]

TASK [Gather Package Facts] **************************************************
ok: [servera.lab.example.com]

TASK [Show Package Facts for the custom package] *****************************
skipping: [servera.lab.example.com]

...output omitted...

TASK [Install Example package] ***********************************************
changed: [servera.lab.example.com]

TASK [Gather Package Facts] **************************************************
ok: [servera.lab.example.com]

TASK [Show Package Facts for the custom package] *****************************
ok: [servera.lab.example.com] => {
    "ansible_facts['packages'][custom_pkg]": [
        {
            "arch": "x86_64",
            "epoch": null,
            "name": "simple-agent",
            "release": "1.el9",
            "source": "rpm",
            "version": "1.0"
        }
    ]
}

PLAY RECAP *******************************************************************
servera.lab.example.com    : ok=7    changed=1    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0

	No package fact exists for the `simple-agent` package because the package is not installed on the managed hosts.
	The `simple-agent` package is installed as a result of this task, as indicated by the `changed` status.
	This task updates the package facts with information about the `simple-agent` package.
	The `simple-agent` package fact exists and indicates only one `simple-agent` package is installed. The installed package is version `1.0`.

Finish

On the workstation machine, change to the student user home directory and use the lab command to complete this exercise. This step is important to ensure that resources from previous exercises do not impact upcoming exercises.

[student@workstation ~]$ lab finish system-software

This concludes the section.

Discuss Red Hat Enterprise Linux Automation with Ansible

Go to community

Red Hat Linux Automation with Ansible (RH294)

Haley_Ruccio

24 lip 2023

Learn how to automate Linux system administration tasks with Red Hat Ansible Automation PlatformRed Hat Enterprise Linux Automation with Ansible (RH294) is designed for Linux administrators and developers who need to automate repeatable and error-prone steps for system provisioning, configuration, application deployment, and orchestration. This course is based on Red Hat® Enterprise Linux® 9 and Red Hat Ansible Automation Platform 2.2.Course content summaryInstall Red Hat Ansible Automation Platform on control nodes.Create and update inventories of managed hosts and manage connections to them.Automate administration tasks with Ansible Playbooks and ad hoc commands.Write effective playbooks at scale.Protect sensitive data used by Ansible Automation Platform with Ansible Vault.Reuse code and simplify playbook development with Ansible Roles and Ansible Content Collections.Audience for this courseThis course is geared toward Linux system administrators, DevOps engineers, infrastructure automation engineers, and systems design engineers who are responsible for these tasks:Automating configuration managementEnsuring consistent and repeatable application deploymentProvisioning and deployment of development, testing, and production serversIntegrating with DevOps continuous integration/continuous delivery workflowsPrerequisites for this coursePass the Red Hat Certified System Administrator (RHCSA) exam (EX200), or demonstrate equivalent Red Hat Enterprise Linux knowledge and experience.Take our free assessment to gauge whether this offering is the best fit for your skills.

980

curl finds no route to host?

TPeters

23 lip 2023

I am doing the self-paced course RH294 . With two exercises (Ch.3 final Lab and Ch.4 lab exercise 2) I ran into this problem:after installing and starting a web service, from the classroom web termicaI I cannot reach servera.lab.example.com with curl: "No route to host". This despite the fact that I can ping it, open a shell to it, and install the package on it with Ansible.Anyone else have the same problem?What might be the cause?

1702

Welcome to the Red Hat Linux Automation with Ansible (RH294) group in the Red Hat Learning Community

cschunke

18 lip 2023

We are excited to launch a space dedicated to the Red Hat Training course Red Hat Linux Automation with Ansible! To gain the most value from this group - click the "Join Group" button in the upper right hand corner.We encourage group members to collaborate in this group to discuss topics, ask questions, share best practices and tips, provide course feedback, and share their accomplishments as it relates to RH294.Read more about Red Hat Linux Automation with Ansible here.

351

Revision: rh294-9.0-c95c7de