[Yahoo-eng-team] [Bug 1351892] [NEW] Missing packages on clean environment

2014-08-03 Thread Gary Kotton
Public bug reported:

Perhaps you should add the directory containing `libvirt.pc'

to the PKG_CONFIG_PATH environment variable

No package 'libvirt' found

Package libvirt was not found in the pkg-config search path.

Perhaps you should add the directory containing `libvirt.pc'

to the PKG_CONFIG_PATH environment variable

No package 'libvirt' found

running install

running build

/usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt

Package libvirt was not found in the pkg-config search path.

Perhaps you should add the directory containing `libvirt.pc'

to the PKG_CONFIG_PATH environment variable

No package 'libvirt' found

error: command '/usr/bin/pkg-config' failed with exit status 1


Cleaning up...
Command /home/gkotton/nova/.tox/py27/bin/python2.7 -c import setuptools, 
tokenize;__file__='/home/gkotton/nova/.tox/py27/build/libvirt-python/setup.py';exec(compile(getattr(tokenize,
 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec')) 
install --record /tmp/pip-OvSALh-record/install-record.txt 
--single-version-externally-managed --compile --install-headers 
/home/gkotton/nova/.tox/py27/include/site/python2.7 failed with error code 1 in 
/home/gkotton/nova/.tox/py27/build/libvirt-python
Traceback (most recent call last):
  File ../bin/pip, line 11, in module
sys.exit(main())
  File 
/home/gkotton/nova/.tox/py27/local/lib/python2.7/site-packages/pip/__init__.py,
 line 185, in main
return command.main(cmd_args)
  File 
/home/gkotton/nova/.tox/py27/local/lib/python2.7/site-packages/pip/basecommand.py,
 line 161, in main
text = '\n'.join(complete_log)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 66: 
ordinal not in range(128)

** Affects: nova
 Importance: Medium
 Assignee: Gary Kotton (garyk)
 Status: New

** Changed in: nova
Milestone: None = juno-3

** Changed in: nova
 Assignee: (unassigned) = Gary Kotton (garyk)

** Changed in: nova
   Importance: Undecided = Medium

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

Title:
  Missing packages on clean environment

Status in OpenStack Compute (Nova):
  New

Bug description:
  Perhaps you should add the directory containing `libvirt.pc'

  to the PKG_CONFIG_PATH environment variable

  No package 'libvirt' found

  Package libvirt was not found in the pkg-config search path.

  Perhaps you should add the directory containing `libvirt.pc'

  to the PKG_CONFIG_PATH environment variable

  No package 'libvirt' found

  running install

  running build

  /usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt

  Package libvirt was not found in the pkg-config search path.

  Perhaps you should add the directory containing `libvirt.pc'

  to the PKG_CONFIG_PATH environment variable

  No package 'libvirt' found

  error: command '/usr/bin/pkg-config' failed with exit status 1

  
  Cleaning up...
  Command /home/gkotton/nova/.tox/py27/bin/python2.7 -c import setuptools, 
