[Yahoo-eng-team] [Bug 1728368] Re: oslo.serialization 2.21.2 breaks glance

2018-01-19 Thread John L. Villalovos 
** Changed in: oslo.serialization
   Status: New => Invalid

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

Title:
  oslo.serialization 2.21.2 breaks glance

Status in Glance:
  In Progress
Status in oslo.serialization:
  Invalid

Bug description:
  glance unittests break with 2.21.2, work fine with 2.21.1:

  ==
  FAIL: 
glance.tests.unit.v1.test_registry_api.TestRegistryAPI.test_update_all_image_members
  --
  Traceback (most recent call last):
File "glance/tests/unit/v1/test_registry_api.py", line 1629, in 
test_update_all_image_members
  content_type='json')
File "glance/tests/utils.py", line 564, in get_api_response_ext
  self.assertEqual(res.status_int, http_resp)
File 
"/data/dmueller/src/Cloud/glance/.tox/venv/lib/python2.7/site-packages/testtools/testcase.py",
 line 411, in assertEqual
  self.assertThat(observed, matcher, message)
File 
"/data/dmueller/src/Cloud/glance/.tox/venv/lib/python2.7/site-packages/testtools/testcase.py",
 line 498, in assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: 200 != 204

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1728368/+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 1652186] [NEW] CI jobs failing in devstack/lib/keystone

2016-12-22 Thread John L. Villalovos 
Public bug reported:

CI Jobs are failing across OpenStack with an error like this:

http://logs.openstack.org/39/414339/2/check/gate-tempest-dsvm-ironic-
ipa-partition-pxe_snmp-tinyipa-ubuntu-xenial-
nv/1d5e63d/logs/devstacklog.txt.gz#_2016-12-22_22_25_10_787


2016-12-22 22:25:08.714 | 2016-12-22 22:25:08.714 31714 INFO keystone.cmd.cli 
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Granted admin on admin to 
user admin.
2016-12-22 22:25:08.731 | 2016-12-22 22:25:08.730 31714 INFO keystone.cmd.cli 
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Created region RegionOne
2016-12-22 22:25:08.763 | 2016-12-22 22:25:08.763 31714 INFO keystone.cmd.cli 
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Created admin endpoint 
http://15.184.67.84/identity_admin
2016-12-22 22:25:08.775 | 2016-12-22 22:25:08.774 31714 INFO keystone.cmd.cli 
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Created internal endpoint 
http://15.184.67.84/identity
2016-12-22 22:25:08.787 | 2016-12-22 22:25:08.787 31714 INFO keystone.cmd.cli 
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Created public endpoint 
http://15.184.67.84/identity
2016-12-22 22:25:08.793 | 2016-12-22 22:25:08.793 31714 INFO 
keystone.assignment.core [req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] 
Creating the default role 9fe2ff9ee4384b1894a90878d3e92bab because it does not 
exist.
2016-12-22 22:25:08.923 | + ./stack.sh:main:1065 :   
create_keystone_accounts
2016-12-22 22:25:08.927 | + lib/keystone:create_keystone_accounts:371 :   local 
admin_project
2016-12-22 22:25:08.931 | + lib/keystone:create_keystone_accounts:372 :   
openstack project show admin -f value -c id
2016-12-22 22:25:10.787 | /opt/stack/new/devstack/lib/keystone: line 366: 31727 
Illegal instruction openstack project show "admin" -f value -c id
2016-12-22 22:25:10.791 | + lib/keystone:create_keystone_accounts:372 :   true
2016-12-22 22:25:10.796 | ++ lib/keystone:create_keystone_accounts:373 :   
openstack project show admin -f value -c id
2016-12-22 22:25:12.589 | + lib/keystone:create_keystone_accounts:373 :   
admin_project=
2016-12-22 22:25:12.593 | + lib/keystone:create_keystone_accounts:1  :   
exit_trap
2016-12-22 22:25:12.596 | + ./stack.sh:exit_trap:487 :   local 
r=132
2016-12-22 22:25:12.602 | ++ ./stack.sh:exit_trap:488 :   jobs 
-p
2016-12-22 22:25:12.606 | + ./stack.sh:exit_trap:488 :   
jobs=31048
2016-12-22 22:25:12.610 | + ./stack.sh:exit_trap:491 :   [[ -n 
31048 ]]
2016-12-22 22:25:12.614 | + ./stack.sh:exit_trap:491 :   [[ -n 
/opt/stack/new/devstacklog.txt.2016-12-22-221622 ]]
2016-12-22 22:25:12.617 | + ./stack.sh:exit_trap:491 :   [[ 
True == \T\r\u\e ]]
2016-12-22 22:25:12.621 | + ./stack.sh:exit_trap:492 :   echo 
'exit_trap: cleaning up child processes'
2016-12-22 22:25:12.621 | exit_trap: cleaning up child processes
2016-12-22 22:25:12.625 | + ./stack.sh:exit_trap:493 :   kill 
31048
2016-12-22 22:25:12.625 | ./stack.sh: line 493: kill: (31048) - No such process

