Day 87: A Redirected Module and a Renamed Publisher
Day 87 of DevOps, Day 37 of Azure. Both tasks today turned on a name that is not the name the system uses. An Ansible task that says yum runs the dnf module, because the first is now a redirect to the second. And an Azure image "published by Jetware" is published by jetware-srl , which no amount of guessing gets you to. One Ansible task, one Azure task. Install and start a service on three…
On Day 87 of DevOps, the focus was on two tasks: modifying a module and renaming a publisher. The first task involved using an Ansible task to install and start the vsftpd service on three servers. The task utilized the yum module, which was a redirect to the dnf module. This was important as the servers were running CentOS Stream 9, where dnf was the default package manager.
The second task required publishing a Percona MySQL image on Azure and accessing it via a PHP page. The image was published by Jetware, but the system displayed it as jetware-srl. This discrepancy arose from the inconsistent capitalization and spelling of the publisher name in the marketplace. The task involved searching for the publisher using a fragment of the name rather than guessing the full name, which led to finding the correct publisher, jetware-srl.
The tasks were performed using the KodeKloud Engineer platform and followed the instructions provided in the playbook. The main takeaway from the day was the importance of understanding the underlying system and the potential issues that can arise from assuming names or permissions, as well as the need to verify and accept legal terms before deploying marketplace images.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.