tokenize;__file__='/home/gkotton/nova/.tox/py27/build/libvirt-python/setup.py';exec(compile(getattr(tokenize,
 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec')) 
install --record /tmp/pip-OvSALh-record/install-record.txt 
--single-version-externally-managed --compile --install-headers 
/home/gkotton/nova/.tox/py27/include/site/python2.7 failed with error code 1 in 
/home/gkotton/nova/.tox/py27/build/libvirt-python
  Traceback (most recent call last):
File ../bin/pip, line 11, in module
  sys.exit(main())
File 
/home/gkotton/nova/.tox/py27/local/lib/python2.7/site-packages/pip/__init__.py,
 line 185, in main
  return command.main(cmd_args)
File 
/home/gkotton/nova/.tox/py27/local/lib/python2.7/site-packages/pip/basecommand.py,
 line 161, in main
  text = '\n'.join(complete_log)
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 66: 
ordinal not in range(128)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1351892/+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 1351892] Re: Missing packages on clean environment

2014-08-03 Thread Gary Kotton
Added in
https://github.com/openstack/nova/commit/21bf0219f66ca9041bc0cf9c29e3a23c054d125c

** Changed in: nova
   Status: New = 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/1351892

Title:
  Missing packages on clean environment

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  Perhaps you should add the directory containing `libvirt.pc'

  to the PKG_CONFIG_PATH environment variable

  No package 'libvirt' found

  Package libvirt was not found in the pkg-config search path.

  Perhaps you should add the directory containing `libvirt.pc'

  to the PKG_CONFIG_PATH environment variable

  No package 'libvirt' found

  running install

  running build

  /usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt

  Package libvirt was not found in the pkg-config search path.

  Perhaps you should add the directory containing `libvirt.pc'

  to the PKG_CONFIG_PATH environment variable

  No package 'libvirt' found

  error: command '/usr/bin/pkg-config' failed with exit status 1

  
  Cleaning up...
  Command /home/gkotton/nova/.tox/py27/bin/python2.7 -c import setuptools, 
tokenize;__file__='/home/gkotton/nova/.tox/py27/build/libvirt-python/setup.py';exec(compile(getattr(tokenize,
 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec')) 
install --record /tmp/pip-OvSALh-record/install-record.txt 
--single-version-externally-managed --compile --install-headers 
/home/gkotton/nova/.tox/py27/include/site/python2.7 failed with error code 1 in 
/home/gkotton/nova/.tox/py27/build/libvirt-python
  Traceback (most recent call last):
File ../bin/pip, line 11, in module
  sys.exit(main())
File 
/home/gkotton/nova/.tox/py27/local/lib/python2.7/site-packages/pip/__init__.py,
 line 185, in main
  return command.main(cmd_args)
File 
/home/gkotton/nova/.tox/py27/local/lib/python2.7/site-packages/pip/basecommand.py,
 line 161, in main
  text = '\n'.join(complete_log)
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 66: 
ordinal not in range(128)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1351892/+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 1284677] Re: Python 3: do not use 'unicode()'

2014-08-03 Thread Valeriy Ponomaryov
** Changed in: manila
   Status: In Progress = Fix Committed

** Changed in: manila
   Status: Fix Committed = Fix Released

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

Title:
  Python 3: do not use 'unicode()'

Status in OpenStack Image Registry and Delivery Service (Glance):
  Fix Released
Status in Manila:
  Fix Released
Status in Python client library for Glance:
  Fix Committed
Status in Tuskar:
  Fix Released

Bug description:
  The unicode() function is Python2-specific, we should use
  six.text_type() instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1284677/+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 1351960] [NEW] cloud-init.log inconsistent date format

2014-08-03 Thread Darik Horn
Public bug reported:

The first field of the /var/log/cloud-init.log file alternates between
ISO and local date formats.  In the attached example, the change happens
at:

2014-08-03 01:45:53,472 - util.py[DEBUG]: Read 12 bytes from 
/proc/uptime
2014-08-03 01:45:53,472 - util.py[DEBUG]: cloud-init mode 'init' took 
12.704 seconds (12.71)
Aug  3 01:45:56 test209 [CLOUDINIT] util.py[DEBUG]: Cloud-init v. 0.7.5 
running 'modules:config' at Sun, 03 Aug 2014 01:45:56 +. Up 94.33 seconds.
Aug  3 01:45:56 test209 [CLOUDINIT] importer.py[DEBUG]: Looking for 
modules ['cc_emit_upstart', 'cloudinit.config.cc_emit_upstart'] that have 
attributes ['handle']

Expected behavior is consistency in the date format.

** Affects: cloud-init
 Importance: Undecided
 Status: New

** Attachment added: cloud-init.log
   
https://bugs.launchpad.net/bugs/1351960/+attachment/4168766/+files/cloud-init.log

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

Title:
  cloud-init.log inconsistent date format

Status in Init scripts for use on cloud images:
  New

Bug description:
  The first field of the /var/log/cloud-init.log file alternates between
  ISO and local date formats.  In the attached example, the change
  happens at:

2014-08-03 01:45:53,472 - util.py[DEBUG]: Read 12 bytes from 
/proc/uptime
2014-08-03 01:45:53,472 - util.py[DEBUG]: cloud-init mode 'init' took 
12.704 seconds (12.71)
Aug  3 01:45:56 test209 [CLOUDINIT] util.py[DEBUG]: Cloud-init v. 0.7.5 
running 'modules:config' at Sun, 03 Aug 2014 01:45:56 +. Up 94.33 seconds.
Aug  3 01:45:56 test209 [CLOUDINIT] importer.py[DEBUG]: Looking for 
modules ['cc_emit_upstart', 'cloudinit.config.cc_emit_upstart'] that have 
attributes ['handle']

  Expected behavior is consistency in the date format.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1351960/+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 1351973] [NEW] re-raising exceptions in a non-compatible way with Python 3

2014-08-03 Thread Felipe Reyes
Public bug reported:

Horizon's source code is re-raising exceptions using the deprecated
syntax `raise exc_type, exc_value, exc_traceback`, to make the source
code compatible with Python 2 and Python 3, Horizon should user
`six.reraise()`.

** Affects: horizon
 Importance: Undecided
 Assignee: Felipe Reyes (freyes)
 Status: New

** Changed in: horizon
 Assignee: (unassigned) = Felipe Reyes (freyes)

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

Title:
  re-raising exceptions in a non-compatible way with Python 3

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Horizon's source code is re-raising exceptions using the deprecated
  syntax `raise exc_type, exc_value, exc_traceback`, to make the source
  code compatible with Python 2 and Python 3, Horizon should user
  `six.reraise()`.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1351973/+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 1352102] [NEW] users are unable to create ports on provider networks

2014-08-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

after commit da66d50010d5b1ba1d7fc9c3d59d81b6c01bb0b0 my users are
unable to boot vm attached to provider networks, this is a serious
regression for me as we mostly use provider networks.

bug which originated the commit
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1284718

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: in-stable-havana in-stable-icehouse regression-release
-- 
users are unable to create ports on provider networks
https://bugs.launchpad.net/bugs/1352102
You received this bug notification because you are a member of Yahoo! 
Engineering Team, which is subscribed to OpenStack Compute (nova).

-- 
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 1352102] [NEW] users are unable to create ports on provider networks

2014-08-03 Thread gustavo panizzo
Public bug reported:

after commit da66d50010d5b1ba1d7fc9c3d59d81b6c01bb0b0 my users are
unable to boot vm attached to provider networks, this is a serious
regression for me as we mostly use provider networks.

bug which originated the commit
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1284718

** Affects: nova
 Importance: Undecided
 Status: New


** Tags: in-stable-havana in-stable-icehouse regression-release

** Package changed: nova (Ubuntu) = nova

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

Title:
  users are unable to create ports on provider networks

Status in OpenStack Compute (Nova):
  New

Bug description:
  after commit da66d50010d5b1ba1d7fc9c3d59d81b6c01bb0b0 my users are
  unable to boot vm attached to provider networks, this is a serious
  regression for me as we mostly use provider networks.

  bug which originated the commit
  https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1284718

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1352102/+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 1352105] [NEW] can not get network info from metadata server

2014-08-03 Thread lvdongbing
Public bug reported:

I want to use cloudinit to get the network info and write it into the network 
configuration file,
but it failed because cloudinit didn't get the network info.
In the vm, I used curl to test the metadata as below
#curl http://169.254.169.254/openstack/latest/meta_data.json
the reponse info didn't contain network info.
See following code in nova/virt/netutils.py
if subnet_v4:
if subnet_v4.get_meta('dhcp_server') is not None:
continue
It seems that when vm use  neutron dhcp, network info will be ignored in 
meta_data.json

** 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/1352105

Title:
  can not get network info from metadata server

Status in OpenStack Compute (Nova):
  New

Bug description:
  I want to use cloudinit to get the network info and write it into the network 
configuration file,
  but it failed because cloudinit didn't get the network info.
  In the vm, I used curl to test the metadata as below
  #curl http://169.254.169.254/openstack/latest/meta_data.json
  the reponse info didn't contain network info.
  See following code in nova/virt/netutils.py
  if subnet_v4:
  if subnet_v4.get_meta('dhcp_server') is not None:
  continue
  It seems that when vm use  neutron dhcp, network info will be ignored in 
meta_data.json

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1352105/+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 1352115] [NEW] stop spamming cadf event authn messages in log

2014-08-03 Thread Steve Martinelli
Public bug reported:

In keystone we currently log cadf events in the log, twice for every authN. 
Once for pending and once for success/failure.
This is unnecessary since the notification_driver option in keystone.conf can 
have multiple values, one of them being log.

** Affects: keystone
 Importance: Undecided
 Assignee: Steve Martinelli (stevemar)
 Status: In Progress

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

Title:
  stop spamming cadf event authn messages in log

Status in OpenStack Identity (Keystone):
  In Progress

Bug description:
  In keystone we currently log cadf events in the log, twice for every authN. 
Once for pending and once for success/failure.
  This is unnecessary since the notification_driver option in keystone.conf can 
have multiple values, one of them being log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1352115/+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 1352134] [NEW] /bin/pip: No such file or directory in pep8 and cover jobs

2014-08-03 Thread Joe Gordon
Public bug reported:

https://review.openstack.org/#/c/75284/  changed pep8's envdir to venv.
But this breaks the assumptions made by infra for all pep8 jobs.

http://git.openstack.org/cgit/openstack-
infra/config/tree/modules/openstack_project/files/slave_scripts/run-
pep8.sh#n23

** Affects: keystone
 Importance: Undecided
 Status: New

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

Title:
  /bin/pip: No such file or directory in pep8 and cover jobs

Status in OpenStack Identity (Keystone):
  New

Bug description:
  https://review.openstack.org/#/c/75284/  changed pep8's envdir to
  venv. But this breaks the assumptions made by infra for all pep8 jobs.

  http://git.openstack.org/cgit/openstack-
  infra/config/tree/modules/openstack_project/files/slave_scripts/run-
  pep8.sh#n23

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1352134/+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 1352141] [NEW] uncaught exception in floating ip creation when pool is not found with neutron backend

2014-08-03 Thread Christopher Yeoh
Public bug reported:

2014-07-31 07:14:07.574 ERROR nova.api.openstack 
[req-98b42d5d-575f-4209-b711-4cb2ae8ef14e FloatingIPsNegativeTestXML-1138647745 
FloatingIPsNegativeTestXML-1764448859] Caught error: Floating ip pool not found.
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack Traceback (most recent 
call last):
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/opt/stack/new/nova/nova/api/openstack/__init__.py, line 125, in __call__
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack return 
req.get_response(self.application)
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/usr/local/lib/python2.7/dist-packages/webob/request.py, line 1320, in send
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack application, 
catch_exc_info=False)
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/usr/local/lib/python2.7/dist-packages/webob/request.py, line 1284, in 
call_application
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack app_iter = 
application(self.environ, start_response)
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/usr/local/lib/python2.7/dist-packages/webob/dec.py, line 144, in __call__
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack return resp(environ, 
start_response)
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/opt/stack/new/python-keystoneclient/keystoneclient/middleware/auth_token.py, 
line 663, in __call__
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack return self.app(env, 
start_response)
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/usr/local/lib/python2.7/dist-packages/webob/dec.py, line 144, in __call__
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack return resp(environ, 
start_response)
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/usr/local/lib/python2.7/dist-packages/webob/dec.py, line 144, in __call__
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack return resp(environ, 
start_response)
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/usr/lib/python2.7/dist-packages/routes/middleware.py, line 131, in __call__
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack response = 
self.app(environ, start_response)
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/usr/local/lib/python2.7/dist-packages/webob/dec.py, line 144, in __call__
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack return resp(environ, 
start_response)
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/usr/local/lib/python2.7/dist-packages/webob/dec.py, line 130, in __call__
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack resp = 
self.call_func(req, *args, **self.kwargs)
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/usr/local/lib/python2.7/dist-packages/webob/dec.py, line 195, in call_func
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack return 
self.func(req, *args, **kwargs)
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/opt/stack/new/nova/nova/api/openstack/wsgi.py, line 917, in __call__
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack content_type, body, 
accept)
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/opt/stack/new/nova/nova/api/openstack/wsgi.py, line 983, in _process_stack
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack action_result = 
self.dispatch(meth, request, action_args)
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/opt/stack/new/nova/nova/api/openstack/wsgi.py, line 1070, in dispatch
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack return 
method(req=request, **action_args)
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/opt/stack/new/nova/nova/api/openstack/compute/contrib/floating_ips.py, line 
158, in create
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack address = 
self.network_api.allocate_floating_ip(context, pool)
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/opt/stack/new/nova/nova/network/neutronv2/api.py, line 927, in 
allocate_floating_ip
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/opt/stack/new/nova/nova/network/neutronv2/api.py, line 927, in 
allocate_floating_ip
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack pool_id = 
self._get_floating_ip_pool_id_by_name_or_id(client, pool)
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack   File 
/opt/stack/new/nova/nova/network/neutronv2/api.py, line 917, in 
_get_floating_ip_pool_id_by_name_or_id
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack raise 
exception.FloatingIpPoolNotFound()
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack FloatingIpPoolNotFound: 
Floating ip pool not found.
2014-07-31 07:14:07.574 28614 TRACE nova.api.openstack 

http://logs.openstack.org/72/109872/1/check/check-tempest-dsvm-neutron-
full/7e11304/logs/screen-n-api.txt.gz?

** Affects: nova
 Importance: Low
   

[Yahoo-eng-team] [Bug 1352140] [NEW] do not show loading image for shelved offloaded status

2014-08-03 Thread Masco Kaliyamoorthy
Public bug reported:

When we shelve an instance via CLI,
in horizon instance table, the 'loading' image is continuously showing in the 
status column.

This bug is already reported and fixed in bug #1318558 but it is not fixed 
properly.
for rescue it is working fine but not for shelved offloaded.

** Affects: horizon
 Importance: Undecided
 Assignee: Masco Kaliyamoorthy (masco)
 Status: In Progress

** Changed in: horizon
   Status: New = In Progress

** Changed in: horizon
 Assignee: (unassigned) = Masco Kaliyamoorthy (masco)

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

Title:
  do not show loading image for shelved offloaded status

Status in OpenStack Dashboard (Horizon):
  In Progress

Bug description:
  When we shelve an instance via CLI,
  in horizon instance table, the 'loading' image is continuously showing in the 
status column.

  This bug is already reported and fixed in bug #1318558 but it is not fixed 
properly.
  for rescue it is working fine but not for shelved offloaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1352140/+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 1352144] [NEW] API client object like novaclient is created every time openstack_dashboard/api methods are called

2014-08-03 Thread Akihiro Motoki
Public bug reported:

In API modules in openstack_dashboard api such as novaclient, neutronclient and 
so on, API client objects (novaclient, neutronclient...) are created every time 
openstack_dashboard/api methods are called even in a same request.
Recreating API client object leads to recreating API HTTP connections.

In a same request, API client object should be reused as possible as we
can to reduce the number of connections to backend servers.

Note that keystoneclient in openstack_dashboard/api is the only module
which implements the client object caching.[1]

[1]
http://git.openstack.org/cgit/openstack/horizon/tree/openstack_dashboard/api/keystone.py#n121

** Affects: horizon
 Importance: High
 Assignee: Akihiro Motoki (amotoki)
 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/1352144

Title:
  API client object like novaclient is created every time
  openstack_dashboard/api methods are called

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  In API modules in openstack_dashboard api such as novaclient, neutronclient 
and so on, API client objects (novaclient, neutronclient...) are created every 
time openstack_dashboard/api methods are called even in a same request.
  Recreating API client object leads to recreating API HTTP connections.

  In a same request, API client object should be reused as possible as
  we can to reduce the number of connections to backend servers.

  Note that keystoneclient in openstack_dashboard/api is the only module
  which implements the client object caching.[1]

  [1]
  
http://git.openstack.org/cgit/openstack/horizon/tree/openstack_dashboard/api/keystone.py#n121

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