yahoo-eng-team team mailing list archive

[Emilien Macchi <1657467@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Deploying Nova Placement API used to work a few days ago in TripleO and
Puppet OpenStack CIs but not anymore.

"Unable to refresh my resource provider record"

nova-compute log files:
http://logs.openstack.org/66/421366/1/check/gate-puppet-openstack-integration-4-scenario004-tempest-centos-7/f138bcc/logs/nova/nova-compute.txt.gz#_2017-01-17_17_32_39_092

nova.conf:
https://paste.fedoraproject.org/529703/14847479/

** Affects: nova
     Importance: Undecided
         Status: New

** Affects: tripleo
     Importance: High
         Status: Triaged

** Also affects: tripleo
   Importance: Undecided
       Status: New

** Changed in: tripleo
       Status: New => Triaged

** Changed in: tripleo
   Importance: Undecided => High

** Changed in: tripleo
    Milestone: None => ocata-rc1

-- 
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/1657467

Title:
  placement: unable to refresh  compute resource provider record

Status in OpenStack Compute (nova):
  New
Status in tripleo:
  Triaged

Bug description:
  Deploying Nova Placement API used to work a few days ago in TripleO
  and Puppet OpenStack CIs but not anymore.

  "Unable to refresh my resource provider record"

  nova-compute log files:
  http://logs.openstack.org/66/421366/1/check/gate-puppet-openstack-integration-4-scenario004-tempest-centos-7/f138bcc/logs/nova/nova-compute.txt.gz#_2017-01-17_17_32_39_092

  nova.conf:
  https://paste.fedoraproject.org/529703/14847479/

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