[Yahoo-eng-team] [Bug 1814209] [NEW] Messages for security rules are being sent to a wrong MQ topic. Security rules are out of sync

Public bug reported: Hello, We deployed Neutron + OVS + DVR long time ago. After upgrade from Ocata->Pike->Queens we've got a problem with security groups. They all are out of sync because messages are being sent to a queue with no consumers (there were some old Ocata consumers though, but we

[Yahoo-eng-team] [Bug 1805164] [NEW] Services can not be disabled

Public bug reported: I'm trying to disable nova services, but the requests fail. python-nova-17.0.7-1.el7.noarch openstack-nova-api-17.0.7-1.el7.noarch openstack-nova-novncproxy-17.0.7-1.el7.noarch openstack-nova-placement-api-17.0.7-1.el7.noarch python2-novaclient-10.1.0-1.el7.noarch

[Yahoo-eng-team] [Bug 1730890] Re: apiv2. owner isn't set for new images

[paste_deploy] # ... flavor = keystone should be defined ** Changed in: glance Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1730890 Title: apiv2. owner

[Yahoo-eng-team] [Bug 1730890] [NEW] apiv2. owner isn't set for new images

Public bug reported: After switched to APIv2, owner is not set for new images You can see "owner is None". It affects other components, include Horizon, to determine the project. Owner should be set even if no `--owner` specified # openstack image create "cirros-$RANDOM" --file

[Yahoo-eng-team] [Bug 1712518] Re: =multi domain support is broken in Ocata

an RPM packaging bug. oslo.config should be updated. `python-oslo-config >= 2:3.20.0` ** Changed in: keystone Status: New => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Identity (keystone).

[Yahoo-eng-team] [Bug 1712518] [NEW] =multi domain support is broken in Ocata

Public bug reported: Hello, I just upgraded from Newton to Ocata and now I'm facing this bug. # openstack domain list __call__() got an unexpected keyword argument 'default_config_dirs' (HTTP 400) (Request-ID: req-c586814e-9ea2-4f8b-b984-d3104859d00f) (see trace attached) # rpm -qa | grep -i

[Yahoo-eng-team] [Bug 1656241] [NEW] got an unexpected keyword argument 'app_name'

Public bug reported: I'm going to deploy Newton and after I installed Keystone I got this error: # openstack --debug endpoint list START with options: [u'--debug', u'endpoint', u'list'] options: Namespace(access_key='', access_secret='***', access_token='***', access_token_endpoint='',

[Yahoo-eng-team] [Bug 1652233] [NEW] mitaka is incompatible with newton

Public bug reported: Description === I get an error after upgrade half of my cluster. Can't place any VMs. "RemoteError: Remote error: IncompatibleObjectVersion Version 2.1 of InstanceList is not supported" Steps to reproduce == 1) Install 4 nodes with mitaka 2)

[Yahoo-eng-team] [Bug 1649263] [NEW] Nova APi failed after upgrade mitaka->newton

Public bug reported: Hello everybody! I have 2 controllers and 2 compute nodes. I disabled all the services on the first controller and compute (nova service-disable), then I upgraded those services to newton, executed `db sync` and started all the services on both nodes. After start the