[Yahoo-eng-team] [Bug 1266962] Re: Remove set_time_override in timeutils

2018-01-30 Thread Telles Mota Vidal Nóbrega 
** Changed in: sahara
   Status: In Progress => Invalid

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

Title:
  Remove set_time_override in timeutils

Status in Ceilometer:
  Fix Released
Status in Cinder:
  Fix Released
Status in gantt:
  New
Status in Glance:
  Fix Released
Status in OpenStack Heat:
  In Progress
Status in Ironic:
  Fix Released
Status in OpenStack Identity (keystone):
  Fix Released
Status in keystonemiddleware:
  In Progress
Status in Manila:
  Fix Released
Status in neutron:
  In Progress
Status in OpenStack Compute (nova):
  Fix Released
Status in oslo.messaging:
  Fix Released
Status in oslo.utils:
  New
Status in python-keystoneclient:
  Fix Released
Status in python-novaclient:
  Fix Released
Status in rack:
  In Progress
Status in Sahara:
  Invalid
Status in tuskar:
  Fix Released
Status in zaqar:
  Fix Released

Bug description:
  set_time_override was written as a helper function to mock utcnow in
  unittests.

  However we now use mock or fixture to mock our objects so
  set_time_override has become obsolete.

  We should first remove all usage of set_time_override from downstream
  projects before deleting it from oslo.

  List of attributes and functions to be removed from timeutils:
  * override_time
  * set_time_override()
  * clear_time_override()
  * advance_time_delta()
  * advance_time_seconds()

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1356053] Re: Doesn't properly get keystone endpoint when Keystone is configured to use templated catalog

2014-11-18 Thread Telles Mota Vidal Nóbrega 
** Also affects: python-saharaclient
   Importance: Undecided
   Status: New

** Changed in: python-saharaclient
 Assignee: (unassigned) = Telles Mota Vidal Nóbrega (tellesmvn)

** Changed in: sahara
   Status: In Progress = Confirmed

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

Title:
  Doesn't properly get keystone endpoint when Keystone is configured to
  use templated catalog

Status in devstack - openstack dev environments:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in Python client library for Sahara (ex. Savanna):
  New
Status in OpenStack Data Processing (Sahara, ex. Savanna):
  Confirmed

Bug description:
  When using the keystone static catalog file to register endpoints 
(http://docs.openstack.org/developer/keystone/configuration.html#file-based-service-catalog-templated-catalog),
 an endpoint registered (correctly) as catalog.region.data_processing gets 
read as data-processing by keystone.
  Thus, when Sahara looks for an endpoint, it is unable to find one for 
data_processing.

  This causes a problem with the commandline interface and the
  dashboard.

  Keystone seems to be converting underscores to dashes here:
  
https://github.com/openstack/keystone/blob/master/keystone/catalog/backends/templated.py#L47

  modifying this line to not perform the replacement seems to work fine
  for me, but may have unintended consequences.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1356053] Re: Doesn't properly get keystone endpoint when Keystone is configured to use templated catalog

2014-11-18 Thread Telles Mota Vidal Nóbrega 
** Also affects: tempest
   Importance: Undecided
   Status: New

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

Title:
  Doesn't properly get keystone endpoint when Keystone is configured to
  use templated catalog

Status in devstack - openstack dev environments:
  In Progress
Status in OpenStack Dashboard (Horizon):
  In Progress
Status in Python client library for Sahara (ex. Savanna):
  In Progress
Status in OpenStack Data Processing (Sahara, ex. Savanna):
  In Progress
Status in Tempest:
  New

Bug description:
  When using the keystone static catalog file to register endpoints 
(http://docs.openstack.org/developer/keystone/configuration.html#file-based-service-catalog-templated-catalog),
 an endpoint registered (correctly) as catalog.region.data_processing gets 
read as data-processing by keystone.
  Thus, when Sahara looks for an endpoint, it is unable to find one for 
data_processing.

  This causes a problem with the commandline interface and the
  dashboard.

  Keystone seems to be converting underscores to dashes here:
  
https://github.com/openstack/keystone/blob/master/keystone/catalog/backends/templated.py#L47

  modifying this line to not perform the replacement seems to work fine
  for me, but may have unintended consequences.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1328966] [NEW] nova api v2 should be able to return detailed quotas

2014-06-11 Thread Telles Mota Vidal Nóbrega 
Public bug reported:

Compute v2 API shows that there is a method to get detailed quota
information but this implementation is not done.

