[Yahoo-eng-team] [Bug 1651540] [NEW] Lines missing for heat topology in dashboard
Public bug reported: Seems like the heat topology in horizon is broken. The lines connecting all the elements is no longer visible. Please check attached image for the same. ** Affects: horizon Importance: Undecided Status: New ** Attachment added: "newton_horizon_heat_topology.png" https://bugs.launchpad.net/bugs/1651540/+attachment/4794385/+files/newton_horizon_heat_topology.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/1651540 Title: Lines missing for heat topology in dashboard Status in OpenStack Dashboard (Horizon): New Bug description: Seems like the heat topology in horizon is broken. The lines connecting all the elements is no longer visible. Please check attached image for the same. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1651540/+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 1575335] Re: Out-of-tree compute drivers no longer loading
** Also affects: nova-docker Importance: Undecided Status: New ** Changed in: nova-docker Assignee: (unassigned) => Sayali Lunkad (sayalilunkad) -- 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/1575335 Title: Out-of-tree compute drivers no longer loading Status in OpenStack Compute (nova): Fix Released Status in nova-docker: New Status in nova-powervm: Fix Released Bug description: Commit https://github.com/openstack/nova/commit/8eb03de1eb83a6cd2d4d41804e1b8253f94e5400 removed the mechanism by which nova-powervm was loading its Compute driver from out of tree, resulting in the following failure to start up n-cpu: 2016-04-25 23:53:46.581 32459 INFO nova.virt.driver [-] Loading compute driver 'nova_powervm.virt.powervm.driver.PowerVMDriver' 2016-04-25 23:53:46.582 32459 ERROR nova.virt.driver [-] Unable to load the virtualization driver 2016-04-25 23:53:46.582 32459 ERROR nova.virt.driver Traceback (most recent call last): 2016-04-25 23:53:46.582 32459 ERROR nova.virt.driver File "/opt/stack/nova/nova/virt/driver.py", line 1623, in load_compute_driver 2016-04-25 23:53:46.582 32459 ERROR nova.virt.driver virtapi) 2016-04-25 23:53:46.582 32459 ERROR nova.virt.driver File "/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 44, in import_object 2016-04-25 23:53:46.582 32459 ERROR nova.virt.driver return import_class(import_str)(*args, **kwargs) 2016-04-25 23:53:46.582 32459 ERROR nova.virt.driver File "/usr/local/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 30, in import_class 2016-04-25 23:53:46.582 32459 ERROR nova.virt.driver __import__(mod_str) 2016-04-25 23:53:46.582 32459 ERROR nova.virt.driver ImportError: No module named nova_powervm.virt.powervm.driver 2016-04-25 23:53:46.582 32459 ERROR nova.virt.driver n-cpu failed to start To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1575335/+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 1615666] [NEW] Nova config misses [cinder] insecure option
Public bug reported: Sample config generated does not contain insecure option needed for ssl. ** Affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1615666 Title: Nova config misses [cinder] insecure option Status in OpenStack Compute (nova): New Bug description: Sample config generated does not contain insecure option needed for ssl. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1615666/+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 1525209] [NEW] Windows interface polling manager doesn't use ovsdb client monitor
Public bug reported: In Linux the OVS agent uses the class InterfacePollingMinimizer that notifies the agent when a new port is plugged or unplugged and passes the related events (port added or deleted). For Windows it uses the class AlwaysPoll that doesn't notify any specific event, it returns always true. The OVS agent in Windows is forced to rescan the devices currently in the machine to infer which were added. This is because the current Windows implementation of the interface polling manager doesn't use ovsdb client monitor. Fix this by using ovsdb client monitor also for Windows and make sure that the events are passed correctly to the OVS agent. ** Affects: neutron Importance: Undecided Assignee: Sayali Lunkad (sayalilunkad) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Sayali Lunkad (sayalilunkad) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1525209 Title: Windows interface polling manager doesn't use ovsdb client monitor Status in neutron: In Progress Bug description: In Linux the OVS agent uses the class InterfacePollingMinimizer that notifies the agent when a new port is plugged or unplugged and passes the related events (port added or deleted). For Windows it uses the class AlwaysPoll that doesn't notify any specific event, it returns always true. The OVS agent in Windows is forced to rescan the devices currently in the machine to infer which were added. This is because the current Windows implementation of the interface polling manager doesn't use ovsdb client monitor. Fix this by using ovsdb client monitor also for Windows and make sure that the events are passed correctly to the OVS agent. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1525209/+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
