RH294 - ch09s02

Bookmark this page

Guided Exercise: Managing Software and Subscriptions

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

Outcomes

You should be able to:

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

On workstation, run the lab start script to confirm that the environment is ready for the lab to begin. The script creates the working directory, called system-software, and populates it with an Ansible configuration file, a host inventory, and lab files.

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

Procedure 9.1. Instructions

Your organization requires that all hosts have the example-motd package installed. This package is provided by an internal Yum repository maintained by your organization to host internally developed software packages.

You are tasked with writing a playbook to ensure that the example-motd package is installed on the remote host. The playbook must ensure the configuration of the internal Yum repository.

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

As the student user on workstation, change to the /home/student/system-software working 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 that defines a single variable custom_pkg with a value of example-motd. Add the tasks clause to to the playbook.
The playbook now contains:
```
---
- name: Repository Configuration
  hosts: all
  vars:
    custom_pkg: example-motd
  tasks:
```
Add two tasks to the playbook.
Use the package_facts module in the first task to gather information about installed packages on the remote host. This task populates the ansible_facts.packages fact.
Use the debug module in the second task to print the installed version of the package referenced by the custom_pkg variable. Only execute this task if the custom package is found in the ansible_facts.packages fact.
Execute the repo_playbook.yml playbook.
1. Add the first task to the playbook. Configure the manager keyword of the package_facts module with a value of auto. The first task contains the following:
```
    - name: Gather Package Facts
      package_facts:
        manager: auto
```
2. Add a second task to the playbook that uses the debug module to display the value of the ansible_facts.packages[custom_pkg] variable. Add a when clause to the task to check if the value of the custom_pkg variable is contained in the ansible_facts.packages variable. The second task contains the following:
```
    - name: Show Package Facts for the custom package
      debug:
        var: ansible_facts.packages[custom_pkg]
      when: custom_pkg in ansible_facts.packages
```
3. Execute the playbook:
```
[student@workstation system-software]$ ansible-playbook 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=1    rescued=0    ignored=0
```
  The debug task is skipped because the example-motd package is not installed on the remote host.
Add a third task that uses the yum_repository module to ensure the configuration of the internal yum repository on the remote host. Ensure that:
- The repository's configuration is stored in the file /etc/yum.repos.d/example.repo
- The repository ID is example-internal
- The 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 contains the following:
```
    - name: Ensure Example Repo exists
      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 rpm_key module to ensure that the repository public key is present on the remote host. The repository public key URL is http://materials.example.com/yum/repository/RPM-GPG-KEY-example.
The fourth task appears as follows:
```
    - name: Ensure Repo RPM Key is Installed
      rpm_key:
        key: http://materials.example.com/yum/repository/RPM-GPG-KEY-example
        state: present
```
Add a fifth task to ensure that the package referenced by the custom_pkg variable is installed on the remote host.
The fifth task appears as follows:
```
    - name: Install Example motd package
      yum:
        name: "{{ custom_pkg }}"
        state: present
```

The ansible_facts.packages fact is not updated when a new package is installed on a remote host.

Copy the second task and add it as the sixth task in the play. Execute the playbook and verify that the ansible_facts.packages fact does not contain information about the example-motd installed on the remote host.

The sixth task contains a copy of the second task:

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

The entire playbook now looks as follows:

---
- name: Repository Configuration
  hosts: all
  vars:
    custom_pkg: example-motd
  tasks:
    - name: Gather Package Facts
      package_facts:
        manager: auto

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

    - name: Ensure Example Repo exists
      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
      rpm_key:
        key: http://materials.example.com/yum/repository/RPM-GPG-KEY-example
        state: present

    - name: Install Example motd package
      yum:
        name: "{{ custom_pkg }}"
        state: present

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

Execute the playbook.

[student@workstation system-software]$ ansible-playbook 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 motd 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=2    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 example-motd package is installed after the `Gather Package Facts` task.

Insert a task immediately after the Install Example motd package task using the package_facts module to update the package facts. Set the module's manager keyword with a value of auto.

The complete playbook is shown below:

---
- name: Repository Configuration
  hosts: all
  vars:
    custom_pkg: example-motd
  tasks:
    - name: Gather Package Facts
      package_facts:
        manager: auto

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

    - name: Ensure Example Repo exists
      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
      rpm_key:
        key: http://materials.example.com/yum/repository/RPM-GPG-KEY-example
        state: present

    - name: Install Example motd package
      yum:
        name: "{{ custom_pkg }}"
        state: present

    - name: Gather Package Facts
      package_facts:
        manager: auto

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

Use an Ansible ad hoc command to remove the example-motd package installed during the previous execution of the playbook. Execute the playbook with the inserted package_facts task and use the output to verify that the installation of the example-motd package.

To remove the example-motd package from all hosts, use the ansible all command with the -m yum and -a 'name=example-motd state=absent' options.

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

Execute the playbook.

[student@workstation system-software]$ ansible-playbook 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 motd package] ******************************************
changed: [servera.lab.example.com]

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

TASK [Show Package Facts for example-motd] ***********************************
ok: [servera.lab.example.com] => {
    "ansible_facts.packages[custom_pkg]": [
        {
            "arch": "x86_64",
            "epoch": null,
            "name": "example-motd",
            "release": "1.el7",
            "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 example-motd package because the package is not installed on the remote host.
	The example-motd 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 example-motd package.
	The example-motd package fact exists and indicates only one example-motd package is installed. The installed package is at version `1.0`.

Finish

On workstation, run the lab system-software finish script to clean up the resources created in this exercise.

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

This concludes the guided exercise.

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-8.4-9cb53f0