** Affects: ironic
 Importance: Undecided
 Status: New

** Affects: nova
 Importance: Undecided
 Status: New

** Affects: openstack-gate
 Importance: Undecided
 Status: New

** Also affects: openstack-gate
   Importance: Undecided
   Status: New

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

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

Title:
  CI jobs failing in devstack/lib/keystone

Status in Ironic:
  New
Status in OpenStack Compute (nova):
  New
Status in OpenStack-Gate:
  New

Bug description:
  CI Jobs are failing across OpenStack with an error like this:

  http://logs.openstack.org/39/414339/2/check/gate-tempest-dsvm-ironic-
  ipa-partition-pxe_snmp-tinyipa-ubuntu-xenial-
  nv/1d5e63d/logs/devstacklog.txt.gz#_2016-12-22_22_25_10_787

  
  2016-12-22 22:25:08.714 | 2016-12-22 22:25:08.714 31714 INFO keystone.cmd.cli 
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Granted admin on admin to 
user admin.
  2016-12-22 22:25:08.731 | 2016-12-22 22:25:08.730 31714 INFO keystone.cmd.cli 
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Created region RegionOne
  2016-12-22 22:25:08.763 | 2016-12-22 22:25:08.763 31714 INFO keystone.cmd.cli 
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Created admin endpoint 
http://15.184.67.84/identity_admin
  2016-12-22 22:25:08.775 | 2016-12-22 22:25:08.774 31714 INFO keystone.cmd.cli 
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Created internal endpoint 
http://15.184.67.84/identity
  2016-12-22 22:25:08.787 | 2016-12-22 22:25:08.787 31714 INFO keystone.cmd.cli 
[req-f336127d-0628-4b9d-bcc7-a87863c3127e - - - - -] Created public endpoint

[Yahoo-eng-team] [Bug 1629133] Re: New neutron subnet pool support breaks multinode testing.

2016-10-05 Thread John L. Villalovos 
** Also affects: ironic-python-agent
   Importance: Undecided
   Status: New

** Changed in: ironic-python-agent
   Importance: Undecided => Critical

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

Title:
  New neutron subnet pool support breaks multinode testing.

Status in devstack:
  In Progress
Status in Ironic:
  New
Status in ironic-python-agent:
  New
Status in Magnum:
  New
Status in Manila:
  New
Status in neutron:
  Incomplete

Bug description:
  The new subnet pool support in devstack breaks multinode testing bceause it 
results in the route for 10.0.0.0/8 being set to via br-ex when the host has 
interfaces that are actually on 10 nets and that is where we need the routes to 
go out. Multinode testing is affected because it uses these 10 net addresses to 
run the vxlan overlays between hosts.
  For many years devstack-gate has set FIXED_RANGE to ensure that the networks 
devstack uses do not interfere with the underlying test host's networking. 
However this setting was completely ignored when setting up the subnet pools.

  I think the correct way to fix this is to use a much smaller subnet
  pool range to avoid conflicting with every possible 10.0.0.0/8 network
  in the wild, possibly by defaulting to the existing FIXED_RANGE
  information. Using the existing information will help ensure that
  anyone with networks in 10.0.0.0/8 will continue to work if they have
  specified a range that doesn't conflict using this variable.

  In addition to this we need to clearly document what this new stuff in
  devstack does and how people can work around it should they conflict
  with the new defaults we end up choosing.

  I have proposed https://review.openstack.org/379543 which mostly works
  except it fails one tempest test that apparently depends on this new
  subnet pool stuff. Specifically the V6 range isn't large enough aiui.

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1629133/+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 1629133] Re: New neutron subnet pool support breaks multinode testing.

