[Yahoo-eng-team] [Bug 1240045] Re: Weak service state probe algorithm
See step 1, bullet 3 in the docs for setting up a compute node: http://docs.openstack.org/havana/install-guide/install/yum/content/nova- compute.html "Synchronize from the controller node. Follow the instructions in the section called “Network Time Protocol (NTP)”." ** Tags added: compute ** Changed in: nova Status: New => Opinion -- 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/1240045 Title: Weak service state probe algorithm Status in OpenStack Compute (Nova): Opinion Bug description: I've faced with problem when service state of compute node got from nova-manage service list command was XXX most time and some times it was ok, despite in fact compute was ok all time. I found that it coused by time shift between controller and compute node. I think that is the bug to treat node as down basing only on update time, because if we try to ping, probe tcp port or any other real ways to conversate with node we will found it ok. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1240045/+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 1251538] Re: create/update of v3 servers return 422 when input is invalid
It's the same way in the v2 API. There are other APIs doing the same thing too. Maybe a discussion for nova on the dev mailing list? ** Tags added: api ** Changed in: nova Status: New => Opinion -- 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/1251538 Title: create/update of v3 servers return 422 when input is invalid Status in OpenStack Compute (Nova): Opinion Bug description: In v3 servers core api, create and update will return 422 when input is invalid. if not self.is_valid_body(body, 'server'): raise exc.HTTPUnprocessableEntity() We prefer use 400 for this case in v3 api. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1251538/+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 1250332] Re: How to enable jumbo frames for nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver
Please post support requests like this to the general mailing list: https://wiki.openstack.org/wiki/Mailing_Lists#General_List ** Changed in: nova Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1250332 Title: How to enable jumbo frames for nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver Status in OpenStack Compute (Nova): Invalid Bug description: Hi list, I'm working under CentOS 6.4 + Havana. I'm trying to enable jumbo frames for Openstack instances. I'm using libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver in nova.conf I noticed there is a parameter in plugins/openvswitch/ovs_neutron_plugin.ini I can use, so I set it to: veth_mtu = 9000 And, it works fine : ip link |grep 9000 6: eth4: mtu 9000 qdisc mq state UP qlen 1000 263: phy-br-eth4: mtu 9000 qdisc pfifo_fast state UP qlen 1000 264: int-br-eth4: mtu 9000 qdisc pfifo_fast state UP qlen 1000 10: br-eth4: mtu 9000 qdisc noqueue state UNKNOWN But, after the instance booted, all ports used for the instance are still MTU=1500: ip link |grep df6a018a-0d 273: qbrdf6a018a-0d: mtu 1500 qdisc noqueue state UNKNOWN 274: qvodf6a018a-0d: mtu 1500 qdisc pfifo_fast state UP qlen 1000 275: qvbdf6a018a-0d: mtu 1500 qdisc pfifo_fast state UP qlen 1000 276: tapdf6a018a-0d: mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 500 So I have to 1. find the exact ports using by the instance 2. change there MTU one by one 3. login to the instance to change the MTU Is there're way that can make sure after the instance booted, all ports have MTU=9000 ?? Thanks. -chen To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1250332/+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 1220345] Re: TypeError at /admin/routers/ issubclass() arg 1 must be a class
[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/1220345
Title:
TypeError at /admin/routers/ issubclass() arg 1 must be a class
Status in OpenStack Dashboard (Horizon):
Expired
Bug description:
I've included the django debug page,
$ neutron router-list
+--+---+-+
| id | name | external_gateway_info
|
+--+---+-+
| d54ec5f0-1afa-4b38-a27b-5994425c04ed | my router | {"network_id":
"4783f398-8a7e-4e50-8b6f-6141df053d6a", "enable_snat": true} |
+--+---+-+
$ neutron net-list
+--++-+
| id | name | subnets
|
+--++-+
| 4783f398-8a7e-4e50-8b6f-6141df053d6a | public |
7595b3d5-2086-48b2-ab08-e4bdccc587ed 192.168.1.0/24 |
+--++-+
$ neutron port-list
+--+--+---++
| id | name | mac_address | fixed_ips
|
+--+--+---++
| 7f2d6932-a306-4b0c-9d8c-84731e886e45 | | fa:16:3e:14:ac:ee |
{"subnet_id": "7595b3d5-2086-48b2-ab08-e4bdccc587ed", "ip_address":
"192.1.1.2"} |
+--+--+---+
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1220345/+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 1221316] Re: Present an error message from backend when some User operation 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 Dashboard (Horizon). https://bugs.launchpad.net/bugs/1221316 Title: Present an error message from backend when some User operation fails Status in OpenStack Dashboard (Horizon): Expired Bug description: When any Create/Update/Delete operation is performed over User entry thru the Horizon and some error happens, the message presented to the user is not helpful without giving better directions on what caused the failure. Would be more useful if the message had a more meaningful text. It could be accomplished presenting the error message sent from the backend exception that caused the failure. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1221316/+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 1221319] Re: Present an error message from backend when some Group operation 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 Dashboard (Horizon). https://bugs.launchpad.net/bugs/1221319 Title: Present an error message from backend when some Group operation fails Status in OpenStack Dashboard (Horizon): Expired Bug description: When any Create/Update/Delete operation is performed over Group entry (on v3) thru the Horizon and some error happens, the message presented to the user is not helpful without giving better directions on what caused the failure. Would be more useful if the message had a more meaningful text. It could be accomplished presenting the error message sent from the backend exception that caused the failure. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1221319/+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
