[Yahoo-eng-team] [Bug 1222727] Re: camel-style issue in limites v3 api
Used limits will be removed in icehouse as will most if not of all of limits (there are a couple of changesets already in the queue doing this). ** Changed in: nova Status: New = 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/1222727 Title: camel-style issue in limites v3 api Status in OpenStack Compute (Nova): Won't Fix Bug description: there is camel-style issue havn't been clean in limits v3 api. in file nova/api/openstack/compute/plugins/v3/used_limits.py and nova/api/openstack/compute/views/limits.py there is camel-style code used by limits v3 api. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1222727/+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 1220773] Re: Nova command 'nova list' ( also, image-list, nova secgroup-add-rule, etc) fails and the system hangs
From the logs it looks like you have some authentication issues with
your setup which probably explains the very long timeout.
** 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/1220773
Title:
Nova command 'nova list' ( also, image-list, nova secgroup-add-rule,
etc) fails and the system hangs
Status in OpenStack Compute (Nova):
Invalid
Bug description:
I installed the openstack Grizzly in a single node. Every thing went
alright. But, When I execute the nova list, the system hangs and
then I press Ctl-C, and the following message is shown on the display.
I think, the root is he long time to start http connection (around
255 sec).
nova list
INFO (connectionpool:191) Starting new HTTP connection (1): 1XX.56.XX.X
^CTraceback (most recent call last):
File /usr/bin/nova, line 9, in module
load_entry_point('python-novaclient==2.13.0', 'console_scripts', 'nova')()
File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 765, in
main
OpenStackComputeShell().main(map(strutils.safe_decode, sys.argv[1:]))
File /usr/lib/python2.7/dist-packages/novaclient/shell.py, line 701, in
main
args.func(self.cs, args)
File /usr/lib/python2.7/dist-packages/novaclient/v1_1/shell.py, line 937,
in do_list
servers = cs.servers.list(search_opts=search_opts)
File /usr/lib/python2.7/dist-packages/novaclient/v1_1/servers.py, line
375, in list
return self._list(/servers%s%s % (detail, query_string), servers)
File /usr/lib/python2.7/dist-packages/novaclient/base.py, line 62, in
_list
_resp, body = self.api.client.get(url)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 230, in
get
return self._cs_request(url, 'GET', **kwargs)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 217, in
_cs_request
**kwargs)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 199, in
_time_request
resp, body = self.request(url, method, **kwargs)
File /usr/lib/python2.7/dist-packages/novaclient/client.py, line 170, in
request
**kwargs)
File /usr/lib/python2.7/dist-packages/requests/api.py, line 44, in request
return session.request(method=method, url=url, **kwargs)
File /usr/lib/python2.7/dist-packages/requests/sessions.py, line 354, in
request
resp = self.send(prep, **send_kwargs)
File /usr/lib/python2.7/dist-packages/requests/sessions.py, line 460, in
send
r = adapter.send(request, **kwargs)
File /usr/lib/python2.7/dist-packages/requests/adapters.py, line 211, in
send
timeout=timeout
File /usr/lib/python2.7/dist-packages/urllib3/connectionpool.py, line
415, in urlopen
body=body, headers=headers)
File /usr/lib/python2.7/dist-packages/urllib3/connectionpool.py, line
275, in _make_request
httplib_response = conn.getresponse(buffering=True)
File /usr/lib/python2.7/httplib.py, line 1030, in getresponse
response.begin()
File /usr/lib/python2.7/httplib.py, line 407, in begin
version, status, reason = self._read_status()
File /usr/lib/python2.7/httplib.py, line 365, in _read_status
line = self.fp.readline()
File /usr/lib/python2.7/socket.py, line 447, in readline
data = self._sock.recv(self._rbufsize)
KeyboardInterrupt
Here is the last three log entries from the /var/log/nova/nova-
api.log. The http connection time is ~255, which is very large. I have
not yet created any VM, as I could not execute nova image-list,
secgroup-add-rule, etc.
2013-09-04 06:14:24.173 31946 INFO nova.osapi_compute.wsgi.server [-]
(31946) accepted ('1XX.56.XX.X', 41687)
2013-09-04 06:15:13.868 31946 INFO nova.osapi_compute.wsgi.server [-]
1XX.56.XX.X GET /v2/e4e613863a214020935c7aabe44ba7ce/os-tenant-
networks HTTP/1.1 status: 401 len: 465 time: 255.9475789
2013-09-04 06:16:17.996 31946 INFO nova.osapi_compute.wsgi.server [-]
1XX.56.XX.X GET /v2/e4e613863a214020935c7aabe44ba7ce/os-security-
groups HTTP/1.1 status: 401 len: 465 time: 256.0612741
Here I should note down that there are three instances of nova-api
process running in my computer. The openstack is a single-node
installation.
Please help.
Thank you very much,
Abhi
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1220773/+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 1224286] Re: I18n: Untranslated message Displaying X items is showed
Yeah. It works after I updated the po files. Before testing, I had thought I have pulled down the latest transaltions, yet the djangojs.po is not ignored because the Transifex regards the file in my local machine as newer version than the file in Transifex server. Sorry I didn't check the po file carefully. I will mark it as invalid. ** Changed in: horizon Status: Incomplete = Invalid -- 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/1224286 Title: I18n: Untranslated message Displaying X items is showed Status in OpenStack Dashboard (Horizon): Invalid Bug description: At the end of a table, there is a message to show the listed item number: Displaying X items. After changing language setting to other langauge, still the English version of this message is showed. Every table has the same issue. For example, the instance table, the volume table, the image table, the role table, and so on. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1224286/+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 1224393] [NEW] Heat Dashboard: Could not delete multiple stacks at once.
You have been subscribed to a public bug: When user selects two or more stacks, and hit button Delete Stacks, only first stack in deleted ** Affects: horizon Importance: Undecided Status: New -- Heat Dashboard: Could not delete multiple stacks at once. https://bugs.launchpad.net/bugs/1224393 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). -- 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 1224289] Re: I18n: Untranslated message is showed in the action confirm dialog
Right. Cancel in modal.js needs to be in a gettext(). https://github.com/openstack/horizon/blob/master/horizon/static/horizon/js/horizon.modals.js#L33 ** Changed in: horizon Status: Incomplete = Opinion ** Changed in: horizon Status: Opinion = Triaged -- 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/1224289 Title: I18n: Untranslated message is showed in the action confirm dialog Status in OpenStack Dashboard (Horizon): Triaged Bug description: In a table, when I select an action, there is an action confirm dialog promoted. The messages showed in the confirm dialog are untranslated. For example, in the instance list, select Terminate Instance, the dialog will be promoted with untranslated messages. The action name is showed as translated. Yet other messages like Confirm action name You have selected test1. Please confirm your selection. This action cannot be undone. and the button Cancel are not translated, still in English. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1224289/+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 1224342] Re: I18n: the tips in the filter input control and the text input control are not translated
These strings are defined in the djangojs.po file (Javascript strings), I think it's the same issue with using an outdated file as in bug 1224286. ** Changed in: horizon Status: New = Invalid -- 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/1224342 Title: I18n: the tips in the filter input control and the text input control are not translated Status in OpenStack Dashboard (Horizon): Invalid Bug description: There are several filter input controls and text input controls in the UI, and there are tips in these controls. For example, in a filter control, there is a word Filter. In the text input control, there are some words Additional information here These tips are not internationalized, still displayed in English. For example, there is a filter input control at the top of instance table and voume table. In the Volume page, click the button create volume at the right top corner, there will be a form Create volume promoted. The second text input control in this form has a tip Additional information here To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1224342/+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 1167421] Re: Upgrading from folsom to grizzly results in all tenants/users being disabled
** Changed in: cloud-archive Status: New = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1167421 Title: Upgrading from folsom to grizzly results in all tenants/users being disabled Status in Ubuntu Cloud Archive: Fix Released Status in OpenStack Identity (Keystone): Fix Released Status in Keystone grizzly series: Fix Released Status in “keystone” package in Ubuntu: Fix Released Bug description: Hi there, I tested a Folsom to Grizzly upgrade using stock packages on Ubuntu 12.04 and noticed that upon completion of the upgrade that there was a new 'enabled' column in `user`/ `project` tables and that all records within these tables had enabled set to 0. This resulted in authentication failure on users which were working prior to the upgrade. Once I ran the following, users could authenticate again: # mysql keystone -e update user set enabled=1 # mysql keystone -e update project set enabled=1 For anyone else reading this, I knew all my users/tenants were enabled so didn't have to worry about the above statements, however in some environments there are likely to be disabled users/tenants which you'd need to take note of. You can determine this by looking at the text in the `extra` column within these two tables. -Matt To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1167421/+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 1220937] Re: with_venv.sh should enclose command args
** Changed in: trove Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1220937 Title: with_venv.sh should enclose command args Status in OpenStack Image Registry and Delivery Service (Glance): In Progress Status in Orchestration API (Heat): Fix Committed Status in OpenStack Dashboard (Horizon): Fix Committed Status in OpenStack Identity (Keystone): In Progress Status in OpenStack Neutron (virtual network service): Fix Committed Status in Trove - Database as a Service: Fix Released Bug description: $ tools/with_venv.sh neutron --os-username admin 1 net-show net 1 Unknown command [u'1', u'net-show', u'net', u'1'] after enclose command in with_venv.sh $ tools/with_venv.sh neutron --os-username admin 1 net-show net 1 You must provide a password via either --os-password or env[OS_PASSWORD] To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1220937/+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 1223568] Re: pep8 requirements failing
Closing this as this has resolved itself. This issue was mostly related
to an upstream library.
** Changed in: neutron
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/1223568
Title:
pep8 requirements failing
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
Requirements seem to be failing on version check for six
2013-09-10 20:24:53.377 | using tox.ini:
/home/jenkins/workspace/gate-neutron-pep8/tox.ini
2013-09-10 20:24:53.377 | using tox-1.6.1 from
/usr/local/lib/python2.7/dist-packages/tox/__init__.pyc
2013-09-10 20:24:53.378 | GLOB sdist-make:
/home/jenkins/workspace/gate-neutron-pep8/setup.py
2013-09-10 20:24:53.388 | /home/jenkins/workspace/gate-neutron-pep8$
/usr/bin/python /home/jenkins/workspace/gate-neutron-pep8/setup.py sdist
--formats=zip --dist-dir /home/jenkins/workspace/gate-neutron-pep8/.tox/dist
/home/jenkins/workspace/gate-neutron-pep8/.tox/log/tox-0.log
2013-09-10 20:24:56.957 | pep8 create:
/home/jenkins/workspace/gate-neutron-pep8/.tox/pep8
2013-09-10 20:24:56.968 | /home/jenkins/workspace/gate-neutron-pep8/.tox$
/usr/bin/python /usr/local/lib/python2.7/dist-packages/virtualenv.py
--setuptools --python /usr/bin/python pep8
/home/jenkins/workspace/gate-neutron-pep8/.tox/pep8/log/pep8-0.log
2013-09-10 20:24:58.578 | pep8 installdeps:
-r/home/jenkins/workspace/gate-neutron-pep8/requirements.txt,
-r/home/jenkins/workspace/gate-neutron-pep8/test-requirements.txt,
setuptools_git=0.4
2013-09-10 20:24:58.586 | /home/jenkins/workspace/gate-neutron-pep8$
/home/jenkins/workspace/gate-neutron-pep8/.tox/pep8/bin/pip install --pre
-r/home/jenkins/workspace/gate-neutron-pep8/requirements.txt
-r/home/jenkins/workspace/gate-neutron-pep8/test-requirements.txt
setuptools_git=0.4
/home/jenkins/workspace/gate-neutron-pep8/.tox/pep8/log/pep8-1.log
2013-09-10 20:25:52.038 | pep8 inst:
/home/jenkins/workspace/gate-neutron-pep8/.tox/dist/neutron-2013.2.a552.gaa68a3d.zip
2013-09-10 20:25:52.058 | /home/jenkins/workspace/gate-neutron-pep8$
/home/jenkins/workspace/gate-neutron-pep8/.tox/pep8/bin/pip install --pre
/home/jenkins/workspace/gate-neutron-pep8/.tox/dist/neutron-2013.2.a552.gaa68a3d.zip
/home/jenkins/workspace/gate-neutron-pep8/.tox/pep8/log/pep8-2.log
2013-09-10 20:25:57.902 | pep8 runtests: commands[0] | flake8
2013-09-10 20:25:57.907 | /home/jenkins/workspace/gate-neutron-pep8$
/home/jenkins/workspace/gate-neutron-pep8/.tox/pep8/bin/flake8
2013-09-10 20:25:58.112 | Traceback (most recent call last):
2013-09-10 20:25:58.112 | File .tox/pep8/bin/flake8, line 9, in module
2013-09-10 20:25:58.112 | load_entry_point('flake8==2.0',
'console_scripts', 'flake8')()
2013-09-10 20:25:58.112 | File
/home/jenkins/workspace/gate-neutron-pep8/.tox/pep8/local/lib/python2.7/site-packages/flake8/main.py,
line 21, in main
2013-09-10 20:25:58.113 | flake8_style = get_style_guide(parse_argv=True,
config_file=DEFAULT_CONFIG)
2013-09-10 20:25:58.113 | File
/home/jenkins/workspace/gate-neutron-pep8/.tox/pep8/local/lib/python2.7/site-packages/flake8/engine.py,
line 75, in get_style_guide
2013-09-10 20:25:58.114 | kwargs['parser'], options_hooks = get_parser()
2013-09-10 20:25:58.114 | File
/home/jenkins/workspace/gate-neutron-pep8/.tox/pep8/local/lib/python2.7/site-packages/flake8/engine.py,
line 38, in get_parser
2013-09-10 20:25:58.114 | (extensions, parser_hooks, options_hooks) =
_register_extensions()
2013-09-10 20:25:58.115 | File
/home/jenkins/workspace/gate-neutron-pep8/.tox/pep8/local/lib/python2.7/site-packages/flake8/engine.py,
line 24, in _register_extensions
2013-09-10 20:25:58.115 | checker = entry.load()
2013-09-10 20:25:58.115 | File
/home/jenkins/workspace/gate-neutron-pep8/.tox/pep8/local/lib/python2.7/site-packages/pkg_resources.py,
line 2259, in load
2013-09-10 20:25:58.116 | if require: self.require(env, installer)
2013-09-10 20:25:58.116 | File
/home/jenkins/workspace/gate-neutron-pep8/.tox/pep8/local/lib/python2.7/site-packages/pkg_resources.py,
line 2272, in require
2013-09-10 20:25:58.117 |
working_set.resolve(self.dist.requires(self.extras),env,installer)))
2013-09-10 20:25:58.117 | File
/home/jenkins/workspace/gate-neutron-pep8/.tox/pep8/local/lib/python2.7/site-packages/pkg_resources.py,
line 630, in resolve
2013-09-10 20:25:58.118 | raise VersionConflict(dist,req) # XXX put more
info here
2013-09-10 20:25:58.119 | pkg_resources.VersionConflict: (six 1.4.1
(/home/jenkins/workspace/gate-neutron-pep8/.tox/pep8/lib/python2.7/site-packages),
Requirement.parse('six1.4.0'))
2013-09-10 20:25:58.131 | ERROR: InvocationError:
'/home/jenkins/workspace/gate-neutron-pep8/.tox/pep8/bin/flake8'
To manage notifications about this bug go to:
[Yahoo-eng-team] [Bug 1223927] Re: port-create does not respect the ip_adress chosen
This is not an issue, but a typo issue : ip_adress is not a valid
parameter name
quantum port-create --tenant-id 202d25dd32a54d418d59f6b01210f58d --name
new_port --fixed-ip subnet_id=75a2af5e-575f-4fec-
86f0-41b62b77e140,ip_address=10.0.0.15 --device-
id=11ed9c99-1426-4654-b3d3-40c731f88d64 prov_int1
** Changed in: neutron
Assignee: (unassigned) = Nicolas PLANEL (nicolas-planel)
** Changed in: neutron
Status: New = 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/1223927
Title:
port-create does not respect the ip_adress chosen
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
As you can see in the example below, the ip_address desired was
10.0.0.15 but the port was created using the next available IP from
the allocation pool of that subnet:
quantum port-create --tenant-id 202d25dd32a54d418d59f6b01210f58d --name
new_port --fixed-ip
subnet_id=75a2af5e-575f-4fec-86f0-41b62b77e140,ip_adress=10.0.0.15
--device-id=11ed9c99-1426-4654-b3d3-40c731f88d64 prov_int1
Created a new port:
+-+---+
| Field | Value
|
+-+---+
| admin_state_up | True
|
| device_id | 11ed9c99-1426-4654-b3d3-40c731f88d64
|
| device_owner|
|
| fixed_ips | {subnet_id: 75a2af5e-575f-4fec-86f0-41b62b77e140,
ip_address: 10.0.0.104} |
| id | 3a5c97a4-b745-4896-ac3b-10568ad52c3a
|
| mac_address | fa:16:3e:15:67:99
|
| name| new_port
|
| network_id | 3a2b8f6e-811c-4957-896d-c645d7200410
|
| security_groups | ceca0ff6-a801-4f02-9649-61452e03becd
|
| status | DOWN
|
| tenant_id | 202d25dd32a54d418d59f6b01210f58d
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1223927/+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 1178586] Re: scheduling failures leave baremetal instances stuck in BUILDING
*** This bug is a duplicate of bug 1182056 *** https://bugs.launchpad.net/bugs/1182056 ** This bug has been marked a duplicate of bug 1182056 Failed VM's not set to error state on exception -- 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/1178586 Title: scheduling failures leave baremetal instances stuck in BUILDING Status in OpenStack Compute (Nova): Confirmed Bug description: This might not be baremetal specific - dunno. after ] /var/log/upstart/nova-scheduler.log:2013-05-10 09:10:10,911.911 14196 WARNING nova.scheduler.manager [req-1a8b0d73-253b-4999-aeca-00555a4d2e83 87b44714e906420a9e6a07f6835b5b61 c30643483cd849a6b61e98c6ccc03a66] Failed to schedule_run_instance: No valid host was found. Exceeded max scheduling attempts 3 for instance 6b566d0c-320d-4bed-bc7e-ad0ba725925d the following is shown in nova list: | 6b566d0c-320d-4bed-bc7e-ad0ba725925d | test-6b566d0c-320d-4bed-bc7e- ad0ba725925d | BUILD | scheduling | NOSTATE full log: http://paste.ubuntu.com/5650528/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1178586/+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