2016-09-29 Thread John L. Villalovos 
** Also affects: ironic
   Importance: Undecided
   Status: New

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

Title:
  New neutron subnet pool support breaks multinode testing.

Status in devstack:
  New
Status in Ironic:
  New
Status in neutron:
  New

Bug description:
  The new subnet pool support in devstack breaks multinode testing bceause it 
results in the route for 10.0.0.0/8 being set to via br-ex when the host has 
interfaces that are actually on 10 nets and that is where we need the routes to 
go out. Multinode testing is affected because it uses these 10 net addresses to 
run the vxlan overlays between hosts.
  For many years devstack-gate has set FIXED_RANGE to ensure that the networks 
devstack uses do not interfere with the underlying test host's networking. 
However this setting was completely ignored when setting up the subnet pools.

  I think the correct way to fix this is to use a much smaller subnet
  pool range to avoid conflicting with every possible 10.0.0.0/8 network
  in the wild, possibly by defaulting to the existing FIXED_RANGE
  information. Using the existing information will help ensure that
  anyone with networks in 10.0.0.0/8 will continue to work if they have
  specified a range that doesn't conflict using this variable.

  In addition to this we need to clearly document what this new stuff in
  devstack does and how people can work around it should they conflict
  with the new defaults we end up choosing.

  I have proposed https://review.openstack.org/379543 which mostly works
  except it fails one tempest test that apparently depends on this new
  subnet pool stuff. Specifically the V6 range isn't large enough aiui.

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1629133/+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 1618666] Re: deprecated warning for SafeConfigParser

2016-09-19 Thread John L. Villalovos 
** Also affects: ironic
   Importance: Undecided
   Status: New

** Changed in: ironic
   Importance: Undecided => Low

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

Title:
  deprecated warning for SafeConfigParser

Status in Glance:
  In Progress
Status in glance_store:
  In Progress
Status in Ironic:
  New
Status in OpenStack Identity (keystone):
  Fix Released
Status in neutron:
  Fix Released
Status in OpenStack Compute (nova):
  In Progress
Status in PBR:
  Fix Released
Status in python-swiftclient:
  In Progress
Status in OpenStack Object Storage (swift):
  In Progress
Status in tempest:
  In Progress
Status in OpenStack DBaaS (Trove):
  In Progress

Bug description:
  tox -e py34 is reporting a deprecation warning for SafeConfigParser

  /octavia/.tox/py34/lib/python3.4/site-packages/pbr/util.py:207: 
DeprecationWarning: The SafeConfigParser class has been renamed to ConfigParser 
in Python 3.2. This alias will be removed in future versions. Use ConfigParser 
directly instead.
parser = configparser.SafeConfigParser()

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1618666/+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 1610960] Re: Invalid input for external_gateway_info. Reason: '' is not a valid UUID.

2016-08-08 Thread John L. Villalovos 
** Also affects: os-client-config
   Importance: Undecided
   Status: New

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

Title:
  Invalid input for external_gateway_info. Reason: '' is not a valid
  UUID.

Status in grenade:
  New
Status in Ironic:
  Confirmed
Status in Manila:
  New
Status in neutron:
  Confirmed
Status in os-client-config:
  New
Status in tempest:
  New

Bug description:
  Currently grenade gate is completely busted with:

  ft14.1: setUpClass 
(tempest.api.identity.admin.v3.test_domains.DomainsTestJSON)_StringException: 
Traceback (most recent call last):
File "tempest/test.py", line 273, in setUpClass
  six.reraise(etype, value, trace)
File "tempest/test.py", line 261, in setUpClass
  cls.setup_credentials()
File "tempest/test.py", line 361, in setup_credentials
  credential_type=credentials_type)
