[Yahoo-eng-team] [Bug 1617499] [NEW] DBDeadlock occurs when multiple neutron server starts at the same time
kages/MySQLdb/cursors.py", line 206, in
executemany
2016-08-27 00:32:11.937 193309 ERROR neutron r = r + self.execute(query, a)
2016-08-27 00:32:11.937 193309 ERROR neutron File
"/usr/lib64/python2.7/site-packages/MySQLdb/cursors.py", line 174, in execute
2016-08-27 00:32:11.937 193309 ERROR neutron self.errorhandler(self, exc,
value)
2016-08-27 00:32:11.937 193309 ERROR neutron File
"/usr/lib64/python2.7/site-packages/MySQLdb/connections.py", line 36, in
defaulterrorhandler
2016-08-27 00:32:11.937 193309 ERROR neutron raise errorclass, errorvalue
2016-08-27 00:32:11.937 193309 ERROR neutron DBDeadlock:
(_mysql_exceptions.OperationalError) (1213, 'Deadlock found when trying to get
lock; try restarting transaction') [SQL: u'INSERT INTO ml2_vlan_allocations
(physical_network, vlan_id, allocated) VALUES (%s, %s, %s)'] [parameters:
(('bond0', 1, 0), ('bond0', 2, 0), ('bond0', 3, 0), ('bond0', 4, 0), ('bond0',
5, 0), ('bond0', 6, 0), ('bond0', 7, 0), ('bond0', 8, 0) ... displaying 10 of
4095 total bound parameter sets ... ('bond0', 4094, 0), ('bond0', 4095, 0))]
The problem occurs more oftern under this following situation:
1. network_vlan_ranges is large (My condition is from 1 to 4095)
2. slow controller
** Affects: neutron
Importance: Undecided
Assignee: Kahou Lei (kahou82)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Kahou Lei (kahou82)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1617499
Title:
DBDeadlock occurs when multiple neutron server starts at the same time
Status in neutron:
New
Bug description:
I have multiple controllers and each controllers are running neutron-
server. When I start the neutron-server, some of the controllers
occasionally crash with DBDeadlock exceptions:
2016-08-27 00:32:11.937 193309 CRITICAL neutron [-] DBDeadlock:
(_mysql_exceptions.OperationalError) (1213, 'Deadlock found when trying to get
lock; try restarting transaction') [SQL: u'INSERT INTO ml2_vlan_allocations
(physical_network, vlan_id, allocated) VALUES (%s, %s, %s)'] [parameters:
(('bond0', 1, 0), ('bond0', 2, 0), ('bond0', 3, 0), ('bond0', 4, 0), ('bond0',
5, 0), ('bond0', 6, 0), ('bond0', 7, 0), ('bond0', 8, 0) ... displaying 10 of
4095 total bound parameter sets ... ('bond0', 4094, 0), ('bond0', 4095, 0))]
2016-08-27 00:32:11.937 193309 ERROR neutron Traceback (most recent call
last):
2016-08-27 00:32:11.937 193309 ERROR neutron File
"/usr/bin/neutron-server", line 10, in
2016-08-27 00:32:11.937 193309 ERROR neutron
sys.exit(main_wsgi_eventlet())
2016-08-27 00:32:11.937 193309 ERROR neutron File
"/usr/lib/python2.7/site-packages/neutron/cmd/eventlet/server/__init__.py",
line 19, in main_wsgi_eventlet
2016-08-27 00:32:11.937 193309 ERROR neutron wsgi_eventlet.main()
2016-08-27 00:32:11.937 193309 ERROR neutron File
"/usr/lib/python2.7/site-packages/neutron/server/wsgi_eventlet.py", line 50, in
main
2016-08-27 00:32:11.937 193309 ERROR neutron
server.boot_server(_eventlet_wsgi_server)
2016-08-27 00:32:11.937 193309 ERROR neutron File
"/usr/lib/python2.7/site-packages/neutron/server/__init__.py", line 35, in
boot_server
2016-08-27 00:32:11.937 193309 ERROR neutron server_func()
2016-08-27 00:32:11.937 193309 ERROR neutron File
"/usr/lib/python2.7/site-packages/neutron/server/wsgi_eventlet.py", line 27, in
_eventlet_wsgi_server
2016-08-27 00:32:11.937 193309 ERROR neutron neutron_api =
service.serve_wsgi(service.NeutronApiService)
2016-08-27 00:32:11.937 193309 ERROR neutron File
"/usr/lib/python2.7/site-packages/neutron/service.py", line 117, in serve_wsgi
2016-08-27 00:32:11.937 193309 ERROR neutron
LOG.exception(_LE('Unrecoverable error: please check log '
2016-08-27 00:32:11.937 193309 ERROR neutron File
"/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 204, in __exit__
2016-08-27 00:32:11.937 193309 ERROR neutron six.reraise(self.type_,
self.value, self.tb)
2016-08-27 00:32:11.937 193309 ERROR neutron File
"/usr/lib/python2.7/site-packages/neutron/service.py", line 114, in serve_wsgi
2016-08-27 00:32:11.937 193309 ERROR neutron service.start()
2016-08-27 00:32:11.937 193309 ERROR neutron File
"/usr/lib/python2.7/site-packages/neutron/service.py", line 87, in start
2016-08-27 00:32:11.937 193309 ERROR neutron self.wsgi_app =
_run_wsgi(self.app_name)
2016-08-27 00:32:11.937 193309 ERROR neutron File
"/usr/lib/python2.
[Yahoo-eng-team] [Bug 1597861] [NEW] Cannot install mac spoofing for allowed_address_pairs if port mac address is unavaliable
Public bug reported: From https://github.com/openstack/neutron/blob/3e26a7851e10d0bae5625c042e8f5f0f74ed327e/neutron/plugins/ml2/drivers/linuxbridge/agent/arp_protect.py#L133-L134, if the port_details mac address is not presented I cannot install the allowed_address_pairs mac protection. Since mac address is not a required field in port model, we need to add extra check for the port_details to see if the mac_address field is presented or not. ** Affects: neutron Importance: Undecided Assignee: Kahou Lei (kahou82) Status: New ** Changed in: neutron Assignee: (unassigned) => Kahou Lei (kahou82) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1597861 Title: Cannot install mac spoofing for allowed_address_pairs if port mac address is unavaliable Status in neutron: New Bug description: From https://github.com/openstack/neutron/blob/3e26a7851e10d0bae5625c042e8f5f0f74ed327e/neutron/plugins/ml2/drivers/linuxbridge/agent/arp_protect.py#L133-L134, if the port_details mac address is not presented I cannot install the allowed_address_pairs mac protection. Since mac address is not a required field in port model, we need to add extra check for the port_details to see if the mac_address field is presented or not. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1597861/+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 1571342] [NEW] Misleading variable naming is used in ldap driver
Public bug reported: In keystone/common/ldap/core.py, the get_all() method of EnabledEmuMixIn is using "tenant" as the return object. This is misleading as the core method is not using as project only but also other identity or resources (such as user and group). We should change to name to be more generic to avoid confusion. https://github.com/openstack/keystone/blob/master/keystone/common/ldap/core.py#L1921-L1932 ** Affects: keystone Importance: Undecided Assignee: Kahou Lei (kahou82) Status: In Progress -- 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/1571342 Title: Misleading variable naming is used in ldap driver Status in OpenStack Identity (keystone): In Progress Bug description: In keystone/common/ldap/core.py, the get_all() method of EnabledEmuMixIn is using "tenant" as the return object. This is misleading as the core method is not using as project only but also other identity or resources (such as user and group). We should change to name to be more generic to avoid confusion. https://github.com/openstack/keystone/blob/master/keystone/common/ldap/core.py#L1921-L1932 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1571342/+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 1505414] [NEW] Broken error message during subnet creation
Public bug reported: Whenever user create a Neutron subnet and Neutron returns error, Horizon will display : Error: Failed to create subnet "90.0.0.0/24" for network "None": Notice that "None" is supposed to be a network name. The root cause is due to horizon/horizon/openstack_dashboard/dashboards/project/networks/subnets/workflows.py never pass Network object in the _create_subnet method and that breaks the error message. ** Affects: horizon Importance: Undecided Assignee: Kahou Lei (kahou82) Status: New ** Changed in: horizon Assignee: (unassigned) => Kahou Lei (kahou82) -- 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/1505414 Title: Broken error message during subnet creation Status in OpenStack Dashboard (Horizon): New Bug description: Whenever user create a Neutron subnet and Neutron returns error, Horizon will display : Error: Failed to create subnet "90.0.0.0/24" for network "None": Notice that "None" is supposed to be a network name. The root cause is due to horizon/horizon/openstack_dashboard/dashboards/project/networks/subnets/workflows.py never pass Network object in the _create_subnet method and that breaks the error message. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1505414/+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 1495161] [NEW] Cannot add tap interface to the bridge when bridge mappings is not provided
Public bug reported:
I am using linux bridge and I cannot add dhcp tap interface when the
bridge mappings is not provided.
Steps to reproduce:
1. Create a network
2. Create a subnet under that network
3. Observe that the dhcp port is DOWN
>From the linux bridge log:
2015-09-12 18:25:28.857 ERROR
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
[req-9cf39db9-
5071-4b9a-bcb6-908f759de0f4 None None] Error in agent loop. Devices info:
{'current': set(['tap895fe52f-0d', 'tapb2d
9e954-de', 'tap20a094ab-24', 'tap8aebc9c0-89', 'tap108580e4-6f',
'tapd4feefc5-f4']), 'removed': set([]), 'added': se
t(['tap895fe52f-0d', 'tapb2d9e954-de', 'tap20a094ab-24', 'tap8aebc9c0-89',
'tap108580e4-6f', 'tapd4feefc5-f4']), 'up
dated': set([])}
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
Traceback (mos
t recent call last):
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent File
"/opt/s
tack/neutron/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py",
line 1110, in daemon_loop
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
sync = sel
f.process_network_devices(device_info)
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent File
"/opt/s
tack/neutron/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py",
line 959, in process_netwo
rk_devices
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
resync_a =
self.treat_devices_added_updated(devices_added_updated)
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent File
"/opt/s
tack/neutron/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py",
line 998, in treat_devices
_added_updated
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
device_det
ails['port_id']):
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent File
"/opt/s
tack/neutron/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py",
line 501, in add_interface
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
tap_device
_name)
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent File
"/opt/s
tack/neutron/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py",
line 479, in add_tap_inter
face
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent if
bridge_
lib.BridgeDevice(bridge_name).addif(tap_device_name):
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent File
"/opt/s
tack/neutron/neutron/agent/linux/bridge_lib.py", line 38, in addif
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
return sel
f._brctl(['addif', self.name, interface])
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent File
"/opt/s
tack/neutron/neutron/agent/linux/bridge_lib.py", line 26, in _brctl
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
return ip_
wrapper.netns.execute(cmd, run_as_root=True)
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent File
"/opt/s
tack/neutron/neutron/agent/linux/ip_lib.py", line 795, in execute
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
extra_ok_c
odes=extra_ok_codes, **kwargs)
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent File
"/opt/s
tack/neutron/neutron/agent/linux/utils.py", line 160, in execute
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
raise Runt
imeError(m)
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
RuntimeError:
2015-09-12 18:25:28.857 TRACE
neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent
Command: ['brc
tl', 'addif', None, u'tapb2d9e954-de']
>From the code, looks like we need to provide bridge mapping when the
interface mapping is provided:
https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/linuxbridge/agent/linuxbridge_neutron_agent.py#L456-L459
But this is not the case as it works in Kilo as bridge mapping option
doesn't exist until Liberty.
Neutron version : Liberty
Attached local.conf here
** Affects: neutron
Importance: Undecided
Status: New
** Attachment added: "local
[Yahoo-eng-team] [Bug 1485144] [NEW] User cannot create an admin network without knowing the physical network name
Public bug reported: Currently user cannot create an admin network without knowing the physical network name. It will be more convenient if the physical network field is a choice field such that user can choose the name from the list. Steps to reproduce: 1. Go to Admin -> Network 2. Click create network 3. You will notice that the physical network field is a text field ** Affects: horizon Importance: Undecided Assignee: Ying Zuo (yinzuo) 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/1485144 Title: User cannot create an admin network without knowing the physical network name Status in OpenStack Dashboard (Horizon): New Bug description: Currently user cannot create an admin network without knowing the physical network name. It will be more convenient if the physical network field is a choice field such that user can choose the name from the list. Steps to reproduce: 1. Go to Admin -> Network 2. Click create network 3. You will notice that the physical network field is a text field To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1485144/+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 1484636] [NEW] User cannot create network if network_vlan_ranges is not specified
Public bug reported: Steps to reproduce: 1. In ml2_conf.ini, set the network_vlan_ranges as phy1 (phy1 is your physical network mapping) 2. Restart neutron server 3. Run "neutron net-create NET-1" 4. You will see "Service Unavaliable" error 5. Run "neutron net-create NET-1 --provider:network_type vlan --provider:physical_network phy1 --provider:segmentation_id 2000 Network from step 5 will be created successfully. The problem is that if user doesn't specify network_vlan_ranges, does it mean user cannot create any VLAN? or Does it mean user can create any VLAN (from 1 to 4096)? If it is the second case, that means we have bug on Step 3. ** Affects: neutron Importance: Undecided Assignee: Kahou Lei (kahou82) Status: New ** Changed in: neutron Assignee: (unassigned) => Kahou Lei (kahou82) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1484636 Title: User cannot create network if network_vlan_ranges is not specified Status in neutron: New Bug description: Steps to reproduce: 1. In ml2_conf.ini, set the network_vlan_ranges as phy1 (phy1 is your physical network mapping) 2. Restart neutron server 3. Run "neutron net-create NET-1" 4. You will see "Service Unavaliable" error 5. Run "neutron net-create NET-1 --provider:network_type vlan --provider:physical_network phy1 --provider:segmentation_id 2000 Network from step 5 will be created successfully. The problem is that if user doesn't specify network_vlan_ranges, does it mean user cannot create any VLAN? or Does it mean user can create any VLAN (from 1 to 4096)? If it is the second case, that means we have bug on Step 3. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1484636/+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 1475786] [NEW] Cannot ping to a same subnet VM via floating IP
Public bug reported: Suppose I have two VMs running and they are under the same subnet, they are assigned with the floating IPs. (See attached image). I am using nova network model. I cannot get ping working if I ping from one VM to another VM via the floating IP. Ping to another vm which resides in another subnet via floating IP seems fine. I did some investigation, looks like the packet is being dropped after the PREROUTING rules. Here is the modprobe iptable log: Jul 17 10:15:40 localhost kernel: [ 1846.629048] TRACE: raw:PREROUTING:rule:2 IN=br100 OUT= PHYSIN=vlan100 MAC=fa:16:3e:c2:b9:7d:fa:16:3e:dd:e7:c9:08:00 SRC=10.0.0.3 DST=172.24.4.2 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=3620 DF PROTO=ICMP TYPE=8 CODE=0 ID=8705 SEQ=0 Jul 17 10:15:40 localhost kernel: [ 1846.629055] TRACE: raw:PREROUTING:policy:3 IN=br100 OUT= PHYSIN=vlan100 MAC=fa:16:3e:c2:b9:7d:fa:16:3e:dd:e7:c9:08:00 SRC=10.0.0.3 DST=172.24.4.2 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=3620 DF PROTO=ICMP TYPE=8 CODE=0 ID=8705 SEQ=0 Jul 17 10:15:40 localhost kernel: [ 1846.629063] TRACE: mangle:PREROUTING:policy:1 IN=br100 OUT= PHYSIN=vlan100 MAC=fa:16:3e:c2:b9:7d:fa:16:3e:dd:e7:c9:08:00 SRC=10.0.0.3 DST=172.24.4.2 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=3620 DF PROTO=ICMP TYPE=8 CODE=0 ID=8705 SEQ=0 Jul 17 10:15:40 localhost kernel: [ 1846.629068] TRACE: nat:PREROUTING:rule:1 IN=br100 OUT= PHYSIN=vlan100 MAC=fa:16:3e:c2:b9:7d:fa:16:3e:dd:e7:c9:08:00 SRC=10.0.0.3 DST=172.24.4.2 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=3620 DF PROTO=ICMP TYPE=8 CODE=0 ID=8705 SEQ=0 Jul 17 10:15:40 localhost kernel: [ 1846.629074] TRACE: nat:nova-network-PREROUTING:rule:3 IN=br100 OUT= PHYSIN=vlan100 MAC=fa:16:3e:c2:b9:7d:fa:16:3e:dd:e7:c9:08:00 SRC=10.0.0.3 DST=172.24.4.2 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=3620 DF PROTO=ICMP TYPE=8 CODE=0 ID=8705 SEQ=0 And from the iptables counter, nothing got incremented after the PREROUTING rule: sudo iptables -t nat -L -v -n Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 184 nova-network-PREROUTING all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 nova-api-PREROUTING all -- * * 0.0.0.0/0 0.0.0.0/0 Chain INPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 nova-network-OUTPUT all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 nova-api-OUTPUT all -- * * 0.0.0.0/0 0.0.0.0/0 Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 nova-network-POSTROUTING all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 nova-api-POSTROUTING all -- * * 0.0.0.0/0 0.0.0.0/0 0 0 nova-postrouting-bottom all -- * * 0.0.0.0/0 0.0.0.0/0 Chain nova-api-OUTPUT (1 references) pkts bytes target prot opt in out source destination Chain nova-api-POSTROUTING (1 references) pkts bytes target prot opt in out source destination Chain nova-api-PREROUTING (1 references) pkts bytes target prot opt in out source destination Chain nova-api-float-snat (1 references) pkts bytes target prot opt in out source destination Chain nova-api-snat (1 references) pkts bytes target prot opt in out source destination 0 0 nova-api-float-snat all -- * * 0.0.0.0/0 0.0.0.0/0 Chain nova-network-OUTPUT (1 references) pkts bytes target prot opt in out source destination 0 0 DNAT all -- * * 0.0.0.0/0172.24.4.1 to:11.0.0.3 0 0 DNAT all -- * * 0.0.0.0/0172.24.4.2 to:10.0.0.4 0 0 DNAT all -- * * 0.0.0.0/0172.24.4.3 to:10.0.0.3 0 0 DNAT all -- * * 0.0.0.0/0172.24.4.4 to:11.0.0.4 Chain nova-network-POSTROUTING (1 references) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- * * 10.0.0.0/24 192.168.62.100 0 0 ACCEPT all -- * * 10.0.0.0/24 10.0.0.0/24 ! ctstate DNAT 0 0 ACCEPT all -- * * 11.0.0.0/24 192.168.62.100 0 0 ACCEPT all -- * * 11.0.0.0/24
[Yahoo-eng-team] [Bug 1460866] [NEW] Hypervisor stats is incorrect in Hozion
Public bug reported: >From the Admin -> Hypervisor panel, I notice that the Hypervisort stats is converted from megabyte to Gibibyte. However, the calculation seems incorrect. Here is my observation: >From nova CLI: vagrant@precise64:~/devstack$ nova hypervisor-stats +--+---+ | Property | Value | +--+---+ | count| 1 | | current_workload | 0 | | disk_available_least | -49 | | free_disk_gb | -43 | | free_ram_mb | -1236 | | local_gb | 38| | local_gb_used| 81| | memory_mb| 7980 | | memory_mb_used | 9216 | | running_vms | 3 | | vcpus| 4 | | vcpus_used | 5 | +--+---+ Where as the member_mb is 7980 On the horizon side, it is converted to 7.8 GB (See attached and GB is Gibibyte). However, if you go to google and convert the value, it is 7.43 GB (Gibibyte). https://www.google.com/search?q=megabyte+to+gigabyte&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla :en-US:official&client=firefox-a&channel=sb#rls=org.mozilla:en- US:official&channel=sb&q=7980+megabyte+to+gibibyte Note: you will see my hypervisor stats is oversubscribed. Please ignore that as this bug is only against the calculation problem. ** Affects: horizon Importance: Undecided Assignee: Kahou Lei (kahou82) Status: New ** Attachment added: "Screen Shot 2015-06-01 at 6.17.35 PM.png" https://bugs.launchpad.net/bugs/1460866/+attachment/4408364/+files/Screen%20Shot%202015-06-01%20at%206.17.35%20PM.png ** Changed in: horizon Assignee: (unassigned) => Kahou Lei (kahou82) -- 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/1460866 Title: Hypervisor stats is incorrect in Hozion Status in OpenStack Dashboard (Horizon): New Bug description: From the Admin -> Hypervisor panel, I notice that the Hypervisort stats is converted from megabyte to Gibibyte. However, the calculation seems incorrect. Here is my observation: From nova CLI: vagrant@precise64:~/devstack$ nova hypervisor-stats +--+---+ | Property | Value | +--+---+ | count| 1 | | current_workload | 0 | | disk_available_least | -49 | | free_disk_gb | -43 | | free_ram_mb | -1236 | | local_gb | 38| | local_gb_used| 81| | memory_mb| 7980 | | memory_mb_used | 9216 | | running_vms | 3 | | vcpus| 4 | | vcpus_used | 5 | +--+---+ Where as the member_mb is 7980 On the horizon side, it is converted to 7.8 GB (See attached and GB is Gibibyte). However, if you go to google and convert the value, it is 7.43 GB (Gibibyte). https://www.google.com/search?q=megabyte+to+gigabyte&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla :en-US:official&client=firefox-a&channel=sb#rls=org.mozilla:en- US:official&channel=sb&q=7980+megabyte+to+gibibyte Note: you will see my hypervisor stats is oversubscribed. Please ignore that as this bug is only against the calculation problem. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1460866/+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 1459400] [NEW] Modal form is not working anymore
Public bug reported: With the latest upstream, modal form seems not working anymore. See attached ** Affects: horizon Importance: Undecided Assignee: Kahou Lei (kahou82) Status: New ** Attachment added: "Screen Shot 2015-05-27 at 12.13.15 PM.png" https://bugs.launchpad.net/bugs/1459400/+attachment/4405768/+files/Screen%20Shot%202015-05-27%20at%2012.13.15%20PM.png -- 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/1459400 Title: Modal form is not working anymore Status in OpenStack Dashboard (Horizon): New Bug description: With the latest upstream, modal form seems not working anymore. See attached To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1459400/+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 1458973] [NEW] Edit Port form should display current attached device_id and device_owner values
Public bug reported: Currently when user want to edit the port information, the port update form doesn't display the current attached device_id and device_owner value. This will make user inconvenient to update the port info as user needs to put back the device_id and device_owner value in the port update form. One common use case is that user wants to update the port name: 1. Select the port. 2. Edit port. 3. Input a new port name. 4. Click Save. After that, you will see the port is detached as the device_id and device_owner values are empty. ** Affects: horizon Importance: Undecided Assignee: Kahou Lei (kahou82) Status: New ** Changed in: horizon Assignee: (unassigned) => Kahou Lei (kahou82) -- 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/1458973 Title: Edit Port form should display current attached device_id and device_owner values Status in OpenStack Dashboard (Horizon): New Bug description: Currently when user want to edit the port information, the port update form doesn't display the current attached device_id and device_owner value. This will make user inconvenient to update the port info as user needs to put back the device_id and device_owner value in the port update form. One common use case is that user wants to update the port name: 1. Select the port. 2. Edit port. 3. Input a new port name. 4. Click Save. After that, you will see the port is detached as the device_id and device_owner values are empty. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1458973/+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 1458088] [NEW] Allocation Pool tooltip is truncated
Public bug reported: Steps to reproduce: 1. Network Detail -> Create Subnet. 2. Fill out necessary info, then navigate to Subnet Detail page. 3. Hover the mouse on the allocation pool help. 4. You will notice the tooltip can't display the full text. See attached ** Affects: horizon Importance: Undecided Assignee: Kahou Lei (kahou82) Status: New ** Attachment added: "Screen Shot 2015-05-22 at 4.59.31 PM.png" https://bugs.launchpad.net/bugs/1458088/+attachment/4402747/+files/Screen%20Shot%202015-05-22%20at%204.59.31%20PM.png ** Changed in: horizon Assignee: (unassigned) => Kahou Lei (kahou82) -- 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/1458088 Title: Allocation Pool tooltip is truncated Status in OpenStack Dashboard (Horizon): New Bug description: Steps to reproduce: 1. Network Detail -> Create Subnet. 2. Fill out necessary info, then navigate to Subnet Detail page. 3. Hover the mouse on the allocation pool help. 4. You will notice the tooltip can't display the full text. See attached To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1458088/+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 1458021] [NEW] Some of the fields in subnet create page are not marked as required (with asterisk)
Public bug reported: The subnet creation form doesn't indicate user which fields need to fill out and this will become problematic. Steps to reproduce: 1. On the network panel, create a network. 2. Create a subnet. 3. In the Subnet modal form, create a subnet without filling out either the subnet name or the allocation pool. 4. Click create. 5. Horizon will returns error. ** Affects: horizon Importance: Undecided Assignee: Kahou Lei (kahou82) Status: In Progress ** Changed in: horizon Assignee: (unassigned) => Kahou Lei (kahou82) -- 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/1458021 Title: Some of the fields in subnet create page are not marked as required (with asterisk) Status in OpenStack Dashboard (Horizon): In Progress Bug description: The subnet creation form doesn't indicate user which fields need to fill out and this will become problematic. Steps to reproduce: 1. On the network panel, create a network. 2. Create a subnet. 3. In the Subnet modal form, create a subnet without filling out either the subnet name or the allocation pool. 4. Click create. 5. Horizon will returns error. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1458021/+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 1433849] [NEW] Horizon crashes which user click the "Confirm resize" action multiple times while an instance is resizing
Public bug reported: Steps to reproduce: 1. Boot an instance 2. Resize that instance 3. When the instance is in Confirm resize state, click the "Confirm resize" action. 4. After the action is clicked once, the "Confirm resize" action still shows up, click it couple times. 5. You will see Horizon crashes with the following error: Cannot 'confirmResize' instance d1ba0033-4ce7-431d-a9dc-754fe0631fef while it is in vm_state active (HTTP 409) ** 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/1433849 Title: Horizon crashes which user click the "Confirm resize" action multiple times while an instance is resizing Status in OpenStack Dashboard (Horizon): New Bug description: Steps to reproduce: 1. Boot an instance 2. Resize that instance 3. When the instance is in Confirm resize state, click the "Confirm resize" action. 4. After the action is clicked once, the "Confirm resize" action still shows up, click it couple times. 5. You will see Horizon crashes with the following error: Cannot 'confirmResize' instance d1ba0033-4ce7-431d-a9dc-754fe0631fef while it is in vm_state active (HTTP 409) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1433849/+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 1433847] [NEW] Horizon crashes when a non-admin user try to resize a locked instance
Public bug reported: Steps to reproduce: 1. Login as admin 2. Boot an instance. 3. Resize that instance. 4. While that instance is in "Confirm" state, logout and login as a non-admin user. 5. Go to the instance panel and notice that the instance has "Confirm Resize" action enabled. 6. Click the action and Horizon crash. The problem is due to nova client doesn't have the lock state report to the GUI and that's why we cannot filter out the action. ** 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/1433847 Title: Horizon crashes when a non-admin user try to resize a locked instance Status in OpenStack Dashboard (Horizon): New Bug description: Steps to reproduce: 1. Login as admin 2. Boot an instance. 3. Resize that instance. 4. While that instance is in "Confirm" state, logout and login as a non-admin user. 5. Go to the instance panel and notice that the instance has "Confirm Resize" action enabled. 6. Click the action and Horizon crash. The problem is due to nova client doesn't have the lock state report to the GUI and that's why we cannot filter out the action. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1433847/+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 1432904] [NEW] Project with empty description is not sorted correctly
Public bug reported: Steps to reproduce: 1. Identity -> Project 2. In one of the project, edit the description as an empty description 3. Refresh the page and try to sort it, you will notice that the project list is sorted without including the empty description project. ** Affects: horizon Importance: Undecided Assignee: Kahou Lei (kahou82) Status: New ** Changed in: horizon Assignee: (unassigned) => Kahou Lei (kahou82) -- 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/1432904 Title: Project with empty description is not sorted correctly Status in OpenStack Dashboard (Horizon): New Bug description: Steps to reproduce: 1. Identity -> Project 2. In one of the project, edit the description as an empty description 3. Refresh the page and try to sort it, you will notice that the project list is sorted without including the empty description project. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1432904/+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 1430005] [NEW] Improve security rule notification message
Public bug reported: If we create a rule that allow all ports to go thru, we are displaying the following notification message (see attached image too): Successfully added rule: ALLOW -1:-1 from 0.0.0.0/0 whereas -1:-1 doesn't deliver useful information. Suggest to change -1:-1 to "any port" instead. ** Affects: horizon Importance: Undecided Assignee: Kahou Lei (kahou82) Status: New ** Attachment added: "Screen Shot 2015-03-09 at 1.25.38 PM.png" https://bugs.launchpad.net/bugs/1430005/+attachment/4339229/+files/Screen%20Shot%202015-03-09%20at%201.25.38%20PM.png ** Changed in: horizon Assignee: (unassigned) => Kahou Lei (kahou82) -- 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/1430005 Title: Improve security rule notification message Status in OpenStack Dashboard (Horizon): New Bug description: If we create a rule that allow all ports to go thru, we are displaying the following notification message (see attached image too): Successfully added rule: ALLOW -1:-1 from 0.0.0.0/0 whereas -1:-1 doesn't deliver useful information. Suggest to change -1:-1 to "any port" instead. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1430005/+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 1428585] Re: Filtering compute host in admin page makes an internal server error
This was fixed in this commit: https://github.com/openstack/horizon/commit/dd487f236db15fe6d6de76eb86fe98b75e2987b6 ** Changed in: horizon Status: New => Fix Released -- 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/1428585 Title: Filtering compute host in admin page makes an internal server error Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Horizon returns Internal Server Error when you push filter button in admin's compute host page. How to reproduce: 1. login as admin 2. moving System -> Hypervisors -> Compute Host 3. clicking Filter button I received following error on my browser: TemplateSyntaxError at /admin/hypervisors/ 'Service' object is not iterable Request Method: POST Request URL: http://10.10.1.10/admin/hypervisors/ Django Version: 1.6.10 Exception Type: TemplateSyntaxError Exception Value: 'Service' object is not iterable Exception Location: /opt/stack/horizon/openstack_dashboard/wsgi/../../openstack_dashboard/dashboards/admin/hypervisors/compute/tables.py in filter, line 63 Python Executable:/usr/bin/python Python Version: 2.7.6 Python Path: ['/opt/stack/horizon/openstack_dashboard/wsgi/../..', '/opt/stack/keystone', '/opt/stack/glance', '/opt/stack/cinder', '/opt/stack/neutron', '/opt/stack/nova', '/opt/stack/horizon', '/opt/stack/heat', '/usr/lib/python2.7', '/usr/lib/python2.7/plat-x86_64-linux-gnu', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/local/lib/python2.7/dist-packages', '/usr/lib/python2.7/dist-packages', '/opt/stack/horizon/openstack_dashboard'] Server time:Thu, 5 Mar 2015 10:42:18 + I attach horizon.log in this report. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1428585/+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 1427014] [NEW] Images with same created timestamp breaks paging
Public bug reported: Suppose there are several images which are created at the same timestamp, paging back and forth will mess up the order. ** Affects: horizon Importance: Undecided Assignee: Kahou Lei (kahou82) 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/1427014 Title: Images with same created timestamp breaks paging Status in OpenStack Dashboard (Horizon): New Bug description: Suppose there are several images which are created at the same timestamp, paging back and forth will mess up the order. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1427014/+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 1426604] [NEW] User cannot page backward in Project Instance table
Public bug reported: Steps to reproduce: 1. In the user settings, set the Item per page as 3. 2. On the project -> Instance page, launch 6 instances. 3. You should see 3 instances per page in the instance table. 4. Click the "Next" link. 6. Notice that the "Prev" link is missing. ** Affects: horizon Importance: Undecided Assignee: Kahou Lei (kahou82) Status: New ** Changed in: horizon Assignee: (unassigned) => Kahou Lei (kahou82) -- 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/1426604 Title: User cannot page backward in Project Instance table Status in OpenStack Dashboard (Horizon): New Bug description: Steps to reproduce: 1. In the user settings, set the Item per page as 3. 2. On the project -> Instance page, launch 6 instances. 3. You should see 3 instances per page in the instance table. 4. Click the "Next" link. 6. Notice that the "Prev" link is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1426604/+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 1426076] [NEW] Paging to the next page doesn't work after all the items in the current page are deleted
Public bug reported:
I was not able to page to the next page after I delete all the instance
of the current page.
Steps to reproduce:
1. In the user settings, set the Item per page as 3.
2. On the project -> Instance page, launch 6 instances.
3. You should see 3 instances per page in the instance table.
4. On the first page, delete all the instance at once.
5. After all the instances are deleted, click the "Next" link.
6. You should see an error saying that it cannot page to the next page.
** Affects: horizon
Importance: Undecided
Assignee: Kahou Lei (kahou82)
Status: New
** Changed in: horizon
Assignee: (unassigned) => Kahou Lei (kahou82)
** Summary changed:
- Paging to the next page doesn't work if all the items in the current page are
deleted
+ Paging to the next page doesn't work after all the items in the current page
are deleted
--
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/1426076
Title:
Paging to the next page doesn't work after all the items in the
current page are deleted
Status in OpenStack Dashboard (Horizon):
New
Bug description:
I was not able to page to the next page after I delete all the
instance of the current page.
Steps to reproduce:
1. In the user settings, set the Item per page as 3.
2. On the project -> Instance page, launch 6 instances.
3. You should see 3 instances per page in the instance table.
4. On the first page, delete all the instance at once.
5. After all the instances are deleted, click the "Next" link.
6. You should see an error saying that it cannot page to the next page.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1426076/+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 1424930] Re: Compressing an incorrect scss files
Turns out the scss compiler will do a glob if we set DEBUG = True. Therefore, it will never get the file from the static folder. Once DEBUG is set as False, everything works fine. ** Changed in: horizon Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1424930 Title: Compressing an incorrect scss files Status in OpenStack Dashboard (Horizon): Invalid Bug description: I was trying to compress the css file with some local changes. Since it is a local change, I was doing the change under the static folder (horizon/static) for testing. But I notice that the changes are not being picked up at all. Here are the steps to reproduce. 1. Run python manage.py collectstatic --noinput 2. Under horizon/static folder, open up horizon/static/bootstrap/scss/bootstrap/_variables.scss 3. Look for $brand-primary declaration, change the hex value to #00 4. Run python manage.py compress 5. Under horizon/static/dashboard/css, open up the compressed css file. 6. Look for "btn-primary", you will notice that it is still using the old value but not #00 I spent some time to debug it and turns out compressor is still importing the scss file from the xstatic installation package under the .venv folder. I tried it on devstack and my local computer and the issue stays the same. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1424930/+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 1424930] [NEW] Compressing an incorrect scss files
Public bug reported: I was trying to compress the css file with some local changes. Since it is a local change, I was doing the change under the static folder (horizon/static) for testing. But I notice that the changes are not being picked up at all. Here are the steps to reproduce. 1. Run python manage.py collectstatic --noinput 2. Under horizon/static folder, open up horizon/static/bootstrap/scss/bootstrap/_variables.scss 3. Look for $brand-primary declaration, change the hex value to #00 4. Run python manage.py compress 5. Under horizon/static/dashboard/css, open up the compressed css file. 6. Look for "btn-primary", you will notice that it is still using the old value but not #00 I spent some time to debug it and turns out compressor is still importing the scss file from the xstatic installation package under the .venv folder. I tried it on devstack and my local computer and the issue stays the same. ** 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/1424930 Title: Compressing an incorrect scss files Status in OpenStack Dashboard (Horizon): New Bug description: I was trying to compress the css file with some local changes. Since it is a local change, I was doing the change under the static folder (horizon/static) for testing. But I notice that the changes are not being picked up at all. Here are the steps to reproduce. 1. Run python manage.py collectstatic --noinput 2. Under horizon/static folder, open up horizon/static/bootstrap/scss/bootstrap/_variables.scss 3. Look for $brand-primary declaration, change the hex value to #00 4. Run python manage.py compress 5. Under horizon/static/dashboard/css, open up the compressed css file. 6. Look for "btn-primary", you will notice that it is still using the old value but not #00 I spent some time to debug it and turns out compressor is still importing the scss file from the xstatic installation package under the .venv folder. I tried it on devstack and my local computer and the issue stays the same. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1424930/+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 1424244] [NEW] Go button of the instance log page becomes disable
Public bug reported: Steps to reproduce. 1. Spin up an instance. 2. Once the instance is up, click the View Log action. 3. On the view log page, enter some valid value on the Log Length text box. 4. Click "Go" button 5. Once the page is refreshed, you will notice that the Go button become disable forever. Test it on Chrome broswer. ** Affects: horizon Importance: Undecided Assignee: Kahou Lei (kahou82) Status: New ** Changed in: horizon Assignee: (unassigned) => Kahou Lei (kahou82) ** Description changed: Steps to reproduce. 1. Spin up an instance. 2. Once the instance is up, click the View Log action. 3. On the view log page, enter some valid value on the Log Length text box. 4. Click "Go" button 5. Once the page is refreshed, you will notice that the Go button become disable forever. + + Test it on Chrome broswer. -- 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/1424244 Title: Go button of the instance log page becomes disable Status in OpenStack Dashboard (Horizon): New Bug description: Steps to reproduce. 1. Spin up an instance. 2. Once the instance is up, click the View Log action. 3. On the view log page, enter some valid value on the Log Length text box. 4. Click "Go" button 5. Once the page is refreshed, you will notice that the Go button become disable forever. Test it on Chrome broswer. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1424244/+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 1420112] [NEW] Nova doesn't show enough error message when creating a new network with a duplicate vlan ID.
Public bug reported: This happens when user tries to create a new network with a duplicate vlan ID: vagrant@ubuntu:~/devstack$ nova network-list +--+-+-+ | ID | Label | Cidr| +--+-+-+ | a16f1896-da4c-4978-9776-0b6368129b07 | private | 10.0.0.0/24 | +--+-+-+ vagrant@ubuntu:~/devstack$ nova network-show a16f1896-da4c-4978-9776-0b6368129b07 +-+--+ | Property| Value +-+--+ | bridge | br100 | bridge_interface| eth1 | broadcast | 10.0.0.255 | cidr| 10.0.0.0/24 | cidr_v6 | - | created_at | 2015-02-10T05:52:41.00 | deleted | False | deleted_at | - | dhcp_server | 10.0.0.1 | dhcp_start | 10.0.0.3 | dns1| 8.8.4.4 | dns2| - | enable_dhcp | True | gateway | 10.0.0.1 | gateway_v6 | - | host| - | id | a16f1896-da4c-4978-9776-0b6368129b07 | injected| False | label | private | mtu | - | multi_host | False | netmask | 255.255.255.0 | netmask_v6 | - | priority| - | project_id | - | rxtx_base | - | share_address | False | updated_at | - | vlan| 100 | vpn_private_address | 10.0.0.2 | vpn_public_address | - | vpn_public_port | 1000 +-+--+ vagrant@ubuntu:~/devstack$ nova network-create --fixed-range-v4 20.0.0.0/24 --vlan 100 vlan100 ERROR (Conflict): There was a conflict when trying to complete your request. (HTTP 409) (Request-ID: req-634ac773-3fc7-4013-a319-69fbd4f1cca3) Contrary to other conflict such as subnet conflict, nova returns a clearer error message. ** Affects: nova Importance: Undecided Assignee: Kahou Lei (kahou82) Status: New ** Changed in: nova Assignee: (unassigned) => Kahou Lei (kahou82) -- 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/1420112 Title: Nova doesn't show enough error message when creating a new network with a duplicate vlan ID. Status in OpenStack Compute (Nova): New Bug description: This happens when user tries to create a new network with a duplicate vlan ID: vagrant@ubuntu:~/devstack$ nova network-list +--+-+-+ | ID | Label | Cidr| +--+-+-+ | a16f1896-da4c-4978-9776-0b6368129b07 | private | 10.0.0.0/24 | +--+-+-+ vagrant@ubuntu:~/devstack$ nova network-show a16f1896-da4c-4978-9776-0b6368129b07 +-+--+ | Property| Value +-+--+ | bridge | br100 | bridge_interface| eth1 | broadcast | 10.0.0.255 | cidr| 10.0.0.0/24 | cidr_v6 | - | created_at | 2015-02-10T05:52:41.00 | deleted | False | deleted_at | - | dhcp_server | 10.0.0.1 | dh
[Yahoo-eng-team] [Bug 1394800] [NEW] Potential undefined object issue in angular horizon.js
Public bug reported: If you look at the horizon.js (https://github.com/openstack/horizon/blob/master/horizon/static/horizon/js/angular/horizon.js), you will notice that horizon.conf is being assigned by hzConfig during the run function. I was trying to add a provider which also rely on hzConfig and the provider is created under the same hz module. (https://gist.github.com/kahou82/86578bcc64cdf5919ec3#file-horizon-js-L8). Since the horizon.conf is being assigned AFTER the provider is create, my provider will have undefined object error. ** Affects: horizon Importance: Undecided Assignee: Kahou Lei (kahou82) Status: New ** Changed in: horizon Assignee: (unassigned) => Kahou Lei (kahou82) -- 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/1394800 Title: Potential undefined object issue in angular horizon.js Status in OpenStack Dashboard (Horizon): New Bug description: If you look at the horizon.js (https://github.com/openstack/horizon/blob/master/horizon/static/horizon/js/angular/horizon.js), you will notice that horizon.conf is being assigned by hzConfig during the run function. I was trying to add a provider which also rely on hzConfig and the provider is created under the same hz module. (https://gist.github.com/kahou82/86578bcc64cdf5919ec3#file-horizon-js-L8). Since the horizon.conf is being assigned AFTER the provider is create, my provider will have undefined object error. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1394800/+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
