yahoo-eng-team team mailing list archive

[OpenStack Hudson <1200214@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/36671
Committed: http://github.com/openstack/tempest/commit/b3635c99a8332400b2c7a05c8f63bf5ac8618663
Submitter: Jenkins
Branch:    master

commit b3635c99a8332400b2c7a05c8f63bf5ac8618663
Author: Matthew Treinish <treinish@xxxxxxxxxxxxxxxxxx>
Date:   Thu Jul 11 10:44:18 2013 -0400

    Remove version caps from python-fooclient.
    
    This removes the version caps from python-neutronclient and
    python-cinderclient in Tempest. Per mailing list thread, allowing
    any project to cap one of our own clients actually prevents us
    from testing that client's git version in devstack gate (because
    there are 2 ways to install a python client, one from git, one from
    pip). This can allow bugs to creep into the clients because they are
    no longer tested in the gate.
    
    An exception is currently being made for neutron client because of
    the need for an incompatible change in their next release.
    
    Fixes bug #1200214 for Tempest
    
    Change-Id: I00a451448ec380068905b28f3b74656c083dc261


** Changed in: tempest
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1200214

Title:
  Relax OpenStack upper capping of client versions

Status in Ceilometer:
  New
Status in Cinder:
  Fix Committed
Status in Orchestration API (Heat):
  Triaged
Status in OpenStack Dashboard (Horizon):
  Confirmed
Status in Ironic (Bare Metal Provisioning):
  In Progress
Status in OpenStack Identity (Keystone):
  In Progress
Status in OpenStack Compute (Nova):
  In Progress
Status in Python client library for Ceilometer:
  New
Status in Python client library for Glance:
  New
Status in Python client library for heat:
  Triaged
Status in Tempest:
  Fix Released

Bug description:
  Because of the way the gate  process pip requirements (one project at a time), on a current gate run 
  we actually install and uninstall python-keystoneclient 4 times in a 
  normal run, flipping back and forth from HEAD to 0.2.5.

  http://paste.openstack.org/show/39880/ - shows what's going on

  The net of this means that if any of the projects specify a capped 
  client, it has the potential for preventing that client from being 
  tested in the gate. 

  As part of the discussion here:

  http://lists.openstack.org/pipermail/openstack-
  dev/2013-July/011660.html

  it was suggested to only cap client versions at the major version,
  since all minor version bumps must be strictly backward compatible by
  policy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1200214/+subscriptions