File "tempest/test.py", line 535, in get_client_manager
  creds = getattr(cred_provider, credentials_method)()
File "tempest/common/dynamic_creds.py", line 305, in get_primary_creds
  return self.get_credentials('primary')
File "tempest/common/dynamic_creds.py", line 297, in get_credentials
  credentials.tenant_id)
File "tempest/common/dynamic_creds.py", line 214, in 
_create_network_resources
  router = self._create_router(router_name, tenant_id)
File "tempest/common/dynamic_creds.py", line 273, in _create_router
  tenant_id=tenant_id)
File "tempest/lib/services/network/routers_client.py", line 26, in 
create_router
  return self.create_resource(uri, post_body)
File "tempest/lib/services/network/base.py", line 60, in create_resource
  resp, body = self.post(req_uri, req_post_data)
File "tempest/lib/common/rest_client.py", line 273, in post
  return self.request('POST', url, extra_headers, headers, body, chunked)
File "tempest/lib/common/rest_client.py", line 667, in request
  resp, resp_body)
File "tempest/lib/common/rest_client.py", line 770, in _error_checker
  raise exceptions.BadRequest(resp_body, resp=resp)
  tempest.lib.exceptions.BadRequest: Bad request
  Details: {u'type': u'HTTPBadRequest', u'detail': u'', u'message': u"Invalid 
input for external_gateway_info. Reason: '' is not a valid UUID."}

  http://logs.openstack.org/26/352326/1/check/gate-grenade-dsvm-neutron-
  ubuntu-trusty/acf0516/console.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/grenade/+bug/1610960/+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 1537754] Re: Unable to associate floating IP 172.24.5.4 to fixed IP 10.1.0.5 for instance ...

2016-01-26 Thread John L. Villalovos 
** Also affects: neutron
   Importance: Undecided
   Status: New

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

Title:
  Unable to associate floating IP 172.24.5.4 to fixed IP 10.1.0.5 for
  instance ...

Status in Ironic:
  Triaged
Status in neutron:
  New

Bug description:
  Gate seems to be failing because of:

  2016-01-25 12:27:22.139 ERROR nova.api.openstack.compute.floating_ips 
[req-ebc3999e-b054-400f-a85e-bc3446a49f44 tempest-BaremetalBasicOps-1761846040 
tempest-BaremetalBasicOps-1606508311] Unable to associate floating IP 
172.24.5.4 to fixed IP 10.1.0.5 for instance 
213b10ac-06eb-4ea0-b638-263f2b75a329. Error: Router 
a771a17f-0224-4293-b757-59fcc6d21410 could not be found
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips 
Traceback (most recent call last):
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips   
File "/opt/stack/new/nova/nova/api/openstack/compute/floating_ips.py", line 
238, in _add_floating_ip
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips
 fixed_address=fixed_address)
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips   
File "/opt/stack/new/nova/nova/network/base_api.py", line 77, in wrapper
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips
 res = f(self, context, *args, **kwargs)
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips   
File "/opt/stack/new/nova/nova/network/neutronv2/api.py", line 1203, in 
associate_floating_ip
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips
 client.update_floatingip(fip['id'], {'floatingip': param})
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips   
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", 
line 100, in with_params
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips
 ret = self.function(instance, *args, **kwargs)
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips   
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", 
line 714, in update_floatingip
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips
 return self.put(self.floatingip_path % (floatingip), body=body)
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips   
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", 
line 275, in put
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips
 headers=headers, params=params)
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips   
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", 
line 243, in retry_request
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips
 headers=headers, params=params)
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips   
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", 
line 206, in do_request
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips
 self._handle_fault_response(status_code, replybody)
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips   
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", 
line 182, in _handle_fault_response
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips
 exception_handler_v20(status_code, des_error_body)
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips   
File "/usr/local/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", 
line 69, in exception_handler_v20
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips
 status_code=status_code)
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips 
NotFound: Router a771a17f-0224-4293-b757-59fcc6d21410 could not be found
  2016-01-25 12:27:22.139 2247 ERROR nova.api.openstack.compute.floating_ips 

  http://logs.openstack.org/10/255310/10/check/gate-tempest-dsvm-ironic-
  pxe_ssh/67c7e80/logs/screen-n-api.txt.gz#_2016-01-25_12_27_22_139

