yahoo-eng-team team mailing list archive

[Steve Baker <sbaker@xxxxxxxxxx>]

** Changed in: python-heatclient
       Status: Fix Committed => Fix Released

** Changed in: python-heatclient
    Milestone: v0.2.3 => None

** Changed in: python-heatclient
    Milestone: None => v0.2.5

-- 
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:
  Fix Released
Status in Cinder:
  Fix Released
Status in Orchestration API (Heat):
  Fix Released
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in Ironic (Bare Metal Provisioning):
  Fix Committed
Status in OpenStack Identity (Keystone):
  Fix Released
Status in OpenStack Compute (Nova):
  Fix Released
Status in Python client library for Ceilometer:
  Fix Committed
Status in Python client library for Cinder:
  Fix Committed
Status in Python client library for Glance:
  Fix Committed
Status in Python client library for heat:
  Fix Released
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