Multipathd is not enabling

[Prady A]

Hi All..

I ve a very 2 very basic task of enabling multipath.

The 2 task is failing since the first one is not enabling. But in ansible job it is showing as changed but when I checked multipath service in system it is showing as Below: 

Active: inactive(dead)

Condition: start condition failed

                   |- ConditionPathExists=/etc/multipath.conf was not met 

Tasks

———-

- name: confirm multipathd is enabled 

        service: multipathd

        state: started

        enable: yes

- name: check default polling interval

         shell: multipathd list config | awk ‘/defaults {/,/}’|grep -w polling_interval

          register: polling_interval

          changed_when: false

Please suggest why ansible not able to enable multipath service correctly..

Regards 

[dulh...@mailbox.org]

hi,

 

the syntax of your TASK sems not to match the docs for the service module. Would something like ...

 

   - name: Enable service httpd, and not touch the state
     ansible.builtin.service:
       name: multipathd
       state: started
       enabled: true

... work?

[Prady A]

Thank you . Due to some old iso image the multipath is not able to enable . We have to update the iso image it seems

Thank you

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/1998953809.39642.1697605729025%40office.mailbox.org.

[Will McDonald]

This seems like a pretty glaring error:

 

ConditionPathExists=/etc/multipath.conf was not met

This is likely nothing to do with Ansible. You're installing a multipath package, enabling a service, the service is failing to start automatically because it doesn't have any valid config. You should see the same problem if you perform the same steps manually. Figure out your manual process first, then automate it.

Either:

1. Include a templated /etc/multipath.conf config before enabling/starting the systemd service

2. Run something like mpathconf --enable to create a default config

3. Override/replace the Condition in the systemd unit file (probably a bad idea).

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAEuB3Aq7dH0AB%3DMrPXBZ%3DtMbTT-uY4tfE6BMPpQEkiVMKUhXOg%40mail.gmail.com.

[Prady A]

Thank you so much for your kind reply. 

For temporary fix I copied the  /etc/multipath.conf from other machine but eventually we need to update our ISO image to include this file. 

Regards 

PD

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAKtKohQsrvv0O5eXWFyVWU%2B84T6SFukHoOQ8Fr4UMj50gokiCw%40mail.gmail.com.

[Will McDonald]

I'd recommend looking at having your role or playbook drop in a sensible, templated configuration personally.

Baking a static file into an ISO will almost certainly cause future pain unless you only ever deploy one hardware and storage combination with absolutely zero variation?

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAEuB3ApbBantMgeDiBS%3DB-UG989yRxmeZtWGZuHjjcf5tYDMxA%40mail.gmail.com.

[Prady A]

Thank you for your suggestion. These code are inside our Tower placed in git. 

Right now I ve no idea why they are baking a file to iso instead they could do using template. I need to dig more .. 

Thanks again for your help

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAKtKohQ9MpPWjYQSQ%3DdJGmVKBUsPz8%3DTR5pgZf2TstvB1_VNtg%40mail.gmail.com.