O2-flp-setup error

Dear all,
I’m trying to upgrade the FLP software using the flp-suite with:

o2-flp-setup deploy --head myhost --flps myhost

but it fails with the following error message:

Check if custom configuration exists in templates...
  myhost -> localhost failed | msg: MODULE FAILURE
See stdout/stderr for the exact error

Here is a fuller log:

Store inventory_head to consul...
  myhost done
Store inventory_flps to consul...
  myhost done
Add or update control default consul values...
  myhost done
  myhost done
  myhost done
Create consul o2 components...
  myhost done
  myhost done
  myhost done
Check if custom configuration exists...
  myhost skipped
Set file_details...
  myhost skipped
Check if custom configuration exists in templates...
  myhost -> localhost failed | msg: MODULE FAILURE
See stdout/stderr for the exact error
Reload systemd configs (via handler)... 
  myhost ok
Restart consul (via handler)... 
  myhost done
Restart infoLoggerServer (via handler)... 
  myhost done
Restart o2-ilg (via handler)... 
  myhost done
Restart Mesos master (via handler)... 
  myhost done
Restart AliECS core (via handler)... 
  myhost done
Restart o2-cog (via handler)... 
  myhost done
Reload daemon (via handler)... 
  myhost done
Cleanup meta/slaves/latest (via handler)... 
  myhost ok
Restart mesos-master (via handler)... 
  myhost done
Restart mesos-slave (via handler)... 
  myhost done

- Play recap -
  myhost          : ok=205  changed=77   unreachable=0    failed=1    rescued=0    ignored=0   

Any idea on what could be wrong (or where to find the stdout/stderr file?)
Thanks in advance,
best regards,
Diego

Dear @dstocco,

Can you provide us with the output of the following commands:

o2-flp-setup status
ansible --version

Also, is it possible to execute the o2-flp-setup command with the debug flag, like this:

o2-flp-setup deploy --head myhost --flps myhost --debug

It might provide more info on what is failing.

Kind Regards,
Miltiadis

Dear @malexis,
here is the command output:

2-flp-setup *** The ALICE O²/FLP Suite Setup Tool

version:                             0.6.0-7481916
system configuration revision:       flp-suite-v0.8.0-2b802d2  

ansible 2.9.3
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, Aug  7 2019, 00:51:29) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]

I relaunched in debug mode, here is the output:

TASK [control-consul : Check if custom configuration exists in templates] ******
fatal: [myhost -> localhost]: FAILED! => {
    "changed": false, 
    "rc": 127
}

MSG:

MODULE FAILURE
See stdout/stderr for the exact error


MODULE_STDERR:

/var/tmp/sclmm9jsu: line 8: -H: command not found

But I guess that the file is temporary because it does not exist…

By the way, when I launch the program I put the hostname in both --head and --flps.
Should I put localhost instead?

Thanks!
Cheers,
Diego

Dear @dstocco,

Thank you very much for providing the output.

The hostname is fine for installing. The task failing is looking for custom configuration files for Readout or QC in your local machine(the one you triggered the deployment), that’s why it prints [myhost -> localhost].

Is it possible to retry after upgrading the Ansible like this:

sudo yum remove ansible
sudo yum --disablerepo=* --enablerepo=epel -y install ansible

One more question is the user, the one trying the deployment, in the sudoers?

Kind Regards,
Miltiadis

Dear @dstocco,

To add in my previous post, what is the output of the following:

 which sudo

Kind Regards,
Miltiadis

Hi @malexis,
it is: /opt/rh/devtoolset-7/root/usr/bin/sudo

But notice that I’m launching the o2-flp-setup command as root, so I should not have permission issues.
Should I run it as flp instead?

Cheers,
Diego

Hi @dstocco,

No, the problem is with the sudo. You have enabled the devtoolset-7 and there is an issue with the sudo found there. You can verify it by executing

sudo -H -S -n -u root /bin/sh

It should produce the same error with ansible /var/tmp/sclKpdWFR: line 8: -H: command not found.

To fix that you can either disable devtoolset-7 or even better you can export
export PATH=/usr/bin:$PATH. It would be better if you add it to your bash profile( otherwise you need to export it every time you open a new shell session).

Let me know if this fixed the problem.

Kind Regards,
Miltiadis

I see…
Yes, you’re right: if I run sudo with -H option I get the same error.

I do load the devtoolset-7…but only as a user. The problem is that I became root with su instead of su -…and it turns out that it kept my user PATH (which had devtoolset7)
I connected directly as root and it seems to work fine.

Thanks a lot for your help!
Cheers,
Diego

1 Like