OpenStack-Ansible

Bug #1755593
Comment #2

Comment 2 for bug 1755593

Revision history for this message

Jeff Albert (jralbert) wrote on 2018-03-21: Re: [Bug 1755593] Re: Rally can't install encapsulated Tempest verifier

Rally installs an encapsulated Tempest of its own to use for verifying OS functionality; in the OSA deployment of Rally, some of the dependencies for its encapsulated Tempest are more recent than the packages that Rally itself requires. In order for Rally to perform all of its functions including verification, its environment has to include packages (specifically Oslo.concurrency) at the versions its encapsulated Tempest requires.

> On Mar 20, 2018, at 10:50 AM, Jean-Philippe Evrard <email address hidden> wrote:
>
> ** Changed in: openstack-ansible
> Status: New => Confirmed
>
> ** Changed in: openstack-ansible
> Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1755593
>
> Title:
> Rally can't install encapsulated Tempest verifier
>
> Status in openstack-ansible:
> Confirmed
>
> Bug description:
> The os_rally role installs Rally in a virtualenv on the utility
> containers. When the virtualenv is instantiated by OSA, that
> instantiation is configured by the "rally_git_install_fragments"
> directive to allow installation from both the OSA-created pip repo as
> well as PyPi.
>
> However, after Rally is installed, a key element of its use is to have
> it build and operate a Tempest verifier self-contained within Rally by
> issuing "rally verify create-verifier --type tempest"; this causes
> Rally to create a new virtualenv for Tempest, git clone it there, and
> attempt to build pip dependencies for it. This fails, because Rally's
> doing its own virtualenv creation that's not configured the same way
> the Rally virtualenv creation was via OSA.
>
> To fix this, I can see a couple possibilities: trying to see whether
> altering the environment that Rally runs in will allow propagation of
> the pip index configuration; or using OSA to pre-install pip
> dependencies into the Rally virtualenv at the versions that Tempest
> will require.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openstack-ansible/+bug/1755593/+subscriptions

> On Mar 20, 2018, at 10:50 AM, Jean-Philippe Evrard <1755593@bugs.launchpad.net> wrote:
> 
> ** Changed in: openstack-ansible
>       Status: New => Confirmed
> 
> ** Changed in: openstack-ansible
>   Importance: Undecided => Medium
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1755593
> 
> Title:
>  Rally can't install encapsulated Tempest verifier
> 
> Status in openstack-ansible:
>  Confirmed
> 
> Bug description:
>  The os_rally role installs Rally in a virtualenv on the utility
>  containers. When the virtualenv is instantiated by OSA, that
>  instantiation is configured by the "rally_git_install_fragments"
>  directive to allow installation from both the OSA-created pip repo as
>  well as PyPi.
> 
>  However, after Rally is installed, a key element of its use is to have
>  it build and operate a Tempest verifier self-contained within Rally by
>  issuing "rally verify create-verifier --type tempest"; this causes
>  Rally to create a new virtualenv for Tempest, git clone it there, and
>  attempt to build pip dependencies for it. This fails, because Rally's
>  doing its own virtualenv creation that's not configured the same way
>  the Rally virtualenv creation was via OSA.
> 
>  To fix this, I can see a couple possibilities: trying to see whether
>  altering the environment that Rally runs in will allow propagation of
>  the pip index configuration; or using OSA to pre-install pip
>  dependencies into the Rally virtualenv at the versions that Tempest
>  will require.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openstack-ansible/+bug/1755593/+subscriptions