[Avocado-devel] What is a right way to install avocado?

[Cleber Rosa]

----- Original Message -----
> From: "Andrei Stepanov" <astepano at redhat.com>
> To: "avocado-devel" <avocado-devel at redhat.com>
> Sent: Wednesday, February 1, 2017 11:48:11 AM
> Subject: [Avocado-devel] What is a right way to install avocado?
> 
> Hello.
> 
> We are currently experiencing some issues with avocado / avocado-vt.
> 
> Our automation can be described in next steps:
> 
> 0. Install RHEL 6/7.
> 1. Clone "master" branches for avocado/avocado-vt from github.

Hi Andrei,

Do you need specific features of Avocado not present in the LTS version?  I would strongly recommend that for "production testing", you'd use a more stable version of Avocado.  If you're willing to take a look at this suggested approach, let me if the fix for the Workstation version of EPEL6 works for you.

> 2. In avocado dir:
> 
> make requirements
> python setup.py install
> 
> 3. In avocado-vt dir:
> make link
> pip install sphinx
> pip install -r requirements.txt
> python setup.py install
> 

For avocado-vt, an RPM package is also available (non-LTS, but designed to work with avocado LTS).  Most dependencies would be solved by the package install alone.  Then, dependencies for the test provider, say tp-qemu, could also be installed alongside it (but manually specified).

> 4. Run tests.
> 
> Above commands are run from root account.
> We cannot use this approach any more.
> It doesn't work with RHEL7.3.
> 
> I have opened a bug: https://bugzilla.redhat.com/show_bug.cgi?id=1417613
> Than I had discussion with Tomas Orsava.
> 
> The problem is, running pip as root in Fedora/EPEL is not supported and
> will break your system.
> 
> https://fedoraproject.org/wiki/Changes/Making_sudo_pip_safe
> 
> My question is: what is official way to install avocado/avocado-vt?
> 
> Invoking pip commands from root account is a bad approach.
> 
> Is there a safe way to install avocado & avocado-vt?
>