** Affects: nova
 Importance: Undecided
 Assignee: Telles Mota Vidal Nóbrega (tellesmvn)
 Status: New

** Changed in: nova
 Assignee: (unassigned) = Telles Mota Vidal Nóbrega (tellesmvn)

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

Title:
  nova api v2 should be able to return detailed quotas

Status in OpenStack Compute (Nova):
  New

Bug description:
  Compute v2 API shows that there is a method to get detailed quota
  information but this implementation is not done.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1328966] Re: nova api v2 should be able to return detailed quotas

2014-06-11 Thread Telles Mota Vidal Nóbrega 
** Also affects: python-novaclient
   Importance: Undecided
   Status: New

** Changed in: python-novaclient
 Assignee: (unassigned) = Telles Mota Vidal Nóbrega (tellesmvn)

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

Title:
  nova api v2 should be able to return detailed quotas

Status in OpenStack Compute (Nova):
  In Progress
Status in Python client library for Nova:
  New

Bug description:
  Compute v2 API shows that there is a method to get detailed quota
  information but this implementation is not done.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1290857] [NEW] Image list api is wrong

2014-03-11 Thread Telles Mota Vidal Nóbrega 
Public bug reported:

The Compute API explains that to list images you need to call v2/images
but this information is wrong because the right url is
v2/{project_id}/images

** Affects: nova
 Importance: Undecided
 Assignee: Telles Mota Vidal Nóbrega (tellesmvn)
 Status: Confirmed

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

Title:
  Image list api is wrong

Status in OpenStack Compute (Nova):
  Confirmed

Bug description:
  The Compute API explains that to list images you need to call
  v2/images but this information is wrong because the right url is
  v2/{project_id}/images

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1290857] Re: Image list api is wrong

2014-03-11 Thread Telles Mota Vidal Nóbrega 
** Project changed: nova = openstack-api-site

** Description changed:

  The Compute API explains that to list images you need to call v2/images
  but this information is wrong because the right url is
  v2/{project_id}/images
+ 
+ The problem can be found here:
+ http://api.openstack.org/api-ref-compute.html#compute_images

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

Title:
  Image list api is wrong

Status in OpenStack API documentation site:
  Confirmed

Bug description:
  The Compute API explains that to list images you need to call
  v2/images but this information is wrong because the right url is
  v2/{project_id}/images

  The problem can be found here:
  http://api.openstack.org/api-ref-compute.html#compute_images

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-api-site/+bug/1290857/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1234192] Re: Nova documentation for running a subset of unit tests is out of date

2013-10-30 Thread Telles Mota Vidal Nóbrega 
** Changed in: nova
   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/1234192

Title:
  Nova documentation for running a subset of unit tests is out of date

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  The documentation section about running a subset of tests
  (http://docs.openstack.org/developer/nova/devref/unit_tests.html#running-a
  -subset-of-tests) is wrong (or out of date).

  To run a tests in some specific class you have to pass the arguments to the 
run_tests.sh script following the format:
  ./run_tests.sh package.class_name
  and not package:class_name, as the documentation says.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

[Yahoo-eng-team] [Bug 1183633] Re: nova-compute wedged by deleting an in-use baremetal node

2013-10-15 Thread Telles Mota Vidal Nóbrega 
I talked to Robert Collins  and tried to reproduce the bug, but it didnt
happen again, i tried several times and at last ran a test he suggested
and the bug didn't happen, so he said that i could mark this bug as fix
released.

** Changed in: nova
   Status: Triaged = Fix Released

** Changed in: tripleo
   Status: Triaged = 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/1183633

Title:
  nova-compute wedged by deleting an in-use baremetal node

Status in OpenStack Compute (Nova):
  Fix Released
Status in tripleo - openstack on openstack:
  Fix Released

Bug description:
  we deleted a node that had an instance sortof on it, because we
  thought it was dead.

  symptoms:
  nova compute stops checking in:
  $ nova service-list 
  
+--+---+--+-+---++
  | Binary   | Host  | Zone | Status  | State | Updated_at  
   |
  
+--+---+--+-+---++
  | nova-cert| foo.novalocal | internal | enabled | up| 
2013-05-24T01:45:02.00 |
  | nova-compute | foo.novalocal | nova | enabled | down  | 
2013-05-23T22:16:26.00 |
  | nova-conductor   | foo.novalocal | internal | enabled | up| 
2013-05-24T01:45:04.00 |
  | nova-consoleauth | foo.novalocal | internal | enabled | up| 
