← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1288313] [NEW] PEP8 failures after oslo.rpc release

 

Public bug reported:

Keystone builds are failing PEP8 after a release of the oslo.rpc library
caused the sample config file check to fail.

The failure looks like this in the pep8 log:

2014-03-04 21:43:49.119 | --- /tmp/keystone.SqJmcw/keystone.conf.sample	2014-03-04 21:43:49.086235074 +0000
2014-03-04 21:43:49.119 | +++ etc/keystone.conf.sample	2014-03-04 21:40:36.614869698 +0000
2014-03-04 21:43:49.120 | @@ -168,10 +168,6 @@
2014-03-04 21:43:49.120 |  # enabled). (string value)
2014-03-04 21:43:49.120 |  #kombu_ssl_ca_certs=
2014-03-04 21:43:49.120 |  
2014-03-04 21:43:49.120 | -# How long to wait before reconnecting in response to an AMQP
2014-03-04 21:43:49.121 | -# consumer cancel notification. (floating point value)
2014-03-04 21:43:49.121 | -#kombu_reconnect_delay=1.0
2014-03-04 21:43:49.121 | -
2014-03-04 21:43:49.121 |  # The RabbitMQ broker address where a single node is used.
2014-03-04 21:43:49.121 |  # (string value)
2014-03-04 21:43:49.121 |  #rabbit_host=localhost
2014-03-04 21:43:49.122 | check_uptodate.sh: keystone.conf.sample is not up to date.

** Affects: keystone
     Importance: Undecided
     Assignee: Brant Knudson (blk-u)
         Status: Fix Committed

** Changed in: keystone
       Status: New => Fix Committed

** Changed in: keystone
     Assignee: (unassigned) => Brant Knudson (blk-u)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1288313

Title:
  PEP8 failures after oslo.rpc release

Status in OpenStack Identity (Keystone):
  Fix Committed

Bug description:
  Keystone builds are failing PEP8 after a release of the oslo.rpc
  library caused the sample config file check to fail.

  The failure looks like this in the pep8 log:

  2014-03-04 21:43:49.119 | --- /tmp/keystone.SqJmcw/keystone.conf.sample	2014-03-04 21:43:49.086235074 +0000
  2014-03-04 21:43:49.119 | +++ etc/keystone.conf.sample	2014-03-04 21:40:36.614869698 +0000
  2014-03-04 21:43:49.120 | @@ -168,10 +168,6 @@
  2014-03-04 21:43:49.120 |  # enabled). (string value)
  2014-03-04 21:43:49.120 |  #kombu_ssl_ca_certs=
  2014-03-04 21:43:49.120 |  
  2014-03-04 21:43:49.120 | -# How long to wait before reconnecting in response to an AMQP
  2014-03-04 21:43:49.121 | -# consumer cancel notification. (floating point value)
  2014-03-04 21:43:49.121 | -#kombu_reconnect_delay=1.0
  2014-03-04 21:43:49.121 | -
  2014-03-04 21:43:49.121 |  # The RabbitMQ broker address where a single node is used.
  2014-03-04 21:43:49.121 |  # (string value)
  2014-03-04 21:43:49.121 |  #rabbit_host=localhost
  2014-03-04 21:43:49.122 | check_uptodate.sh: keystone.conf.sample is not up to date.

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


Follow ups

References