[Yahoo-eng-team] [Bug 1278342] [NEW] novncproxy accepts un-masked client websocket frames
Public bug reported: using Havana nova with python-websockify-0.5.1 I found that the server is not picky enough. It accepts WebSocket frames with the masked-bit unset though the relevant standard https://tools.ietf.org/html/rfc6455#section-5.1 says The server MUST close the connection upon receiving a frame that is not masked. For testing this behaviour, you can use my code without this fix https://github.com/bmwiedemann/connectionproxy/commit/1ece2024090cfbacc003f66c036c2fe550fd488a it is used like this: git clone https://github.com/bmwiedemann/connectionproxy.git $INSTALL perl-Protocol-WebSocket nova get-vnc-console $YOURINSTANCE novnc perl wsconnectionproxy.pl --port 5942 --to http://cloud.example.com:6080/vnc_auto.html?token=xxx gvncviewer localhost:42 ** 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/1278342 Title: novncproxy accepts un-masked client websocket frames Status in OpenStack Compute (Nova): New Bug description: using Havana nova with python-websockify-0.5.1 I found that the server is not picky enough. It accepts WebSocket frames with the masked-bit unset though the relevant standard https://tools.ietf.org/html/rfc6455#section-5.1 says The server MUST close the connection upon receiving a frame that is not masked. For testing this behaviour, you can use my code without this fix https://github.com/bmwiedemann/connectionproxy/commit/1ece2024090cfbacc003f66c036c2fe550fd488a it is used like this: git clone https://github.com/bmwiedemann/connectionproxy.git $INSTALL perl-Protocol-WebSocket nova get-vnc-console $YOURINSTANCE novnc perl wsconnectionproxy.pl --port 5942 --to http://cloud.example.com:6080/vnc_auto.html?token=xxx gvncviewer localhost:42 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1278342/+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 1278348] [NEW] Typo Duration of volune
Public bug reported: hi :) Horizon Typo. http://git.openstack.org/cgit/openstack/horizon/tree/openstack_dashboard/api/ceilometer.py#n1106 Duration of volune Duration of volume Thanks, Sungjin Kang. ** Affects: horizon Importance: Undecided Status: New ** Tags: string -- 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/1278348 Title: Typo Duration of volune Status in OpenStack Dashboard (Horizon): New Bug description: hi :) Horizon Typo. http://git.openstack.org/cgit/openstack/horizon/tree/openstack_dashboard/api/ceilometer.py#n1106 Duration of volune Duration of volume Thanks, Sungjin Kang. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1278348/+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 1278349] [NEW] nec plugin deletes and recreate a OFC port unexpectedly when update_port from dhcp-agent.
Public bug reported: nec plugin deletes and recreate a OFC port unexpectedly when update_port from dhcp-agent even though there is no actual changes in OpenFlow port information (datapath_id and port number). It is caused by normalization of datapath_id is different between when plugin.update_port is called and when portinfo upadte is notified from nec-plugin-agent. As a result, nec-plugin will mis-recognize datapath_id is changed and recreate a port on OpenFlow controller. This leads to unexpected temporary outage of a dhcp port. The same normalization method should be used for both case. ** Affects: neutron Importance: Medium Assignee: Akihiro Motoki (amotoki) Status: New ** Tags: nec -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1278349 Title: nec plugin deletes and recreate a OFC port unexpectedly when update_port from dhcp-agent. Status in OpenStack Neutron (virtual network service): New Bug description: nec plugin deletes and recreate a OFC port unexpectedly when update_port from dhcp-agent even though there is no actual changes in OpenFlow port information (datapath_id and port number). It is caused by normalization of datapath_id is different between when plugin.update_port is called and when portinfo upadte is notified from nec-plugin-agent. As a result, nec-plugin will mis-recognize datapath_id is changed and recreate a port on OpenFlow controller. This leads to unexpected temporary outage of a dhcp port. The same normalization method should be used for both case. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1278349/+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 1278353] [NEW] a failed modification of project quota shows an error success at the same time
Public bug reported: the admin user try to edit the quota setting of a project: changing the amount of instances from 10 to 4 when there are 5 instances active. The dashboard show an error balloon that says that it was unable to change the quotas the a success balloon beneath it saying success modified project. If there was an error the success balloon should not appear. ** Affects: horizon Importance: Undecided Status: New ** Tags: horizon -- 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/1278353 Title: a failed modification of project quota shows an error success at the same time Status in OpenStack Dashboard (Horizon): New Bug description: the admin user try to edit the quota setting of a project: changing the amount of instances from 10 to 4 when there are 5 instances active. The dashboard show an error balloon that says that it was unable to change the quotas the a success balloon beneath it saying success modified project. If there was an error the success balloon should not appear. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1278353/+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 1260118] Re: VNC on compute node refused connection from controller
** 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/1260118 Title: VNC on compute node refused connection from controller Status in OpenStack Dashboard (Horizon): New Status in OpenStack Compute (Nova): New Bug description: Nova-novncproxy threw this error when trying to connect to the VM's console via VNC. The root cause was found to be at the compute node (10.52.224.20) which dropped network connection on vnc-server port(s) (i.e. 5900+N) from the controller node. 22: connecting to: 10.52.224.20:5903 22: handler exception: [Errno 113] EHOSTUNREACH A temp work-around is to manually open up vnc ports on compute node(s). -A INPUT -m state --state NEW -m tcp -p tcp --dport 5900:5950 -j ACCEPT Wondering if this could be addressed dynamically, during VM creation ideally. The issue was found with openstack-nova-compute-2013.2-2.el6 running on CentOS kernel 2.6.32-358.123.2.openstack.el6.x86_64. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1260118/+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 1260118] Re: VNC on compute node refused connection from controller
I don't think this is related to Horizon - we simply get the URL from Nova and embed it in the page. ** 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 Compute (nova). https://bugs.launchpad.net/bugs/1260118 Title: VNC on compute node refused connection from controller Status in OpenStack Dashboard (Horizon): Invalid Status in OpenStack Compute (Nova): New Bug description: Nova-novncproxy threw this error when trying to connect to the VM's console via VNC. The root cause was found to be at the compute node (10.52.224.20) which dropped network connection on vnc-server port(s) (i.e. 5900+N) from the controller node. 22: connecting to: 10.52.224.20:5903 22: handler exception: [Errno 113] EHOSTUNREACH A temp work-around is to manually open up vnc ports on compute node(s). -A INPUT -m state --state NEW -m tcp -p tcp --dport 5900:5950 -j ACCEPT Wondering if this could be addressed dynamically, during VM creation ideally. The issue was found with openstack-nova-compute-2013.2-2.el6 running on CentOS kernel 2.6.32-358.123.2.openstack.el6.x86_64. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1260118/+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 1254555] Re: tenant does not see network that is routable from tenant-visible network until neutron-server is restarted
All commits here were with Partial-Bug: or Related-Bug: - what's left to fix or can this be closed? ** Also affects: neutron/havana Importance: Undecided Status: New ** Changed in: neutron/havana Status: New = Fix Committed ** Changed in: neutron/havana Importance: Undecided = High ** Changed in: neutron/havana Milestone: None = 2013.2.2 ** Changed in: neutron/havana Assignee: (unassigned) = Akihiro Motoki (amotoki) ** Tags removed: havana-backport-potential in-stable-havana -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1254555 Title: tenant does not see network that is routable from tenant-visible network until neutron-server is restarted Status in OpenStack Neutron (virtual network service): Confirmed Status in neutron havana series: Fix Committed Status in tripleo - openstack on openstack: Fix Released Bug description: In TripleO We have a setup script[1] that does this as an admin: neutron net-create default-net --shared neutron subnet-create --ip_version 4 --allocation-pool start=10.0.0.2,end=10.255.255.254 --gateway 10.0.0.1 10.0.0.0/8 $ID_OF_default_net neutron router-create default-router neutron router-interface-add default-router $ID_OF_10.0.0.0/8_subnet neutron net-create ext-net --router:external=True neutron subnet-create ext-net $FLOATING_CIDR --disable-dhcp --alocation-pool start=$FLOATING_START,end=$FLOATING_END neutron router-gateway-set default-router ext-net I would then expect that all users will be able to see ext-net using 'neutron net-list' and that they will be able to create floating IPs on ext-net. As of this commit: commit c655156b98a0a25568a3745e114a0bae41bc49d1 Merge: 75ac6c1 c66212c Author: Jenkins jenk...@review.openstack.org Date: Sun Nov 24 10:02:04 2013 + Merge MidoNet: Added support for the admin_state_up flag I see that the ext-net network is not available after I do all of the above router/subnet creation. It does become available to tenants as soon as I restart neutron-server. [1] https://git.openstack.org/cgit/openstack/tripleo- incubator/tree/scripts/setup-neutron I can reproduce this at will using the TripleO devtest process on real hardware. I have not yet reproduced on VMs using the 'devtest' workflow. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1254555/+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 1275967] Re: duplicate rpc_backend registration
AFAICT the real issue here is that devstack doesn't clean up stale .pyc files ** Also affects: devstack Importance: Undecided Status: New ** Summary changed: - duplicate rpc_backend registration + devstack leaves stale .pyc files around -- 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/1275967 Title: devstack leaves stale .pyc files around Status in devstack - openstack dev environments: New Status in OpenStack Compute (Nova): In Progress Bug description: nova was recently ported to oslo.incubator. This results in devstack raising an exception about duplicate rpc_backend options being registered. The problem is that openstack/common/service.py was not updated as part of that work. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1275967/+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 1275967] Re: devstack leaves stale .pyc files around
** Changed in: nova Status: In Progress = 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/1275967 Title: devstack leaves stale .pyc files around Status in devstack - openstack dev environments: New Status in OpenStack Compute (Nova): Invalid Bug description: nova was recently ported to oslo.incubator. This results in devstack raising an exception about duplicate rpc_backend options being registered. The problem is that openstack/common/service.py was not updated as part of that work. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1275967/+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 1278430] [NEW] py26 unit testing fails with OverflowError: timeout is too large in eventlet/hubs/epolls.py do_poll
Public bug reported: it dies on timeout while sending a test success http://logs.openstack.org/01/68601/2/check/gate-neutron- python26/69a7a57/console.html#_2014-02-10_10_31_41_262 2014-02-10 10:31:41.312 | File /usr/lib64/python2.6/socket.py, line 303, in flush 2014-02-10 10:31:41.313 | self._sock.sendall(buffer(data, write_offset, buffer_size)) 2014-02-10 10:31:41.314 | File /home/jenkins/workspace/gate-neutron-python26/.tox/py26/lib/python2.6/site-packages/eventlet/greenio.py, line 388, in sendall 2014-02-10 10:31:41.314 | trampoline(self, write=True) 2014-02-10 10:31:41.315 | File /home/jenkins/workspace/gate-neutron-python26/.tox/py26/lib/python2.6/site-packages/eventlet/hubs/__init__.py, line 155, in trampoline 2014-02-10 10:31:41.316 | return hub.switch() 2014-02-10 10:31:41.316 | File /home/jenkins/workspace/gate-neutron-python26/.tox/py26/lib/python2.6/site-packages/eventlet/hubs/hub.py, line 187, in switch 2014-02-10 10:31:41.317 | return self.greenlet.switch() 2014-02-10 10:31:41.318 | File /home/jenkins/workspace/gate-neutron-python26/.tox/py26/lib/python2.6/site-packages/eventlet/hubs/hub.py, line 236, in run 2014-02-10 10:31:41.319 | self.wait(sleep_time) 2014-02-10 10:31:41.319 | File /home/jenkins/workspace/gate-neutron-python26/.tox/py26/lib/python2.6/site-packages/eventlet/hubs/poll.py, line 84, in wait 2014-02-10 10:31:41.320 | presult = self.do_poll(seconds) 2014-02-10 10:31:41.320 | File /home/jenkins/workspace/gate-neutron-python26/.tox/py26/lib/python2.6/site-packages/eventlet/hubs/epolls.py, line 61, in do_poll 2014-02-10 10:31:41.321 | return self.poll.poll(seconds) 2014-02-10 10:31:41.323 | OverflowError: timeout is too large ** 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/1278430 Title: py26 unit testing fails with OverflowError: timeout is too large in eventlet/hubs/epolls.py do_poll Status in OpenStack Neutron (virtual network service): New Bug description: it dies on timeout while sending a test success http://logs.openstack.org/01/68601/2/check/gate-neutron- python26/69a7a57/console.html#_2014-02-10_10_31_41_262 2014-02-10 10:31:41.312 | File /usr/lib64/python2.6/socket.py, line 303, in flush 2014-02-10 10:31:41.313 | self._sock.sendall(buffer(data, write_offset, buffer_size)) 2014-02-10 10:31:41.314 | File /home/jenkins/workspace/gate-neutron-python26/.tox/py26/lib/python2.6/site-packages/eventlet/greenio.py, line 388, in sendall 2014-02-10 10:31:41.314 | trampoline(self, write=True) 2014-02-10 10:31:41.315 | File /home/jenkins/workspace/gate-neutron-python26/.tox/py26/lib/python2.6/site-packages/eventlet/hubs/__init__.py, line 155, in trampoline 2014-02-10 10:31:41.316 | return hub.switch() 2014-02-10 10:31:41.316 | File /home/jenkins/workspace/gate-neutron-python26/.tox/py26/lib/python2.6/site-packages/eventlet/hubs/hub.py, line 187, in switch 2014-02-10 10:31:41.317 | return self.greenlet.switch() 2014-02-10 10:31:41.318 | File /home/jenkins/workspace/gate-neutron-python26/.tox/py26/lib/python2.6/site-packages/eventlet/hubs/hub.py, line 236, in run 2014-02-10 10:31:41.319 | self.wait(sleep_time) 2014-02-10 10:31:41.319 | File /home/jenkins/workspace/gate-neutron-python26/.tox/py26/lib/python2.6/site-packages/eventlet/hubs/poll.py, line 84, in wait 2014-02-10 10:31:41.320 | presult = self.do_poll(seconds) 2014-02-10 10:31:41.320 | File /home/jenkins/workspace/gate-neutron-python26/.tox/py26/lib/python2.6/site-packages/eventlet/hubs/epolls.py, line 61, in do_poll 2014-02-10 10:31:41.321 | return self.poll.poll(seconds) 2014-02-10 10:31:41.323 | OverflowError: timeout is too large To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1278430/+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 1278449] [NEW] Inconsistent behavior between instances, volumes network, router pages when quota limit is exceeded
Public bug reported: Inconsistent behavior between instances,volumes network, router pages when quota limit is exceeded +++Steps to reproduce the issue: 1- Bring up the appliance 2- Login to horizon, create one project and assign one user to this project 3- Edit the project quotas and provide all the values as 0 4- Click on save button. 5- Now login to horizon with the created user: traverse instances page and Volumes page, you can observe the message saying Quota exceeded as expected Please see the screenshot attached. similarly traverse the page Access Security, you can observe the Create security group button is enabled and when you try to create the security group, creation fails with message unable to create security group Similarly traverse the page networks, you can observe create network button is enabled and when you try to create network, creation fails with message Failed to create network, quota exceeded for resources Similarly traverse the page router,you can observe the Create router button is enabled and when you try to create the router,creation fails with message unable to create router. Summarizing above behavior, instance and volume pages shows the message as expected whereas access security,networks, routers page allowed user to create network, router etc but failed to create. Inconsistencies observed between different pages. ** Affects: horizon 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/1278449 Title: Inconsistent behavior between instances,volumes network, router pages when quota limit is exceeded Status in OpenStack Dashboard (Horizon): New Bug description: Inconsistent behavior between instances,volumes network, router pages when quota limit is exceeded +++Steps to reproduce the issue: 1- Bring up the appliance 2- Login to horizon, create one project and assign one user to this project 3- Edit the project quotas and provide all the values as 0 4- Click on save button. 5- Now login to horizon with the created user: traverse instances page and Volumes page, you can observe the message saying Quota exceeded as expected Please see the screenshot attached. similarly traverse the page Access Security, you can observe the Create security group button is enabled and when you try to create the security group, creation fails with message unable to create security group Similarly traverse the page networks, you can observe create network button is enabled and when you try to create network, creation fails with message Failed to create network, quota exceeded for resources Similarly traverse the page router,you can observe the Create router button is enabled and when you try to create the router,creation fails with message unable to create router. Summarizing above behavior, instance and volume pages shows the message as expected whereas access security,networks, routers page allowed user to create network, router etc but failed to create. Inconsistencies observed between different pages. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1278449/+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 1278471] [NEW] Dependency check fails when creating a clean Fedora image
Public bug reported:
When trying to build a complete Fedora image from scratch (i.e. using
live-cd-creator for creating a live-cd with openstack-neutron package)
with all openstack-* packages, an error arises:
File /usr/lib/python2.7/site-packages/imgcreate/yuminst.py, line 220, in
runInstall
raise CreatorError(Dependency check failed : %s % \n.join([str(d) for d
in deps]))
imgcreate.errors.CreatorError: Dependency check failed : (('openstack-neutron',
'2013.2.1', '2.fc20'), ('/bin/sh', ''), 0, 0, None)
Since this problem did not happen when I tried creating images with the
old openstack-quantum package, I sought for the diff between the two.
The major difference in the RPM file in the existence of two new section
in the spec file: %posttrans and %pretrans. Once removing them, the
error no longer occurs.
The above is caused probably because rpm can't handle dependencies
(/bin/sh in this case) properly that exists in %posttrans and %pretrans
section in the spec file. Once removing those sections (Personally
because I have no need for the upgrading quantum functionality) the
matter is resolved.
** 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/1278471
Title:
Dependency check fails when creating a clean Fedora image
Status in OpenStack Neutron (virtual network service):
New
Bug description:
When trying to build a complete Fedora image from scratch (i.e. using
live-cd-creator for creating a live-cd with openstack-neutron package)
with all openstack-* packages, an error arises:
File /usr/lib/python2.7/site-packages/imgcreate/yuminst.py, line 220, in
runInstall
raise CreatorError(Dependency check failed : %s % \n.join([str(d) for
d in deps]))
imgcreate.errors.CreatorError: Dependency check failed :
(('openstack-neutron', '2013.2.1', '2.fc20'), ('/bin/sh', ''), 0, 0, None)
Since this problem did not happen when I tried creating images with
the old openstack-quantum package, I sought for the diff between the
two. The major difference in the RPM file in the existence of two new
section in the spec file: %posttrans and %pretrans. Once removing
them, the error no longer occurs.
The above is caused probably because rpm can't handle dependencies
(/bin/sh in this case) properly that exists in %posttrans and
%pretrans section in the spec file. Once removing those sections
(Personally because I have no need for the upgrading quantum
functionality) the matter is resolved.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1278471/+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 1275062] Re: image location is logged when authentication to store fails
@nikhil: any chance you could propose this patch for stable/grizzly as
well ?
** Also affects: glance/grizzly
Importance: Undecided
Status: New
** Also affects: glance/havana
Importance: Undecided
Status: New
** Changed in: glance/havana
Status: New = In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1275062
Title:
image location is logged when authentication to store fails
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Committed
Status in Glance grizzly series:
New
Status in Glance havana series:
In Progress
Status in OpenStack Security Advisories:
Triaged
Bug description:
WARNING glance.store [-] Get image UUID data from {'url':
u'swift+https://X@my_auth_url.com/v2.0/my-images/uuid,
'metadata': {}} failed: Auth GET failed: https://my_auth_url.com
RESP_CODE
19:13:05.027 ERROR glance.store [-] Glance tried all locations to get
data for image UUID but all have failed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1275062/+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 1278487] [NEW] Horizon hangs when double deleting instance
Public bug reported: Steps to reproduce: 1. In Horizon, launch an instance; 2. After the launching is completed, terminate the instance; 3. While the instance is being deleted, a Terminate Instance button appears within the row for the instance being terminated; 4. Press the Terminate Instance button while the instance was not terminated yet; 5. In the Terminate Instance confirmation dialog, wait until the instance has been deleted (as it disappears from the list in the grayed out background page); 6. Press the Terminate Instance button in the confirmation dialog; 7. The UI hangs indefinitely, showing a Working status. Refreshing the browser session seems to clear the problem. ** Affects: horizon 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/1278487 Title: Horizon hangs when double deleting instance Status in OpenStack Dashboard (Horizon): New Bug description: Steps to reproduce: 1. In Horizon, launch an instance; 2. After the launching is completed, terminate the instance; 3. While the instance is being deleted, a Terminate Instance button appears within the row for the instance being terminated; 4. Press the Terminate Instance button while the instance was not terminated yet; 5. In the Terminate Instance confirmation dialog, wait until the instance has been deleted (as it disappears from the list in the grayed out background page); 6. Press the Terminate Instance button in the confirmation dialog; 7. The UI hangs indefinitely, showing a Working status. Refreshing the browser session seems to clear the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1278487/+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 1229324] Re: extraneous vim editor configuration comments
** Also affects: python-cinderclient Importance: Undecided Status: New ** Changed in: python-cinderclient Importance: Undecided = Low ** Changed in: python-cinderclient Assignee: (unassigned) = Jay Bryant (jsbryant) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1229324 Title: extraneous vim editor configuration comments Status in OpenStack Telemetry (Ceilometer): Fix Released Status in Cinder: Fix Released Status in OpenStack Image Registry and Delivery Service (Glance): Fix Released Status in Orchestration API (Heat): In Progress Status in OpenStack Identity (Keystone): In Progress Status in OpenStack Neutron (virtual network service): In Progress Status in OpenStack Compute (Nova): In Progress Status in Oslo - a Library of Common OpenStack Code: Fix Released Status in Python client library for Ceilometer: In Progress Status in Python client library for Cinder: New Status in Python client library for Glance: Fix Committed Status in Python client library for heat: Fix Committed Status in Python client library for Keystone: In Progress Status in Python client library for Neutron: In Progress Status in OpenStack Object Storage (Swift): New Status in Tempest: Fix Released Bug description: Many of the source code files have a beginning line # vim: tabstop=4 shiftwidth=4 softtabstop=4 This should be deleted. Many of these lines are in the ceilometer/openstack/common directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1229324/+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 1278513] [NEW] Provide non-American English alias for nova boot --flavor
Public bug reported: The spelling of flavor in the Nova client is americanized. Those with a non-American English education might prefer to have aliases available for flavour in, e.g., nova boot and the various nova flavor-* commands. There is a precedent in the gnu/linux world in grep where colour can be spelt color, e.g. in grep: grep --help | grep colo --color[=WHEN], --colour[=WHEN] use markers to highlight the matching strings; ** Affects: nova Importance: Undecided Status: 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/1278513 Title: Provide non-American English alias for nova boot --flavor Status in OpenStack Compute (Nova): Won't Fix Bug description: The spelling of flavor in the Nova client is americanized. Those with a non-American English education might prefer to have aliases available for flavour in, e.g., nova boot and the various nova flavor-* commands. There is a precedent in the gnu/linux world in grep where colour can be spelt color, e.g. in grep: grep --help | grep colo --color[=WHEN], --colour[=WHEN] use markers to highlight the matching strings; To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1278513/+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 1278513] Re: Provide non-American English alias for nova boot --flavor
The spelling in APIs and command lines are commonly standardized on US english. I don't think we should go and alias everything which might have a UK english spelling difference. ** 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/1278513 Title: Provide non-American English alias for nova boot --flavor Status in OpenStack Compute (Nova): Won't Fix Bug description: The spelling of flavor in the Nova client is americanized. Those with a non-American English education might prefer to have aliases available for flavour in, e.g., nova boot and the various nova flavor-* commands. There is a precedent in the gnu/linux world in grep where colour can be spelt color, e.g. in grep: grep --help | grep colo --color[=WHEN], --colour[=WHEN] use markers to highlight the matching strings; To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1278513/+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 1228977] Re: n-cpu seems to crash when running with libvirt 1.1.1 from ubuntu cloud archive
** Also affects: libvirt (Ubuntu Saucy) 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/1228977 Title: n-cpu seems to crash when running with libvirt 1.1.1 from ubuntu cloud archive Status in Ubuntu Cloud Archive: Confirmed Status in OpenStack Compute (Nova): Confirmed Status in “libvirt” package in Ubuntu: Confirmed Status in “libvirt” source package in Saucy: New Bug description: We experienced a series of jenkins rejects starting overnight on Saturday whose root cause is still not quite tracked down yet. However, they all have a couple of things in common: 1) they are the first attempt to use libvir 1.0.6 from havana cloud archive for ubuntu precise 2) the fails are all related to guests not spawning correctly 3) the n-cpu log just stops about 1/2 way through the tempest log, making my suspect that we did something to either lockup or hard crash n-cpu After that change went in no devstack/tempest gating project managed to merge a change. This needs more investigation, but creating this bug to both reverify against, as well as track down this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1228977/+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 1228977] Re: n-cpu seems to crash when running with libvirt 1.1.1 from ubuntu cloud archive
Based on the newest listed patch being 'Push nwfilter update locking up to top level', and this patch being applied in trusty, i will mark this as fix released in trusty. I'm testing a saucy package with all the v1.1.1-maint patches applied. ** Changed in: libvirt (Ubuntu) Importance: Undecided = High ** Changed in: libvirt (Ubuntu) Status: Confirmed = Fix Released ** Changed in: libvirt (Ubuntu Saucy) Importance: Undecided = High ** Changed in: libvirt (Ubuntu Saucy) Status: New = Triaged -- 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/1228977 Title: n-cpu seems to crash when running with libvirt 1.1.1 from ubuntu cloud archive Status in Ubuntu Cloud Archive: Confirmed Status in OpenStack Compute (Nova): Confirmed Status in “libvirt” package in Ubuntu: Fix Released Status in “libvirt” source package in Saucy: Triaged Bug description: We experienced a series of jenkins rejects starting overnight on Saturday whose root cause is still not quite tracked down yet. However, they all have a couple of things in common: 1) they are the first attempt to use libvir 1.0.6 from havana cloud archive for ubuntu precise 2) the fails are all related to guests not spawning correctly 3) the n-cpu log just stops about 1/2 way through the tempest log, making my suspect that we did something to either lockup or hard crash n-cpu After that change went in no devstack/tempest gating project managed to merge a change. This needs more investigation, but creating this bug to both reverify against, as well as track down this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1228977/+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 1278530] [NEW] BigSwitch: Ports on shared network sending wrong netid
Public bug reported: When creating a port on a shared network, the plugin is currently using the tenant ID of the port owner in the URI rather than the tenant ID of the network owner. This should always be the tenant ID of the network the port is being attached to. ** Affects: neutron Importance: Undecided Assignee: Kevin Benton (kevinbenton) Status: New ** Changed in: neutron Assignee: (unassigned) = Kevin Benton (kevinbenton) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1278530 Title: BigSwitch: Ports on shared network sending wrong netid Status in OpenStack Neutron (virtual network service): New Bug description: When creating a port on a shared network, the plugin is currently using the tenant ID of the port owner in the URI rather than the tenant ID of the network owner. This should always be the tenant ID of the network the port is being attached to. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1278530/+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 1278533] [NEW] Rebuild instance should check any attached volume before rebuilding it
Public bug reported: When rebuilding an instance without detaching the attached volume from the instance first, nova ‘rebuild_instance’ doesn’t check for any attached volumes and go ahead to rebuild the instance. Therefore, the volume is still attached to the host of 3PAR server. Once the instance is built successfully, it fails to attach the same volume to the rebuilt instance. Steps to reproduce the issue: 1. create an instance, create volume 2. attach the volume to the instance 3. mount the volume to the instance 4. perform rebuild instance without detaching volume 5. attach the same volume to the rebuilt instance ** 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/1278533 Title: Rebuild instance should check any attached volume before rebuilding it Status in OpenStack Compute (Nova): New Bug description: When rebuilding an instance without detaching the attached volume from the instance first, nova ‘rebuild_instance’ doesn’t check for any attached volumes and go ahead to rebuild the instance. Therefore, the volume is still attached to the host of 3PAR server. Once the instance is built successfully, it fails to attach the same volume to the rebuilt instance. Steps to reproduce the issue: 1. create an instance, create volume 2. attach the volume to the instance 3. mount the volume to the instance 4. perform rebuild instance without detaching volume 5. attach the same volume to the rebuilt instance To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1278533/+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 1278550] [NEW] test_provider_token_expiration_validation tests fails on slow system
Public bug reported:
The
keystone.tests.test_token_provider.TestTokenProvider.test_provider_token_expiration_validation
test fails on a system where it takes a long time to run the tests. The
problem is that the test is expecting the token to be valid, but with the long
run time and the shorter default token expiration time, the token turns out to
not be valid by the time the system gets around to running the test.
The errors are like:
in output log:
{{{
...
Traceback (most recent call last):
File keystone/token/provider.py, line 188, in _is_valid_token
expires_at = token_data['token']['expires']
KeyError: 'token'
...}}}
Traceback (most recent call last):
File keystone/tests/test_token_provider.py, line 818, in
test_provider_token_expiration_validation
self.token_provider_api._is_valid_token(SAMPLE_V2_TOKEN_VALID))
File keystone/token/provider.py, line 202, in _is_valid_token
raise exception.TokenNotFound(_('Failed to validate token'))
TokenNotFound: Failed to validate token
There's probably another issue indicated here since we shouldn't be
getting a KeyError in the case of an expired token.
** 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/1278550
Title:
test_provider_token_expiration_validation tests fails on slow system
Status in OpenStack Identity (Keystone):
New
Bug description:
The
keystone.tests.test_token_provider.TestTokenProvider.test_provider_token_expiration_validation
test fails on a system where it takes a long time to run the tests. The
problem is that the test is expecting the token to be valid, but with the long
run time and the shorter default token expiration time, the token turns out to
not be valid by the time the system gets around to running the test.
The errors are like:
in output log:
{{{
...
Traceback (most recent call last):
File keystone/token/provider.py, line 188, in _is_valid_token
expires_at = token_data['token']['expires']
KeyError: 'token'
...}}}
Traceback (most recent call last):
File keystone/tests/test_token_provider.py, line 818, in
test_provider_token_expiration_validation
self.token_provider_api._is_valid_token(SAMPLE_V2_TOKEN_VALID))
File keystone/token/provider.py, line 202, in _is_valid_token
raise exception.TokenNotFound(_('Failed to validate token'))
TokenNotFound: Failed to validate token
There's probably another issue indicated here since we shouldn't be
getting a KeyError in the case of an expired token.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1278550/+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 1278547] [NEW] Update openstack_dashboard test settings.py
Public bug reported:
The settings.py file in the test directory for openstack_dashboard is
missing the profile option in the OPENSTACK_NEUTRON_NETWORK setting.
This needs to be updated so that the tests for the router dashboard
and cisco N1K will be run correctly.
This is the setting in local_settings.py currently -
# The OPENSTACK_NEUTRON_NETWORK settings can be used to enable optional
# services provided by neutron. Options currenly available are load
# balancer service, security groups, quotas, VPN service.
OPENSTACK_NEUTRON_NETWORK = {
'enable_security_group': False,
'enable_lb': False,
'enable_firewall': False,
'enable_quotas': True,
'enable_vpn': False,
# The profile_support option is used to detect if an external router can be
# configured via the dashboard. When using specific plugins the
# profile_support can be turned on if needed.
'profile_support': None,
#'profile_support': 'cisco',
}
And this is the setting in test/settings.py -
OPENSTACK_NEUTRON_NETWORK = {
'enable_lb': True,
'enable_firewall': True,
'enable_quotas': False, # Enabled in specific tests only
'enable_vpn': True
}
The profile_setting option needs to be added.
** Affects: horizon
Importance: Undecided
Assignee: Abishek Subramanian (absubram)
Status: New
** Changed in: horizon
Assignee: (unassigned) = Abishek Subramanian (absubram)
** Description changed:
The settings.py file in the test directory for openstack_dashboard is
missing the profile option in the OPENSTACK_NEUTRON_NETWORK setting.
This needs to be updated so that the tests for the router dashboard
and cisco N1K will be run correctly.
+
+ This is the setting in local_settings.py currently -
+ # The OPENSTACK_NEUTRON_NETWORK settings can be used to enable optional
+ # services provided by neutron. Options currenly available are load
+ # balancer service, security groups, quotas, VPN service.
+ OPENSTACK_NEUTRON_NETWORK = {
+ 'enable_security_group': False,
+ 'enable_lb': False,
+ 'enable_firewall': False,
+ 'enable_quotas': True,
+ 'enable_vpn': False,
+ # The profile_support option is used to detect if an external router can
be
+ # configured via the dashboard. When using specific plugins the
+ # profile_support can be turned on if needed.
+ 'profile_support': None,
+ #'profile_support': 'cisco',
+ }
+
+ And this is the setting in test/settings.py -
+ OPENSTACK_NEUTRON_NETWORK = {
+ 'enable_lb': True,
+ 'enable_firewall': True,
+ 'enable_quotas': False, # Enabled in specific tests only
+ 'enable_vpn': True
+ }
+
+ The profile_setting option needs to be added.
--
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/1278547
Title:
Update openstack_dashboard test settings.py
Status in OpenStack Dashboard (Horizon):
New
Bug description:
The settings.py file in the test directory for openstack_dashboard is
missing the profile option in the OPENSTACK_NEUTRON_NETWORK setting.
This needs to be updated so that the tests for the router dashboard
and cisco N1K will be run correctly.
This is the setting in local_settings.py currently -
# The OPENSTACK_NEUTRON_NETWORK settings can be used to enable optional
# services provided by neutron. Options currenly available are load
# balancer service, security groups, quotas, VPN service.
OPENSTACK_NEUTRON_NETWORK = {
'enable_security_group': False,
'enable_lb': False,
'enable_firewall': False,
'enable_quotas': True,
'enable_vpn': False,
# The profile_support option is used to detect if an external router can
be
# configured via the dashboard. When using specific plugins the
# profile_support can be turned on if needed.
'profile_support': None,
#'profile_support': 'cisco',
}
And this is the setting in test/settings.py -
OPENSTACK_NEUTRON_NETWORK = {
'enable_lb': True,
'enable_firewall': True,
'enable_quotas': False, # Enabled in specific tests only
'enable_vpn': True
}
The profile_setting option needs to be added.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1278547/+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 1278557] [NEW] VM instance errors out - shows that it's still attached to volume
Public bug reported: == How to Reproduce == 1. Create an Instance with flavor m1xlarge, then select 'Boot from Volume'. Pick a volume whose size cannot accommodate the flavor. 2. Launch == Instance will go into error state 4. Now click on the instance name to see the Detail view, scroll to bottom to see it is attached to the volume you selected 5. Now click on that volume to see the Detail view == It does not show it is attached to the volume == In the Volume table, the volume is shown as available If we checked the volume size and the flavor resources, then we could prevent this issue instead of giving the generic error Valid host not found. The error state instance should not show the volume attachment in the detail view. ** Affects: horizon 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/1278557 Title: VM instance errors out - shows that it's still attached to volume Status in OpenStack Dashboard (Horizon): New Bug description: == How to Reproduce == 1. Create an Instance with flavor m1xlarge, then select 'Boot from Volume'. Pick a volume whose size cannot accommodate the flavor. 2. Launch == Instance will go into error state 4. Now click on the instance name to see the Detail view, scroll to bottom to see it is attached to the volume you selected 5. Now click on that volume to see the Detail view == It does not show it is attached to the volume == In the Volume table, the volume is shown as available If we checked the volume size and the flavor resources, then we could prevent this issue instead of giving the generic error Valid host not found. The error state instance should not show the volume attachment in the detail view. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1278557/+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 1275062] Re: image location is logged when authentication to store fails
Thanks for pointing that out ttx, however we do not have this issue in
stable/grizzly.
Please find the code for grizzly here:
https://github.com/openstack/glance/blob/stable/grizzly/glance/store/__init__.py#L393
** Changed in: glance/grizzly
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/1275062
Title:
image location is logged when authentication to store fails
Status in OpenStack Image Registry and Delivery Service (Glance):
Fix Committed
Status in Glance grizzly series:
Invalid
Status in Glance havana series:
In Progress
Status in OpenStack Security Advisories:
Triaged
Bug description:
WARNING glance.store [-] Get image UUID data from {'url':
u'swift+https://X@my_auth_url.com/v2.0/my-images/uuid,
'metadata': {}} failed: Auth GET failed: https://my_auth_url.com
RESP_CODE
19:13:05.027 ERROR glance.store [-] Glance tried all locations to get
data for image UUID but all have failed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1275062/+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 1277746] Re: landscape module not working
** Also affects: landscape-client Importance: Undecided Status: New -- 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/1277746 Title: landscape module not working Status in Init scripts for use on cloud images: New Status in Landscape Client: New Bug description: I've been trying to boot a saucy guest and have been unable to get landscape configured properly. Following the landscape example, I've run into a few issues. My first config was pretty full (like the example), but after lots of failures, I pared it down to this simple case: #cloud-config landscape: client: computer_title = fred account_name = example When I do that, it writes out the landscape client conf like this: client = computer_title = fred account_name = example This is obviously incorrect and landscape complains thusly. Am I doing this wrong or are the docs perhaps incorrect? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1277746/+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 1278642] [NEW] Need 'month to date' in Resource Usage
Public bug reported: Currently there are multiple date options for Resource Usage panel but many times usage is viewed on month boundaries. I would like to add a Month to date' option to date options list. ** Affects: horizon 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/1278642 Title: Need 'month to date' in Resource Usage Status in OpenStack Dashboard (Horizon): New Bug description: Currently there are multiple date options for Resource Usage panel but many times usage is viewed on month boundaries. I would like to add a Month to date' option to date options list. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1278642/+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 1271426] Re: protected property change not rejected if a subsequent rule match accepts them
This seems like something that might catch out unsuspecting sysadmins. Do you think it is worth issuing an OSSN for this? ** Also affects: ossn Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1271426 Title: protected property change not rejected if a subsequent rule match accepts them Status in OpenStack Image Registry and Delivery Service (Glance): Fix Committed Status in Glance havana series: In Progress Status in OpenStack Security Notes: New Bug description: See initial report here: http://lists.openstack.org/pipermail /openstack-dev/2014-January/024861.html What is happening is that if there is a specific rule that would reject an action and a less specific rule that comes after that would accept the action, then the action is being accepted. It should be rejected. This is because we iterate through the property protection rules rather than just finding the first match. This bug does not occur when policies are used to determine property protections, only when roles are used directly. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1271426/+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 1278654] [NEW] Resource Usage views.py needs a some refactoring
Public bug reported: In trying to reuse some of the code in views, I realized that the get method for SampleView is quite long. I will submit this refactoring into a few smaller methods as a cleanup. It will also allow more reuse of the code in the future. ** Affects: horizon 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/1278654 Title: Resource Usage views.py needs a some refactoring Status in OpenStack Dashboard (Horizon): New Bug description: In trying to reuse some of the code in views, I realized that the get method for SampleView is quite long. I will submit this refactoring into a few smaller methods as a cleanup. It will also allow more reuse of the code in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1278654/+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 1260495] Re: Setting autodoc_tree_index_modules makes documentation builds fail
** Also affects: python-keystoneclient 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/1260495 Title: Setting autodoc_tree_index_modules makes documentation builds fail Status in OpenStack Identity (Keystone): Confirmed Status in Python Build Reasonableness: New Status in Python client library for Keystone: New Bug description: The arguments originally being passed into sphinx.apidoc specified '.' as the path to index. Unfortunately this includes the setup.py module. Sphinx dies while trying to process the setup.rst likely because the setup.py module calls setuptools.setup() when imported causing some sort of recursion. The final result is something like: 2013-12-08 21:08:12.088 | reading sources... [ 80%] api/setup 2013-12-08 21:08:12.100 | /usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'setup_requires' 2013-12-08 21:08:12.101 | warnings.warn(msg) 2013-12-08 21:08:12.102 | /usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution option: 'pbr' 2013-12-08 21:08:12.102 | warnings.warn(msg) 2013-12-08 21:08:12.103 | usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] 2013-12-08 21:08:12.103 |or: setup.py --help [cmd1 cmd2 ...] 2013-12-08 21:08:12.104 |or: setup.py --help-commands 2013-12-08 21:08:12.104 |or: setup.py cmd --help 2013-12-08 21:08:12.104 | 2013-12-08 21:08:12.105 | error: invalid command 'build_sphinx' 2013-12-08 21:08:12.622 | ERROR: InvocationError: '/home/jenkins/workspace/gate-keystone-docs/.tox/venv/bin/python setup.py build_sphinx' To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1260495/+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 1278674] [NEW] Vm doesn't get IP due to deleting another subnet
Public bug reported: I found that when a network has two subnet, vm can't get IP if I delete one subnet, you can reprodeuce this problem by the step: 1. create a new network 2. create subnetA in this network 3. create a port in subnetA 4. create subnetB in this network 5. delete subnetA 6. create vm in subnetB, the vm can't get IP I analyse the problem, the reason is that: in my environment, the network id is 2914fe0b-721e-4738-b018-71ac4883e6f8, then you can see there are two TAP in the namespace qdhcp-2914fe0b-721e-4738-b018-71ac4883e6f8 root@ubuntu-242:/var/log/neutron# ip netns exec qdhcp-2914fe0b-721e-4738-b018-71ac4883e6f8 ip addr show 10: tapfd90aa02-d9: BROADCAST,PROMISC,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether fa:16:3e:6a:37:8f brd ff:ff:ff:ff:ff:ff inet 60.60.60.3/24 brd 60.60.60.255 scope global tapfd90aa02-d9 inet 169.254.169.254/16 brd 169.254.255.255 scope global tapfd90aa02-d9 inet 70.70.70.2/24 brd 70.70.70.255 scope global tapfd90aa02-d9 inet6 fe80::f816:3eff:fe6a:378f/64 scope link valid_lft forever preferred_lft forever 15: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 37: tapbed116e5-4f: BROADCAST,PROMISC,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether fa:16:3e:96:c7:ec brd ff:ff:ff:ff:ff:ff inet 70.70.70.2/24 brd 70.70.70.255 scope global tapbed116e5-4f inet 169.254.169.254/16 brd 169.254.255.255 scope global tapbed116e5-4f inet6 fe80::f816:3eff:fe96:c7ec/64 scope link valid_lft forever preferred_lft forever you can see that the ip: 70.70.70.2 is set on two tap ** Affects: neutron Importance: Undecided Assignee: shihanzhang (shihanzhang) Status: New ** Changed in: neutron Assignee: (unassigned) = shihanzhang (shihanzhang) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1278674 Title: Vm doesn't get IP due to deleting another subnet Status in OpenStack Neutron (virtual network service): New Bug description: I found that when a network has two subnet, vm can't get IP if I delete one subnet, you can reprodeuce this problem by the step: 1. create a new network 2. create subnetA in this network 3. create a port in subnetA 4. create subnetB in this network 5. delete subnetA 6. create vm in subnetB, the vm can't get IP I analyse the problem, the reason is that: in my environment, the network id is 2914fe0b-721e-4738-b018-71ac4883e6f8, then you can see there are two TAP in the namespace qdhcp-2914fe0b-721e-4738-b018-71ac4883e6f8 root@ubuntu-242:/var/log/neutron# ip netns exec qdhcp-2914fe0b-721e-4738-b018-71ac4883e6f8 ip addr show 10: tapfd90aa02-d9: BROADCAST,PROMISC,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether fa:16:3e:6a:37:8f brd ff:ff:ff:ff:ff:ff inet 60.60.60.3/24 brd 60.60.60.255 scope global tapfd90aa02-d9 inet 169.254.169.254/16 brd 169.254.255.255 scope global tapfd90aa02-d9 inet 70.70.70.2/24 brd 70.70.70.255 scope global tapfd90aa02-d9 inet6 fe80::f816:3eff:fe6a:378f/64 scope link valid_lft forever preferred_lft forever 15: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 37: tapbed116e5-4f: BROADCAST,PROMISC,UP,LOWER_UP mtu 1500 qdisc noqueue state UNKNOWN link/ether fa:16:3e:96:c7:ec brd ff:ff:ff:ff:ff:ff inet 70.70.70.2/24 brd 70.70.70.255 scope global tapbed116e5-4f inet 169.254.169.254/16 brd 169.254.255.255 scope global tapbed116e5-4f inet6 fe80::f816:3eff:fe96:c7ec/64 scope link valid_lft forever preferred_lft forever you can see that the ip: 70.70.70.2 is set on two tap To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1278674/+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 1278677] [NEW] VMware driver should cache morefs
Public bug reported: The VMware needs to cache morefs as much as possible throughout the codebase. This will avoid extra VC queries. ** Affects: nova Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: nova Assignee: (unassigned) = Arnaud Legendre (arnaudleg) -- 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/1278677 Title: VMware driver should cache morefs Status in OpenStack Compute (Nova): New Bug description: The VMware needs to cache morefs as much as possible throughout the codebase. This will avoid extra VC queries. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1278677/+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 1278678] [NEW] Hypervisors panel displays results in pseudorandom order, does text sorts
Public bug reported: The API calls just return the results in who-knows-what order, which can make the summary page look odd in installations with functional hostnames for compute nodes (e.g., compute1, compute2, compute3, ...) In addition, jquery-tablesorter sees the Hostname column as a plain text field, and does a standard string comparison sort, which yields results like host1, host10, host11, host2, host3, ...) in installations with functional hostnames for compute nodes ** Affects: horizon Importance: Undecided Assignee: Nicolas Simonds (nicolas.simonds) Status: In Progress -- 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/1278678 Title: Hypervisors panel displays results in pseudorandom order, does text sorts Status in OpenStack Dashboard (Horizon): In Progress Bug description: The API calls just return the results in who-knows-what order, which can make the summary page look odd in installations with functional hostnames for compute nodes (e.g., compute1, compute2, compute3, ...) In addition, jquery-tablesorter sees the Hostname column as a plain text field, and does a standard string comparison sort, which yields results like host1, host10, host11, host2, host3, ...) in installations with functional hostnames for compute nodes To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1278678/+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 1278686] [NEW] quota commits to wrong project/user if we use admin user to verify a resized instance of other's
Public bug reported: it is that, if the confirmation is launched through admin user, then the project_id and user_id in context are all admin's, which result in reservations in DB are also have wrong project_id and user_id, when these reservations are committed, the quotas usage of the instance's project/user will become wrong eventually. this bug can be reproduced both in stable havana and master. so we need to backport this fix patch to stable havana. this bug is similar as Bug #1271429. ** Affects: nova Importance: Undecided Assignee: wangpan (hzwangpan) Status: New ** Description changed: it is that, if the confirmation is launched through admin user, then the project_id and user_id in context are all admin's, which result in reservations in DB are also have wrong project_id and user_id, when these reservations are committed, the quotas usage of the instance's project/user will become wrong eventually. this bug can be reproduced both in stable havana and master. so we need to backport this fix patch to stable havana. - this bug is same as 1271429. + this bug is similar as Bug #1271429. -- 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/1278686 Title: quota commits to wrong project/user if we use admin user to verify a resized instance of other's Status in OpenStack Compute (Nova): New Bug description: it is that, if the confirmation is launched through admin user, then the project_id and user_id in context are all admin's, which result in reservations in DB are also have wrong project_id and user_id, when these reservations are committed, the quotas usage of the instance's project/user will become wrong eventually. this bug can be reproduced both in stable havana and master. so we need to backport this fix patch to stable havana. this bug is similar as Bug #1271429. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1278686/+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 1278690] [NEW] VMware: Fetching images from Glance is slower than it should be
Public bug reported: Ran an experiment with a 1.5GB file on a very basic devstack setup: glance download | curl PUT: 2.5min nova code: 4min Customers have reported similar concerns. ** Affects: nova Importance: Undecided Assignee: Arnaud Legendre (arnaudleg) Status: New ** Changed in: nova Assignee: (unassigned) = Arnaud Legendre (arnaudleg) -- 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/1278690 Title: VMware: Fetching images from Glance is slower than it should be Status in OpenStack Compute (Nova): New Bug description: Ran an experiment with a 1.5GB file on a very basic devstack setup: glance download | curl PUT: 2.5min nova code: 4min Customers have reported similar concerns. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1278690/+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 1278695] [NEW] quota commits to wrong project/user if we use admin user reverts a resized instance of other's
Public bug reported: it is that, if the resized instance is reverted through admin user, then the project_id and user_id in context are all admin's, which result in reservations in DB are also have wrong project_id and user_id, when these reservations are committed, the quotas usage of the instance's project/user will become wrong eventually. this bug can be reproduced both in stable havana and master. so we need to backport this fix patch to stable havana. this bug is similar as Bug #1271429. ** Affects: nova Importance: Undecided Assignee: wangpan (hzwangpan) Status: In Progress ** Changed in: nova Assignee: (unassigned) = wangpan (hzwangpan) -- 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/1278695 Title: quota commits to wrong project/user if we use admin user reverts a resized instance of other's Status in OpenStack Compute (Nova): In Progress Bug description: it is that, if the resized instance is reverted through admin user, then the project_id and user_id in context are all admin's, which result in reservations in DB are also have wrong project_id and user_id, when these reservations are committed, the quotas usage of the instance's project/user will become wrong eventually. this bug can be reproduced both in stable havana and master. so we need to backport this fix patch to stable havana. this bug is similar as Bug #1271429. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1278695/+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 1260723] Re: Invalid OpenStack Nova credentials.
** Project changed: keystone = devstack -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Keystone. https://bugs.launchpad.net/bugs/1260723 Title: Invalid OpenStack Nova credentials. Status in devstack - openstack dev environments: New Bug description: It seems there is a credentials problem, the gate failed because of Invalid OpenStack Nova credentials. http://logs.openstack.org/20/56420/7/check/check-tempest-dsvm- neutron/24b6f66/console.html#_2013-12-12_14_41_01_387 To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1260723/+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 1278696] [NEW] 'DescribeInstances' in ec2 shows wrong image-message to instance booting from volumes
Public bug reported:
'DescribeInstances' in ec2 shows the wrong image message('ami-0002')
to the instance booting from a volume:
n781dba539a84:~ # euca-describe-instances i-003a
RESERVATION r-mdcwadip c1c092e1c88f4027aeb203d50d63135b
INSTANCEi-003a ami-0002wjvm1 running None
(c1c092e1c88f4027aeb203d50d63135b, n781dba57c996) 0 m1.small
2014-02-10T07:00:40.000Znova 20.20.16.12
ebs
BLOCKDEVICE /dev/vdavol-000dfalse
More info can be found here: http://paste.openstack.org/show/64087/
--
The codes in ec2utils.py:
def glance_id_to_id(context, glance_id):
Convert a glance id to an internal (db) id.
if glance_id is None:
return
try:
return db.s3_image_get_by_uuid(context, glance_id)['id']
except exception.NotFound:
return db.s3_image_create(context, glance_id)['id']
--
The image_ref (as glance_id in this function) of the instance booting from a
volume, will be , not None.
The protected codes above can't take efforts.
** Affects: nova
Importance: Undecided
Assignee: wingwj (wingwj)
Status: New
** Tags: ec2
** Changed in: nova
Assignee: (unassigned) = wingwj (wingwj)
--
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/1278696
Title:
'DescribeInstances' in ec2 shows wrong image-message to instance
booting from volumes
Status in OpenStack Compute (Nova):
New
Bug description:
'DescribeInstances' in ec2 shows the wrong image
message('ami-0002') to the instance booting from a volume:
n781dba539a84:~ # euca-describe-instances i-003a
RESERVATION r-mdcwadip c1c092e1c88f4027aeb203d50d63135b
INSTANCEi-003a ami-0002wjvm1 running None
(c1c092e1c88f4027aeb203d50d63135b, n781dba57c996) 0 m1.small
2014-02-10T07:00:40.000Znova 20.20.16.12
ebs
BLOCKDEVICE /dev/vdavol-000dfalse
More info can be found here: http://paste.openstack.org/show/64087/
--
The codes in ec2utils.py:
def glance_id_to_id(context, glance_id):
Convert a glance id to an internal (db) id.
if glance_id is None:
return
try:
return db.s3_image_get_by_uuid(context, glance_id)['id']
except exception.NotFound:
return db.s3_image_create(context, glance_id)['id']
--
The image_ref (as glance_id in this function) of the instance booting from a
volume, will be , not None.
The protected codes above can't take efforts.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1278696/+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 1247568] Re: NotFound neutron errors should have a unique base class
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1247568
Title:
NotFound neutron errors should have a unique base class
Status in OpenStack Neutron (virtual network service):
Expired
Status in Python client library for Neutron:
Incomplete
Status in Tempest:
Expired
Bug description:
Most of the sever side exception are caught by the client and re-
thrown as the general NeutronError. original message and type are
still found in the message.
404-{u'NeutronError': {u'message': u'Security group rule 6957532c-
ae2c-4273-89c3-11a does not exist', u'type':
u'SecurityGroupRuleNotFound', u'detail': u''}}
this makes it impossible to catch unique error types such as NotFound.
for instance: in tempest (tempest/scenario/manager:
try:
# OpenStack resources are assumed to have a delete()
# method which destroys the resource...
thing.delete()
except Exception as e:
# If the resource is already missing, mission accomplished.
if e.__class__.__name__ == 'NotFound':
continue
raise
this code should catch and dismiss all not found resources, however,
since neutronClient doesn't have a unique NotFound type, it fails to
catch here.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1247568/+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 1240282] Re: VNC console can not display in Dashboard due to browser blocking cross domain calls
[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete = Expired
--
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/1240282
Title:
VNC console can not display in Dashboard due to browser blocking cross
domain calls
Status in OpenStack Dashboard (Horizon):
Expired
Bug description:
VNC console fails to be displayed by browsers like IE and Chrome due to cross
domain calls in Dashboard iframe.
Dashboard uses apache port 80 while vnc uses 6080. Default security policy
in browsers will forbid cross domain scripts from running. Users have to click
'show all content' in IE or 'load unsafe scripts' in Chrome to have vnc console
properly displayed, or disable the security policy, which is not advised.
p class='alert alert-info'If console is not responding to keyboard input:
click the grey status bar below. a
href=http://10.145.88.231:6080/vnc_auto.html?token=795e5dc0-51be-441c-bf54-5d53b7d65f5eamp;title=test1(a3811ba3-d10b-482c-9275-3dbd5196c1ce)
style=text-decoration: underlineClick here to show only console/a/p
iframe id=console_embed
src=http://10.145.88.231:6080/vnc_auto.html?token=795e5dc0-51be-441c-bf54-5d53b7d65f5eamp;title=test1(a3811ba3-d10b-482c-9275-3dbd5196c1ce)
style=width:100%;height:100%/iframe
script type=text/javascript
var fix_height = function() {
$('iframe#console_embed').css({ height: $(document).height() + 'px' });
};
// there are two code paths to this particular block; handle them both
if (typeof($) != 'undefined') {
$(document).ready(fix_height);
} else {
addHorizonLoadEvent(fix_height);
}
/script
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1240282/+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 1247568] Re: NotFound neutron errors should have a unique base class
[Expired for tempest because there has been no activity for 60 days.]
** Changed in: tempest
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1247568
Title:
NotFound neutron errors should have a unique base class
Status in OpenStack Neutron (virtual network service):
Expired
Status in Python client library for Neutron:
Incomplete
Status in Tempest:
Expired
Bug description:
Most of the sever side exception are caught by the client and re-
thrown as the general NeutronError. original message and type are
still found in the message.
404-{u'NeutronError': {u'message': u'Security group rule 6957532c-
ae2c-4273-89c3-11a does not exist', u'type':
u'SecurityGroupRuleNotFound', u'detail': u''}}
this makes it impossible to catch unique error types such as NotFound.
for instance: in tempest (tempest/scenario/manager:
try:
# OpenStack resources are assumed to have a delete()
# method which destroys the resource...
thing.delete()
except Exception as e:
# If the resource is already missing, mission accomplished.
if e.__class__.__name__ == 'NotFound':
continue
raise
this code should catch and dismiss all not found resources, however,
since neutronClient doesn't have a unique NotFound type, it fails to
catch here.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1247568/+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 1278705] [NEW] neutron can not deal with large token, it is not follow as nova, cinder does
Public bug reported: If the token is large, call neutron related API like /v2.0/networks, it would fail. response would have 400 for header too long If we checked nova, cinder, it have following as below: # Raise the default from 8192 to accommodate large tokens eventlet.wsgi.MAX_HEADER_LINE = 16384 While neutron wsgi.py not have that, so neutron can not deal with that. ** 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/1278705 Title: neutron can not deal with large token, it is not follow as nova, cinder does Status in OpenStack Neutron (virtual network service): New Bug description: If the token is large, call neutron related API like /v2.0/networks, it would fail. response would have 400 for header too long If we checked nova, cinder, it have following as below: # Raise the default from 8192 to accommodate large tokens eventlet.wsgi.MAX_HEADER_LINE = 16384 While neutron wsgi.py not have that, so neutron can not deal with that. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1278705/+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 1278736] [NEW] Strings passed to InvalidAggregateAction should be translated
Public bug reported: InvalidAggregateAction .looks like: class InvalidAggregateAction(Invalid): msg_fmt = _(Cannot perform action '%(action)s' on aggregate %(aggregate_id)s. Reason: %(reason)s.) The values for action are: delete add_host_to_aggregate update aggregate update aggregate metadata Also we use 'not empty' untranslated as a reason string in one place We should standardize these strings a little more and always translate them ** Affects: nova Importance: Low Status: Triaged ** Tags: aggregates i18n -- 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/1278736 Title: Strings passed to InvalidAggregateAction should be translated Status in OpenStack Compute (Nova): Triaged Bug description: InvalidAggregateAction .looks like: class InvalidAggregateAction(Invalid): msg_fmt = _(Cannot perform action '%(action)s' on aggregate %(aggregate_id)s. Reason: %(reason)s.) The values for action are: delete add_host_to_aggregate update aggregate update aggregate metadata Also we use 'not empty' untranslated as a reason string in one place We should standardize these strings a little more and always translate them To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1278736/+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