To manage notifications about this bug go to:
https://bugs.launchpad.net/ironic/+bug/1537754/+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 1498005] Re: EC2 API RegisterImage method ignores KernelId and RamdiskId

2015-10-06 Thread John L. Villalovos 
** Changed in: nova
   Status: Incomplete => Won't Fix

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

Title:
  EC2 API RegisterImage method ignores KernelId and RamdiskId

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest creates
  an AMI image with kernel and ramdisk parameters, here are the values
  passed to n-api:

  2015-09-17 21:42:43.733 INFO nova.api.ec2 
[req-66cd4f86-a320-4173-953b-0a5c441ae8f9 tempest-InstanceRunTest-1462515106 
tempest-InstanceRunTest-17803527] 1.211148s 127.0.0.1 POST / 
CloudController:RegisterImage 200 [Boto/2.38.0 Python/2.7.6 
Linux/3.13.0-63-generic] application/x-www-form-urlencoded text/xml
  2015-09-17 21:42:43.733 INFO nova.ec2.wsgi.server 
[req-66cd4f86-a320-4173-953b-0a5c441ae8f9 tempest-InstanceRunTest-1462515106 
tempest-InstanceRunTest-17803527] 127.0.0.1 "POST / HTTP/1.1" status: 200 len: 
299 time: 1.2117610
  2015-09-17 21:42:43.924 24107 DEBUG nova.ec2.wsgi.server [-] (24107) accepted 
('127.0.0.1', 59659) server 
/usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py:826
  2015-09-17 21:42:43.990 DEBUG nova.api.ec2 
[req-c627bfe6-4fe2-4c5c-ad39-176d348626ce tempest-InstanceRunTest-1462515106 
tempest-InstanceRunTest-17803527] action: RegisterImage __call__ 
/opt/stack/new/nova/nova/api/ec2/__init__.py:388
  2015-09-17 21:42:43.991 DEBUG nova.api.ec2 
[req-c627bfe6-4fe2-4c5c-ad39-176d348626ce tempest-InstanceRunTest-1462515106 
tempest-InstanceRunTest-17803527] arg: Name   val: 
tempest-ami-name-277527092 __call__ 
/opt/stack/new/nova/nova/api/ec2/__init__.py:391
  2015-09-17 21:42:43.991 DEBUG nova.api.ec2 
[req-c627bfe6-4fe2-4c5c-ad39-176d348626ce tempest-InstanceRunTest-1462515106 
tempest-InstanceRunTest-17803527] arg: KernelId   val: aki-0013 
__call__ /opt/stack/new/nova/nova/api/ec2/__init__.py:391
  2015-09-17 21:42:43.991 DEBUG nova.api.ec2 
[req-c627bfe6-4fe2-4c5c-ad39-176d348626ce tempest-InstanceRunTest-1462515106 
tempest-InstanceRunTest-17803527] arg: ImageLocation  val: 
tempest-s3bucket-1592249957/cirros-0.3.4-x86_64-blank.img.manifest.xml __call__ 
/opt/stack/new/nova/nova/api/ec2/__init__.py:391
  2015-09-17 21:42:43.991 DEBUG nova.api.ec2 
[req-c627bfe6-4fe2-4c5c-ad39-176d348626ce tempest-InstanceRunTest-1462515106 
tempest-InstanceRunTest-17803527] arg: RamdiskId  val: ari-0014 
__call__ /opt/stack/new/nova/nova/api/ec2/__init__.py:391

  Despite of that, KernelId and RamdiskId are ignored and image is
  created without these properties. In case of using Ironic driver, an
  image without kernel_id and ramdisk_id properties is considered a
  whole-disk image, and
  tempest.thirdparty.boto.test_ec2_instance_run.InstanceRunTest fails in
  gate, because nodes created by devstack have ephemeral_gb=1 and Ironic
  cannot deploy a whole-disk image when ephemeral or swap are set, which
  causes the following exception:

  n-cpu:
  2015-09-12 16:32:09.817 DEBUG nova.compute.manager 
