[Yahoo-eng-team] [Bug 2009832] [NEW] FWaaS docs lack required packages

Public bug reported: Like the other installation docs the fwaas doc should contain the required packages as well. For example, in this thread [1] we figured out which packages are required. Although for an experienced user it can be obvious what is missing it would be helpful if the basics are

[Yahoo-eng-team] [Bug 2009831] [NEW] VPNaaS docs lack packages to install

Public bug reported: Like the other installation docs the vpnaas doc should contain the required packages as well. For example, in this thread [1] we figured out which packages are required. Although for an experienced user it can be obvious what is missing it would be helpful if the basics are

[Yahoo-eng-team] [Bug 2007982] [NEW] keystone role cache misbehaving in HA setup

Public bug reported: Following up on two mailing list reports [1][2] which seem to have the same root cause. In a HA setup with 3 control nodes (Victoria, baremetal) terraform is used to deploy lots of different k8s clusters (and other stuff). We noticed keystone errors when a project is

[Yahoo-eng-team] [Bug 2007922] [NEW] Cleanup pending instances in "building" state

Public bug reported: Following up on the ML thread [1], it was recommended to create a bug report. After a network issue in a Victoria cluster (3 control nodes in HA mode, 26 compute nodes) some instance builds were interrupted. Some of them could be cleaned up with 'openstack server delete'

[Yahoo-eng-team] [Bug 1763297] [NEW] Install and configure in keystone: missing "domain create" command

Public bug reported: Since Newton release the install guide lacks an essential command. Before a user can create projects, users etc. there has to be the default domain first. In Mitaka guide [1] the steps are - openstack domain create --description "Default Domain" default - openstack project

[Yahoo-eng-team] [Bug 1723918] Re: nova-placement-api port mismatch

Thanks for your comment, you're right, I filed a bug report against openSUSE and marked this bug as invalid. ** Changed in: nova Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack

[Yahoo-eng-team] [Bug 1723918] [NEW] nova-placement-api port mismatch

Public bug reported: Description: Upgraded first from Mitaka to Newton, then to Ocata, and also upgraded openSUSE Leap 42.1 to Leap 42.3, so it's not a fresh installation, but since I couldn't find any hint to check the /etc/apache2/vhosts.d/nova-placement-api.conf.sample I assume this will

[Yahoo-eng-team] [Bug 1587777] Re: Mitaka: dashboard performance

I changed the status back to new because the docs for Ocata still don't contain the required information to configure memcached correctly, please note comment #8. ** Changed in: keystone Status: Invalid => New -- You received this bug notification because you are a member of Yahoo!

[Yahoo-eng-team] [Bug 1587777] Re: Mitaka: dashboard performance

** Changed in: horizon Status: Expired => 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/158 Title: Mitaka: dashboard performance Status in

[Yahoo-eng-team] [Bug 1656242] [NEW] nova live snapshot of rbd instance fails on xen hypervisor

Public bug reported: Description: We use a Mitaka environment with one control and three compute nodes (all running on openSUSE Leap 42.1), the compute nodes are xen hypervisors, our storage backend is ceph (for nova, glance and cinder). When we try to snapshot a running instance, it's always

[Yahoo-eng-team] [Bug 1608565] [NEW] Horizon ignores instance snapshot as pre-selected source image

Public bug reported: Description of problem: When launching an instance from an instance snapshot via Horizon images overview (Button "Launch") the resulting "Launch instance"-dialog ignores the selected image, the source has to be selected again. This only affects "Instance Snapshot" as

[Yahoo-eng-team] [Bug 1598171] [NEW] neutron router-gateway-set --enable-snat fails

Public bug reported: I have a Mitaka environment with 1 control node and 3 compute nodes, all physical machines running on openSUSE Leap 42.1. My version of neutron client: ---cut here--- control1:~ # rpm -qi python-neutronclient-3.1.1-1.1.noarch Name: python-neutronclient Version :

[Yahoo-eng-team] [Bug 1587777] [NEW] Mitaka: dashboard performance

Public bug reported: Environment: Openstack Mitaka on top of Leap 42.1, 1 control node, 2 compute nodes, 3-node-Ceph-cluster. Issue: Since switching to Mitaka, we're experiencing severe delays when accessing the dashboard - i.e. switching between "Compute - Overview" and "Compute - Instances"

[Yahoo-eng-team] [Bug 1560965] Re: libvirt selects wrong root device name

** 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 Compute (nova). https://bugs.launchpad.net/bugs/1560965 Title: libvirt selects wrong root device

[Yahoo-eng-team] [Bug 1560965] [NEW] libvirt selects wrong root device name

Public bug reported: Referring to Liberty, Compute runs with xen hypervisor: When trying to boot an instance from volume via Horizon, the VM fails to spawn because of an invalid block device mapping. I found a cause for that in a default initial "device_name=vda" in the file