[Yahoo-eng-team] [Bug 1406598] Re: nova-cells doesn't url decode transport_url
Fixed in oslo.messaging https://bugs.launchpad.net/oslo.messaging/+bug/1557496 ** Changed in: oslo.messaging Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1406598 Title: nova-cells doesn't url decode transport_url Status in OpenStack Compute (nova): Fix Released Status in oslo.messaging: Fix Released Bug description: When creating a cell using the nova-manage cell create command, the transport_url generated in the database is url-encoded (i.e. '=' is changed to '%3D', etc.) That's propably the correct behavior, since the connection string is stored as URL. However, nova-cells doesn't properly decode that string. So for transport_url credentials that contain url-encodable characters, nova- cells uses the url encoded string, rather than the actual correct credentials. Steps to reproduce: - Create a cell using nova-manage with credentials containing url- encodable characters: nova-manage cell create --name=cell_02 --cell_type=child --username='the=user' --password='the=password' --hostname='hostname' --port=5672 --virtual_host=/ --woffset=1 --wscale=1 - nova.cells table now contains a url-encoded transport_url: mysql> select * from cells \G *** 1. row *** created_at: 2014-12-30 17:30:41 updated_at: NULL deleted_at: NULL id: 3 api_url: NULL weight_offset: 1 weight_scale: 1 name: cell_02 is_parent: 0 deleted: 0 transport_url: rabbit://the%3Duser:the%3Dpassword@hostname:5672// 1 row in set (0.00 sec) - nova-cells uses the literal credentials 'the%3Duser' and 'the%3Dpassword' to connect to RMQ, rather than the correct 'the=user' and 'the=password' credentials. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1406598/+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 1329195] Re: Discrepancy in Free Ram in audit log and on Dashboard
[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/1329195 Title: Discrepancy in Free Ram in audit log and on Dashboard Status in OpenStack Dashboard (Horizon): Expired Bug description: I have connected Openstack to vCenter. This is my audit information from compute.log 2014-06-12 12:29:39.302 2915 AUDIT nova.compute.resource_tracker [-] Free ram (MB): 3308 2014-06-12 12:29:39.303 2915 AUDIT nova.compute.resource_tracker [-] Free disk (GB): 450 2014-06-12 12:29:39.303 2915 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 2 As you can see Free Memory is 3308 but in my horizon dashborad it shows that only 1GB of memory is available. And it does not allow me to utilize all 3 GB of vCenter memory that is actually avaiable. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1329195/+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 1328923] Re: The Disassociate Monitor list is not properly populated
[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/1328923 Title: The Disassociate Monitor list is not properly populated Status in OpenStack Dashboard (Horizon): Expired Bug description: When trying to disassociate a health monitor from pool, the workfow modal does not show the currently associated monitors. The list is empty. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1328923/+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 1273882] Re: os-collect-config unable to restart neutron-l3-agent
[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/1273882 Title: os-collect-config unable to restart neutron-l3-agent Status in neutron: Expired Status in tripleo: Invalid Bug description: The command 'os-collect-config --force --one' fails on overcloud- notcompute with: + service neutron-l3-agent restart neutron-l3-agent stop/waiting start: Job failed to start [2014-01-28 23:17:33,155] (os-refresh-config) [ERROR] during post-configure phase. [Command '['dib-run-parts', '/opt/stack/os-config-refresh/post-configure.d']' returned non-zero exit status 1] And in /var/log/upstart/neutron-l3-agent.log: Stderr: '/usr/bin/neutron-rootwrap: Unauthorized command: kill -9 11634 (no filter matched)\n' 2014-01-28 23:17:33.073 13463 ERROR neutron.common.legacy [-] Skipping unknown group key: firewall_driver 2014-01-28 23:17:33.133 13463 CRITICAL neutron [req-5f2c30e1-d121-4183-8bb1-109940edc995 None] Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'kill', '-9', '11634'] Exit code: 99 Stdout: '' Stderr: '/usr/bin/neutron-rootwrap: Unauthorized command: kill -9 11634 (no filter matched)\n' Was able to fix by adding filter to /etc/neutron/rootwrap.d/l3.filters: kill_l3_agent: KillFilter, root, /opt/stack/venvs/neutron/bin/python, -9 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1273882/+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 1435744] Re: UnicodeEncodeError in Creating instance
[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/1435744 Title: UnicodeEncodeError in Creating instance Status in OpenStack Dashboard (Horizon): Expired Bug description: Launch instance failed , horizon error message : Danger: There was an error submitting the form. Please try again. Apache logs: [Tue Mar 24 17:31:32.200854 2015] [:error] [pid 23314:tid 140209584568064] Internal Server Error: /horizon/project/instances/launch [Tue Mar 24 17:31:32.200922 2015] [:error] [pid 23314:tid 140209584568064] Traceback (most recent call last): [Tue Mar 24 17:31:32.200931 2015] [:error] [pid 23314:tid 140209584568064] File "/usr/lib/python2.7/dist-packages/django/core/handlers/base.py", line 112, in get_response [Tue Mar 24 17:31:32.200939 2015] [:error] [pid 23314:tid 140209584568064] response = wrapped_callback(request, *callback_args, **callback_kwargs) [Tue Mar 24 17:31:32.200945 2015] [:error] [pid 23314:tid 140209584568064] File "/usr/lib/python2.7/dist-packages/horizon/decorators.py", line 36, in dec [Tue Mar 24 17:31:32.200952 2015] [:error] [pid 23314:tid 140209584568064] return view_func(request, *args, **kwargs) [Tue Mar 24 17:31:32.200958 2015] [:error] [pid 23314:tid 140209584568064] File "/usr/lib/python2.7/dist-packages/horizon/decorators.py", line 52, in dec [Tue Mar 24 17:31:32.200964 2015] [:error] [pid 23314:tid 140209584568064] return view_func(request, *args, **kwargs) [Tue Mar 24 17:31:32.200970 2015] [:error] [pid 23314:tid 140209584568064] File "/usr/lib/python2.7/dist-packages/horizon/decorators.py", line 36, in dec [Tue Mar 24 17:31:32.200977 2015] [:error] [pid 23314:tid 140209584568064] return view_func(request, *args, **kwargs) [Tue Mar 24 17:31:32.200983 2015] [:error] [pid 23314:tid 140209584568064] File "/usr/lib/python2.7/dist-packages/horizon/decorators.py", line 84, in dec [Tue Mar 24 17:31:32.200989 2015] [:error] [pid 23314:tid 140209584568064] return view_func(request, *args, **kwargs) [Tue Mar 24 17:31:32.200995 2015] [:error] [pid 23314:tid 140209584568064] File "/usr/lib/python2.7/dist-packages/django/views/generic/base.py", line 69, in view [Tue Mar 24 17:31:32.201002 2015] [:error] [pid 23314:tid 140209584568064] return self.dispatch(request, *args, **kwargs) [Tue Mar 24 17:31:32.201008 2015] [:error] [pid 23314:tid 140209584568064] File "/usr/lib/python2.7/dist-packages/django/views/generic/base.py", line 87, in dispatch [Tue Mar 24 17:31:32.201014 2015] [:error] [pid 23314:tid 140209584568064] return handler(request, *args, **kwargs) [Tue Mar 24 17:31:32.201020 2015] [:error] [pid 23314:tid 140209584568064] File "/usr/lib/python2.7/dist-packages/horizon/workflows/views.py", line 165, in post [Tue Mar 24 17:31:32.201027 2015] [:error] [pid 23314:tid 140209584568064] context = self.get_context_data(**kwargs) [Tue Mar 24 17:31:32.201033 2015] [:error] [pid 23314:tid 140209584568064] File "/usr/lib/python2.7/dist-packages/horizon/workflows/views.py", line 89, in get_context_data [Tue Mar 24 17:31:32.201039 2015] [:error] [pid 23314:tid 140209584568064] workflow = self.get_workflow() [Tue Mar 24 17:31:32.201045 2015] [:error] [pid 23314:tid 140209584568064] File "/usr/lib/python2.7/dist-packages/horizon/workflows/views.py", line 79, in get_workflow [Tue Mar 24 17:31:32.201051 2015] [:error] [pid 23314:tid 140209584568064] entry_point=entry_point) [Tue Mar 24 17:31:32.201069 2015] [:error] [pid 23314:tid 140209584568064] File "/usr/lib/python2.7/dist-packages/horizon/workflows/base.py", line 648, in __init__ [Tue Mar 24 17:31:32.201075 2015] [:error] [pid 23314:tid 140209584568064] valid = step.action.is_valid() [Tue Mar 24 17:31:32.201081 2015] [:error] [pid 23314:tid 140209584568064] File "/usr/lib/python2.7/dist-packages/django/forms/forms.py", line 129, in is_valid [Tue Mar 24 17:31:32.201086 2015] [:error] [pid 23314:tid 140209584568064] return self.is_bound and not bool(self.errors) [Tue Mar 24 17:31:32.201092 2015] [:error] [pid 23314:tid 140209584568064] File "/usr/lib/python2.7/dist-packages/django/forms/forms.py", line 121, in errors [Tue Mar 24 17:31:32.201097 2015] [:error] [pid 23314:tid 140209584568064] self.full_clean() [Tue Mar 24 17:31:32.201103 2015] [:error] [pid 23314:tid 140209584568064] File "/usr/lib/python2.7/dist-packages/django/forms/forms.py", line 274, in full_clean [Tue Mar 24 17:31:32.201108 2015] [:error] [pid 23314:tid 140209584568064] self._clean_form() [Tue Mar 24 17:31:32.201113 2015] [:error] [pid 23314:tid 140209584568064] File "/usr/lib/python2.7/dist-packages/dja
[Yahoo-eng-team] [Bug 1449111] Re: Horizon doesn't accept changes / authentication issue
[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/1449111 Title: Horizon doesn't accept changes / authentication issue Status in OpenStack Dashboard (Horizon): Expired Bug description: Completed a fresh install using instructions [1] up till where it said to use launchpad as we installed it on a single server to start with. After install, I am able to access Juju and Horizon with no problems. If I try to make a change in horizon, it will seem to take it, but not long after I will start to see a list of errors along of the lines of "unable to retrieve x" and "unauthorized" while logged in with the main login which shows up in openstack-status. if I logout, or if someone else tries to login after these messages show up, it shows an unsuccessful login at first, and then shows an authentication error issue. Seen this on a few forums as being related to cinder user not being setup in mysql, haven't been able to confirm that is the root cause yet. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1449111/+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 1497954] Re: Error in instance launch, when boot from volume is selected
[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/1497954 Title: Error in instance launch, when boot from volume is selected Status in OpenStack Dashboard (Horizon): Expired Bug description: Open stack Horizon ( Master Branch ) 1. Click on Launch Instance (Instances panel) 2. Instance boot source : Boot from volume 3. Select the required volume 4. Fill all necessary details 5. Launch Getting error message : Error : Unable to launch instance named "xrz". Please see the attached image below in the comment. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1497954/+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 1500994] Re: Json parameter is converted from double quotes to single quotes - Error on launch
[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/1500994
Title:
Json parameter is converted from double quotes to single quotes -
Error on launch
Status in OpenStack Dashboard (Horizon):
Expired
Bug description:
I created a json parameter with a default value in my template:
{"somekey" : "somevalue"}
When I launch the stack in Horizon, it changes the json value to be:
{u'somekey': u'somevalue'}
But this is invalid, because when I try to launch it tells me: Error:
ERROR: Value must be valid JSON: Expecting property name enclosed in
double quotes: line 1 column 2 (char 1)
Resolution: Don't translate the quotes in the json parameter default
value at launch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1500994/+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 1571150] Re: login as admin to projects fails
[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 Identity (keystone). https://bugs.launchpad.net/bugs/1571150 Title: login as admin to projects fails Status in OpenStack Dashboard (Horizon): Expired Status in OpenStack Identity (keystone): Expired Bug description: create project: 1)login as admin. 2)add project, add admin as member to that project. 3)logout recreate bug: 2.1)login as admin. 2.2)from "projects" on top left choose the project. 2.3)you are "unauthorized" and sent out 2.4)try login again (no change to url) - unsuccessful ... 2.5)change url back to root level, login again, and you are now authorized inside the project. repeat 2.1 to 2.5 many times same results To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1571150/+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 1571150] Re: login as admin to projects fails
[Expired for OpenStack Identity (keystone) because there has been no activity for 60 days.] ** Changed in: keystone Status: Incomplete => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone). https://bugs.launchpad.net/bugs/1571150 Title: login as admin to projects fails Status in OpenStack Dashboard (Horizon): Expired Status in OpenStack Identity (keystone): Expired Bug description: create project: 1)login as admin. 2)add project, add admin as member to that project. 3)logout recreate bug: 2.1)login as admin. 2.2)from "projects" on top left choose the project. 2.3)you are "unauthorized" and sent out 2.4)try login again (no change to url) - unsuccessful ... 2.5)change url back to root level, login again, and you are now authorized inside the project. repeat 2.1 to 2.5 many times same results To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1571150/+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 1508942] Re: Events for create/update/delete floating IP address do not contain an instance ID
[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/1508942 Title: Events for create/update/delete floating IP address do not contain an instance ID Status in neutron: Expired Bug description: At the moment the update events for a floating IP address do not contain an instance ID. I think it makes sense to include the instance ID in the payload of the generated event to simplify the processing of those events in 3rd party applications. At the moment the payload only contains the port ID when associating a floating IP address with an instance. When disassociating a floating IP address there is no port ID included in the payload. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1508942/+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 1526577] Re: Wrong Allocation Pools will disable the 'Next' button
[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/1526577 Title: Wrong Allocation Pools will disable the 'Next' button Status in OpenStack Dashboard (Horizon): Expired Bug description: When create a new network, if user give a wrong Allocation Pools by typo, then user will get an error. And the 'Create' button turned to be 'Next' button and in disabled mode. However, at that moment, even user fix the wrong pools, user will still have to go back instead of let the user try again at current page. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1526577/+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 1571643] Re: Vmware : snapshot failed to restore with original VM flavor
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
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/1571643
Title:
Vmware : snapshot failed to restore with original VM flavor
Status in OpenStack Compute (nova):
Expired
Bug description:
When I try to restore a Swift snapshot of a VMware instance, it fails if the
flavor has not a bigger root size than the original flavor.
If the flavor has a bigger disk, it works without any error.
I'm on Kilo release, with vsphere 6.
Do you have any idea what is going wrong ?
Thanks by advance,
There is the original flavor of the VM :
++--+
| Property | Value|
++--+
| disk | 3|
| extra_specs| {} |
| id | 5dce9c86-7a5d-446a-b3bd-deb6066636e5 |
| name | m1.small |
| os-flavor-access:is_public | True |
| ram| 2048 |
| rxtx_factor| 1.0 |
| swap | |
| vcpus | 1|
++--+
the original image :
++--+
| Property | Value|
++--+
| Property 'hypervisor_type' | vmware |
| checksum | 1ca0d617522ea27718ee9e4924f99737 |
| container_format | bare |
| created_at | 2016-03-01T15:59:23.00 |
| deleted| False|
| disk_format| vmdk |
| id | 364512f1-2912-4b77-a59c-66a1e58340c4 |
| is_public | True |
| min_disk | 1|
| min_ram| 0|
| name | Debian VMDK |
| owner | 19cbfe88e1f04f8f94d5b6eb83d5d703 |
| protected | False|
| size | 1073741824 |
| status | active |
| updated_at | 2016-04-15T14:30:56.00 |
++--+
The snapshoted image :
+-+--+
| Property| Value|
+-+--+
| Property 'base_image_ref' | 364512f1-2912-4b77-a59c-66a1e58340c4 |
| Property 'hypervisor_type' | vmware |
| Property 'image_type' | snapshot |
| Property 'instance_uuid'| 12bdca62-215c-406d-8190-ee40f5503268 |
| Property 'owner_id' | 19cbfe88e1f04f8f94d5b6eb83d5d703 |
| Property 'user_id' | afe3cfedd2ec407f882dfeab817c784e |
| Property 'vmware_disktype' | streamOptimized |
| Property 'vmware_image_version' | 1|
| checksum| 4288105090d9289a5ec2bc62983dfd7e |
| container_format| bare |
| created_at | 2016-04-15T15:02:41.00 |
| deleted | False|
| disk_format | vmdk |
| id | e64270b9-64d5-4445-bd5d-461666c0b94c |
| is_public | False|
| min_disk| 3|
| min_ram | 0|
| name| vmware snap |
| owner | 19cbfe88e1f04f8f94d5b6eb83d5d703 |
| protected | False
[Yahoo-eng-team] [Bug 1593967] Re: neutron command need filtering
Transition to OSC is in progress: http://docs.openstack.org/developer /python-neutronclient/devref/transition_to_osc.html ** 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/1593967 Title: neutron command need filtering Status in neutron: Invalid Bug description: When existing many neutron ports, it will cost much time to list port. We need filtering this ports by host_id/device_owner/security_groups and so on. Now when using nova command it could filtering name/host and many more. Neutron lack this. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1593967/+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 1568708] Re: translation sync broken due to wrong usage of venv
** Also affects: sahara/mitaka Importance: Undecided Status: New ** Changed in: sahara/mitaka Importance: Undecided => High ** Changed in: sahara/mitaka Assignee: (unassigned) => Vitaly Gridnev (vgridnev) ** Changed in: sahara/mitaka Status: New => In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1568708 Title: translation sync broken due to wrong usage of venv Status in networking-midonet: In Progress Status in networking-ovn: Confirmed Status in neutron: Fix Committed Status in Sahara: Fix Released Status in Sahara mitaka series: In Progress Bug description: post jobs cannot use zuul-cloner and have no access currently to upper-constraints. See how nova or neutron itself handle this. Right now the sync with translations fails: https://jenkins.openstack.org/job/neutron-fwaas-propose-translation- update/119/console Please fix venv tox environment. To manage notifications about this bug go to: https://bugs.launchpad.net/networking-midonet/+bug/1568708/+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 1593967] [NEW] neutron command need filtering
Public bug reported: When existing many neutron ports, it will cost much time to list port. We need filtering this ports by host_id/device_owner/security_groups and so on. Now when using nova command it could filtering name/host and many more. Neutron lack this. ** 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/1593967 Title: neutron command need filtering Status in neutron: New Bug description: When existing many neutron ports, it will cost much time to list port. We need filtering this ports by host_id/device_owner/security_groups and so on. Now when using nova command it could filtering name/host and many more. Neutron lack this. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1593967/+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 1423644] Re: CPU/MEM usage not accurate. Hits quotas while resources are available
** Changed in: ubuntu 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/1423644 Title: CPU/MEM usage not accurate. Hits quotas while resources are available Status in Juno: Invalid Status in OpenStack Compute (nova): Won't Fix Status in Ubuntu: Invalid Bug description: I tried to set my quotas to exactly the hardware specs of my compute node for accurate reporting. My compute node runs on bare metal. After I did this I got quotas exceeded, unable to launch instance. I checked the hypervisor from the web interface and cli. 5 of 12 VCPUs used and 6GB of 16GB used. When you try and change the quotas to match the hardware it errors. From the CLI it reports that quota cant be set to 12 VCPUs because 17 are in use. Same with mem says 17GB are in use. But they arent in use clearly. So the bandaid is to set the quotas really high and then it ignores them and allows you to create instances against the actual nova usage stats. This also causes some failure to launch instance errors, no host is available meaning there arent enough resources even though there are. Im running this as a production environment for my domain so I have spent hundreds of hours chasing my tail. Hope this is helpful for debugging the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/juno/+bug/1423644/+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 1411480] Re: remain "BUILD" status when instance with force-host failed to create
The problem is no longer happening. ** Changed in: nova Status: Confirmed => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1411480 Title: remain "BUILD" status when instance with force-host failed to create Status in OpenStack Compute (nova): Invalid Bug description: The state "BUILD" remained when instance with force-host failed to create. Till the period task "_check_instance_build_time" change the state "BUILD" to "ERROR". # nova list +--+---+++-+---+ | ID | Name | Status | Task State | Power State | Networks | +--+---+++-+---+ | 2d14b1b3-fa57-4953-b226-40076f78e9ac | instanceA | ACTIVE | - | Running | net-test=192.168.0.23 | | fcc745de-a15d-47c4-9167-153eb73a4c9b | instanceB | BUILD | - | NOSTATE | | +--+---+++-+---+ reproduce: 1. create one instance group with policy "anti-affinity", named "group-anti-affinity"; 2. create one instance with "--hint group=group-anti-affinity", hosted on hostA; 3. create another instance with "--hint group=group-anti-affinity", force it to hostA; To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1411480/+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
