From 6359ff32b5f0069921629e07595850a776d324a4 Mon Sep 17 00:00:00 2001
From: Joshua Harlow <harlowja@yahoo-inc.com>
Date: Fri, 20 Mar 2015 15:27:11 -0700
Subject: [PATCH] Always try to use the latest virtualenv
Instead of fixing on an old version of virtualenv that is
fixed at 1.11.4 which has an older version of pip (which does not
like the new version specifications) we should always try to use
the latest to ensure that we find bugs early, and also so that we
can parse the new version specifications without dying.
Change-Id: I73c981a9683868455c3326c4e9aebe50608ae184
---
modules/openstack_project/manifests/base.pp | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/modules/openstack_project/manifests/base.pp b/modules/openstack_project/manifests/base.pp
index bc9b082524..fa02da700a 100644
--- a/modules/openstack_project/manifests/base.pp
+++ b/modules/openstack_project/manifests/base.pp
@@ -60,15 +60,9 @@ class openstack_project::base(
}
include pip
- $desired_virtualenv = '1.11.4'
- if (( versioncmp($::virtualenv_version, $desired_virtualenv) < 0 )) {
- $virtualenv_ensure = $desired_virtualenv
- } else {
- $virtualenv_ensure = present
- }
package { 'virtualenv':
- ensure => $virtualenv_ensure,
+ ensure => latest,
provider => pip,
require => Class['pip'],
}