[Yahoo-eng-team] [Bug 1624264] Re: Dashboard take 5-10 secs for OpenStack operations
** Also 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/1624264 Title: Dashboard take 5-10 secs for OpenStack operations Status in OpenStack Dashboard (Horizon): New Status in horizon package in Ubuntu: New Bug description: Dashboard takes around 5-10secs for OpenStack operations (e.g opening instance's page etc) from project panel in admin tenant. Although, if we open any page from admin panel, it takes around 2-3 seconds. Similarly, if we open any page from any other tenant, 5-10 secs are consumed. CLI commands seem to be working fine as they take around 1-3.5 secs. Please let me know the logs to share. Neutron, Keystone, Nova logs doesn't show any errors regarding slowness in API calls. OpenStack Release: Mitaka Horizon version: 9.1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1624264/+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 1617206] Re: OpenStack Horizon: unable to update network name/state
This doesn't seem to be the duplicate of bug #1609467 Apache2 error logs in horizon: horizon-unit-1: http://paste.ubuntu.com/23092341/ horizon-unit-2: http://paste.ubuntu.com/23092346/ horizon-unit-3: http://paste.ubuntu.com/23092350/ ** This bug is no longer a duplicate of bug 1609467 Rename Network return 403 Error -- 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/1617206 Title: OpenStack Horizon: unable to update network name/state Status in OpenStack Dashboard (Horizon): New Status in openstack-dashboard package in Juju Charms Collection: New Bug description: The issue is hitting for tenants other than the admin. I am unable to update "name" or "state" of the network from the owner tenant in Horizon although able to update subnet for the same network, routers and VMs in the same tenant. From horizon, admin tenant allows to update name/state of that tenant's network. "policy.json" looks fine as it is allowing both admin and owner tenant to update networks. Right now, two workarounds are available: 1- Use CLI to update network name/state 2- Use admin tenant to update network name/state Horizon version: $ dpkg -l | grep horizon ii python-django-horizon2:9.1.0-0ubuntu1~cloud0 all Django module providing web based interaction with OpenStack It is also hitting on version 9.0 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1617206/+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 1617206] [NEW] OpenStack Horizon: unable to update network name/state
Public bug reported: The issue is hitting for tenants other than the admin. I am unable to update "name" or "state" of the network from the owner tenant in Horizon although able to update subnet for the same network, routers and VMs in the same tenant. >From horizon, admin tenant allows to update name/state of that tenant's >network. "policy.json" looks fine as it is allowing both admin and owner >tenant to update networks. Right now, two workarounds are available: 1- Use CLI to update network name/state 2- Use admin tenant to update network name/state Horizon version: $ dpkg -l | grep horizon ii python-django-horizon2:9.1.0-0ubuntu1~cloud0 all Django module providing web based interaction with OpenStack It is also hitting on version 9.0 ** Affects: horizon Importance: Undecided Status: New ** Affects: openstack-dashboard (Juju Charms Collection) Importance: Undecided Status: New ** Package changed: nova-compute (Juju Charms Collection) => openstack- dashboard (Juju Charms Collection) ** Also 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/1617206 Title: OpenStack Horizon: unable to update network name/state Status in OpenStack Dashboard (Horizon): New Status in openstack-dashboard package in Juju Charms Collection: New Bug description: The issue is hitting for tenants other than the admin. I am unable to update "name" or "state" of the network from the owner tenant in Horizon although able to update subnet for the same network, routers and VMs in the same tenant. From horizon, admin tenant allows to update name/state of that tenant's network. "policy.json" looks fine as it is allowing both admin and owner tenant to update networks. Right now, two workarounds are available: 1- Use CLI to update network name/state 2- Use admin tenant to update network name/state Horizon version: $ dpkg -l | grep horizon ii python-django-horizon2:9.1.0-0ubuntu1~cloud0 all Django module providing web based interaction with OpenStack It is also hitting on version 9.0 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1617206/+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 1589221] Re: Nova-compute: "ImageNotFound: Image could not be found."
Hi Augustina, thanks for the reply. 192.168.10.59 is my neutron Virtual IP. If you see the timestamps of this error ConnectFailure: Unable to establish connection to http://192.168.10.59:9696/v2.0/ports.json?tenant_id=a28c7b4b55034254a2d912fe6bfb49ad_id=21a97ef7-7ae8-4f... and this one ImageNotFound: Image b1c302c6-23b2-4d59-9b32-da9ff5d11e5b could not be found. it can be observed that they are not related. This error occurs with a newly created image. 1. The version of Nova is Mitaka 2. Steps to reproduce: (error hits in HA environment) - Create a new image. - Spawn a new instance using the newly created image. - It fails with error the error in horizon as shown in the attached image and log as provided above (ImageNotFound) ** Attachment added: "Screenshot from 2016-06-22 12:07:27.png" https://bugs.launchpad.net/charms/+source/nova-compute/+bug/1589221/+attachment/4688338/+files/Screenshot%20from%202016-06-22%2012%3A07%3A27.png ** Changed in: nova Status: Invalid => 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/1589221 Title: Nova-compute: "ImageNotFound: Image could not be found." Status in OpenStack Compute (nova): New Status in nova-compute package in Juju Charms Collection: New Bug description: Spawning a new instance using a newly created image most of the time fails. After 2-3 attempts, the problem gets resolved. The configs that I'm using in my HA-environment are: nova-compute: enable-live-migration: "True" enable-resize: "True" openstack-origin: "cloud:trusty-mitaka" migration-auth-type: "ssh" manage-neutron-plugin-legacy-mode: False glance: openstack-origin: "cloud:trusty-mitaka" region: "serverstack" vip: nova-cloud-controller: network-manager: "Neutron" console-access-protocol: "novnc" openstack-origin: "cloud:trusty-mitaka" region: "serverstack" vip: I have one compute. Compute logs: http://paste.ubuntu.com/17026140/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1589221/+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 1589221] Re: Nova-compute: "ImageNotFound: Image could not be found."
** Also affects: nova Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1589221 Title: Nova-compute: "ImageNotFound: Image could not be found." Status in OpenStack Compute (nova): New Status in nova-compute package in Juju Charms Collection: New Bug description: Spawning a new instance using a newly created image most of the time fails. After 2-3 attempts, the problem gets resolved. The configs that I'm using in my HA-environment are: nova-compute: enable-live-migration: "True" enable-resize: "True" openstack-origin: "cloud:trusty-mitaka" migration-auth-type: "ssh" manage-neutron-plugin-legacy-mode: False glance: openstack-origin: "cloud:trusty-mitaka" region: "serverstack" vip: nova-cloud-controller: network-manager: "Neutron" console-access-protocol: "novnc" openstack-origin: "cloud:trusty-mitaka" region: "serverstack" vip: I have one compute. Compute logs: http://paste.ubuntu.com/17026140/ To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1589221/+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