[req-3e3492fa-056e-407f-acc4-bb8c85b16883 tempest-InstanceRunTest-21715614 
tempest-InstanceRunTest-326056565] [instance: 
d09fb517-c17c-4405-9d29-13a1f92a669f] Build of instance 
d09fb517-c17c-4405-9d29-13a1f92a669f was re-scheduled: RPC do_node_deploy 
failed to validate deploy or power info. Error: Cannot deploy whole disk image 
with swap or ephemeral size set (HTTP 500) _do_build_and_run_instance 
/opt/stack/new/nova/nova/compute/manager.py:1923

  ir-api:
  2015-09-12 16:32:08.808 22705 ERROR wsme.api 
[req-6840c2a2-3923-47dd-9ef6-451fa7c6e3f7 ] Server-side error: "RPC 
do_node_deploy failed to validate deploy or power info. Error: Cannot deploy 
whole disk image with swap or ephemeral size set
  Traceback (most recent call last):

    File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", 
line 142, in inner
  return func(*args, **kwargs)

    File "/opt/stack/new/ironic/ironic/conductor/manager.py", line 732, in 
do_node_deploy
  "power info. Error: %(msg)s") % {'msg': e})

  InstanceDeployFailure: RPC do_node_deploy failed to validate deploy or power 
info. Error: Cannot deploy whole disk image with swap or ephemeral size set
  ". Detail:
  Traceback (most recent call last):

    File "/usr/local/lib/python2.7/dist-packages/wsmeext/pecan.py", line 84, in 
callfunction
  result = f(self, *args, **kwargs)

    File "/opt/stack/new/ironic/ironic/api/controllers/v1/node.py", line 479, 
in provision
  configdrive, topic)

    File "/opt/stack/new/ironic/ironic/conductor/rpcapi.py", line 303, in 
do_node_deploy
  rebuild=rebuild, configdrive=configdrive)

    File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/client.py", 
line 158, in call
  retry=self.retry)

    File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/transport.py", 
line

[Yahoo-eng-team] [Bug 1489159] Re: IronicDriverTestCase unit tests are seg-faulting

2015-10-06 Thread John L. Villalovos 
No response in over a month.  Closing this bug. Feel free to re-open if
desired.

** Changed in: nova
   Status: Confirmed => Invalid

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

Title:
  IronicDriverTestCase unit tests are seg-faulting

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  http://logs.openstack.org/80/148980/28/check/gate-nova-
  python27/f7cb9dd/console.html#_2015-08-25_22_14_53_647

  {3}
  
nova.tests.unit.virt.ironic.test_driver.IronicDriverTestCase.test__unprovision_fail_max_retries
  [] ... inprogress

  This seems to be new(ish).  Someone I work with was saying they were
  hitting it locally too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1489159/+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 1489059] Re: "db type could not be determined" running py34

2015-09-30 Thread John L. Villalovos 
** Also affects: ironic-lib
   Importance: Undecided
   Status: New

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

Title:
  "db type could not be determined" running py34

Status in heat:
  Fix Released
Status in Ironic:
  Fix Released
Status in ironic-lib:
  New
Status in neutron:
  New

Bug description:
  When running tox for the first time, the py34 execution fails with an
  error saying "db type could not be determined".

  This issue is know to be caused when the run of py27 preceeds py34 and
  can be solved erasing the .testrepository and running "tox -e py34"
  first of all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/heat/+bug/1489059/+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 1401121] Re: SimpleCIDRAffinityFilter should accept missing host_ip

2015-08-25 Thread John L. Villalovos 
Marking as WONTFIX as bug submitter hasn't continued with patch.  Feel
free to re-open.

** Changed in: nova
   Status: In Progress = Incomplete

** Changed in: nova
   Status: Incomplete = Won't Fix

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

Title:
  SimpleCIDRAffinityFilter should accept missing host_ip

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  The SimpleCIDRAffinityFilter uses the host_ip value from host_state,
  but the ironic driver doesn't provide this value. Whilst it doesn't
  make sense to use this filter with Ironic nodes, it should be possible
  to have in configured in system configured to use both ironic and a
  virt driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1401121/+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