2013-05-24T01:45:03.00 |
  | nova-scheduler   | foo.novalocal | internal | enabled | up| 
2013-05-24T01:45:03.00 |
  
+--+---+--+-+---++

  and it's log is full of repeating attempts to start it where it dies [because 
upstart is restarting it]
  2013-05-24 01:48:52,227.227 28649 INFO nova.openstack.common.periodic_task 
[-] Skipping periodic task _periodic_update_dns because its interval is negative
  2013-05-24 01:48:52,291.291 28649 INFO nova.virt.driver [-] Loading compute 
driver 'baremetal.driver.BareMetalDriver'
  2013-05-24 01:48:52,346.346 28649 INFO nova.openstack.common.rpc.common 
[req-08ee3ab5-fc1f-4550-a203-c0fb37d9a9e3 None None] Connected to AMQP server 
on 127.0.0.1:5672
  2013-05-24 01:48:52,409.409 28649 AUDIT nova.service [-] Starting compute 
node (version 2013.2)
  2013-05-24 01:48:52,817.817 28649 ERROR nova.compute.manager 
[req-76be156c-c2d9-4c7c-aa00-3ce45b3b49a8 None None] Instance 
test-332aac1b-8987-488d-9ea2-19f26a16907d found in the hypervisor, but not in 
the database
  2013-05-24 01:48:52,817.817 28649 ERROR nova.compute.manager 
[req-76be156c-c2d9-4c7c-aa00-3ce45b3b49a8 None None] Instance 
bootstack-vm.notcompute found in the hypervisor, but not in the database
  2013-05-24 01:48:52,817.817 28649 ERROR nova.compute.manager 
[req-76be156c-c2d9-4c7c-aa00-3ce45b3b49a8 None None] Instance 
bootstack-vm-4.notcompute found in the hypervisor, but not in the database
  2013-05-24 01:48:52,818.818 28649 ERROR nova.compute.manager 
[req-76be156c-c2d9-4c7c-aa00-3ce45b3b49a8 None None] Instance 
bootstack-vm-testing.notcompute found in the hypervisor, but not in the database
  2013-05-24 01:48:52,818.818 28649 ERROR nova.compute.manager 
[req-76be156c-c2d9-4c7c-aa00-3ce45b3b49a8 None None] Instance 
compute-test.novacompute-0 found in the hypervisor, but not in the database
  2013-05-24 01:48:52,818.818 28649 ERROR nova.compute.manager 
[req-76be156c-c2d9-4c7c-aa00-3ce45b3b49a8 None None] Instance 
test-8b80ff43-ba81-44c6-a22a-fffd6034579a found in the hypervisor, but not in 
the database
  2013-05-24 01:48:52,818.818 28649 ERROR nova.compute.manager 
[req-76be156c-c2d9-4c7c-aa00-3ce45b3b49a8 None None] Instance 
test-cd715548-afd7-4342-8c74-b4d5e5984dd6 found in the hypervisor, but not in 
the database
  2013-05-24 01:48:52,818.818 28649 ERROR nova.compute.manager 
[req-76be156c-c2d9-4c7c-aa00-3ce45b3b49a8 None None] Instance 
test-bb35ffdf-9fae-4e23-8e46-ec76b89c1ce4 found in the hypervisor, but not in 
the database
  2013-05-24 01:48:52,818.818 28649 ERROR nova.compute.manager 
[req-76be156c-c2d9-4c7c-aa00-3ce45b3b49a8 None None] Instance 
test-d01059f8-97ab-4f0a-968b-7411b2ab717c found in the hypervisor, but not in 
the database
  2013-05-24 01:48:52,818.818 28649 ERROR nova.compute.manager 
[req-76be156c-c2d9-4c7c-aa00-3ce45b3b49a8 None None] Instance 
test-f7862b82-268d-4971-b961-a8fe51488b21 found in the hypervisor, but not in 
the database
  2013-05-24 01:48:52,819.819 28649 ERROR nova.compute.manager 
[req-76be156c-c2d9-4c7c-aa00-3ce45b3b49a8 None None] Instance 
test-3f0cdb8f-70ae-43f7-bb98-83c48f5da317 found in the hypervisor, but not in 
the database
  2013-05-24 01:48:52,819.819 28649 ERROR nova.compute.manager 
[req-76be156c-c2d9-4c7c-aa00-3ce45b3b49a8 None None] Instance 
test-d3d7d58f-408c-47ff-993a-4b8327f27541 found in the hypervisor, but not in 
the database