Description of problem: With latest puddles of RHOSP 8.0, "openstack flavor delete" fails with "public endpoint for messaging service not found" but "nova flavor-delete" succeeds Version-Release number of selected component (if applicable): How reproducible: [stack@undercloud-0-rhosp8 ~]$ openstack flavor delete compute public endpoint for messaging service not found [stack@undercloud-0-rhosp8 ~]$ nova flavor-delete compute +--------------------------------------+---------+-----------+------+-----------+------+-------+-------------+-----------+ | ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public | +--------------------------------------+---------+-----------+------+-----------+------+-------+-------------+-----------+ | 778d6fdc-ce9d-42aa-a6c6-e7732034a503 | compute | 4096 | 40 | 0 | | 1 | 1.0 | True | +--------------------------------------+---------+-----------+------+-----------+------+-------+-------------+-----------+ Steps to Reproduce: 1. Install latest undercloud 2. Try to delete the default flavors 3. Actual results: Fails Expected results: Succeeds Additional info: ----------------------+----------------------------------------+----------------------------------+ | id | region | publicurl | internalurl | adminurl | service_id | +----------------------------------+-----------+---------------------------------------------+---------------------------------------------+----------------------------------------+----------------------------------+ | 1f4e955b657341bfaa87ed3f678e1c87 | regionOne | http://192.0.2.1:8774/v3 | http://192.0.2.1:8774/v3 | http://192.0.2.1:8774/v3 | 9615dcfa802946b3b1ce4ce73cb95c8f | | 240dd3d4a8164908a4a48f3b8f3ec48b | regionOne | http://192.0.2.1:8042 | http://192.0.2.1:8042 | http://192.0.2.1:8042 | ff703cce75444794a50adb003d1de578 | | 24c48e58f3e6413aadff8660108db08d | regionOne | http://192.0.2.1:6385 | http://192.0.2.1:6385 | http://192.0.2.1:6385 | 271217283d324f9d8d318c13be3a9023 | | 2b7c0d2b18184860bf8a8f07bd45673f | regionOne | http://192.0.2.1:8080/v1/AUTH_%(tenant_id)s | http://192.0.2.1:8080/v1/AUTH_%(tenant_id)s | http://192.0.2.1:8080 | c2719fd8b9dd496db7505b2849bd73a7 | | 67dd9f93f383460aaa7c2e617e9c107a | regionOne | http://192.0.2.1:9696 | http://192.0.2.1:9696 | http://192.0.2.1:9696 | 6a5d97f4889349b8bf6aadbde8a03192 | | 8b5c2edf0f734f3bb613f3f7c0f5862b | regionOne | http://192.0.2.1:8004/v1/%(tenant_id)s | http://192.0.2.1:8004/v1/%(tenant_id)s | http://192.0.2.1:8004/v1/%(tenant_id)s | 5be142782c3a4a4ba02c11afc9c89a1f | | d30a53bd9729475289bd6d98624d6a8d | regionOne | http://192.0.2.1:8774/v2/%(tenant_id)s | http://192.0.2.1:8774/v2/%(tenant_id)s | http://192.0.2.1:8774/v2/%(tenant_id)s | ac063e4a4fe24b0c8d9446d42f157b3e | | de2a02625bc04195a18c429d65476a92 | regionOne | http://192.0.2.1:9292 | http://192.0.2.1:9292 | http://192.0.2.1:9292 | 58b9e6f56c27455c9e46eda877d48236 | | e03def6579394e8baf924aff43fe70ae | regionOne | http://192.0.2.1:5000/v2.0 | http://192.0.2.1:5000/v2.0 | http://192.0.2.1:35357//v2.0 | ad8bd0228bf44892a22b396ff82987a2 | | e0b87d78cb7a41ee8f9874995a304276 | regionOne | http://192.0.2.1:8777 | http://192.0.2.1:8777 | http://192.0.2.1:8777 | a65579f83f6d4592954d029fa5d82b0a | +----------------------------------+-----------+---------------------------------------------+---------------------------------------------+----------------------------------------+----------------------------------+
Same problem with latest RHOS 8 puddle (03/11). In fact "flavor delete" command from python-zaqarclient overrides the "flavor delete" from python-openstackclient. https://github.com/openstack/python-openstackclient/blob/stable/liberty/setup.cfg#L76 https://github.com/openstack/python-zaqarclient/blob/stable/liberty/setup.cfg#L56 The issue has been fixed upstream ("flavor delete" renamed in python-zaqarclient) but not backport in liberty https://bugs.launchpad.net/python-zaqarclient/+bug/1506957
Created attachment 1136603 [details] openstack flavor delete
Same error with the puddle of 18th march.
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
Mike, this bug only affects OSP 8 because the fix is already present in Mitaka since Oct 2015 so set the target to OSP 10 makes no sense.
Not a problem, moving back to 9 and marking MODIFIED
Verified: Environment: python-tripleoclient-2.0.0-1.0.2.el7ost.noarch [stack@instack ~]$ openstack flavor list +--------------------------------------+---------------+------+------+-----------+-------+-----------+ | ID | Name | RAM | Disk | Ephemeral | VCPUs | Is Public | +--------------------------------------+---------------+------+------+-----------+-------+-----------+ | 1a702766-9c4c-4a56-8bf8-867b1843e87a | baremetal | 4096 | 40 | 0 | 1 | True | | 3ecc9455-c80d-48fa-a9ec-a6c2880c2894 | compute | 4096 | 40 | 0 | 1 | True | | 41323b6b-190f-4c49-82c5-90c2fb8b71f6 | swift-storage | 4096 | 40 | 0 | 1 | True | | 4ba0262b-a677-4661-afa0-c7f2252d4ce4 | block-storage | 4096 | 40 | 0 | 1 | True | | d9320eb8-f387-464b-9f66-7f101953fd03 | control | 4096 | 40 | 0 | 1 | True | | dd20586d-07ec-4fb7-ad93-ec88eba2ce69 | ceph-storage | 4096 | 40 | 0 | 1 | True | +--------------------------------------+---------------+------+------+-----------+-------+-----------+ [stack@instack ~]$ openstack flavor delete compute [stack@instack ~]$ openstack flavor list +--------------------------------------+---------------+------+------+-----------+-------+-----------+ | ID | Name | RAM | Disk | Ephemeral | VCPUs | Is Public | +--------------------------------------+---------------+------+------+-----------+-------+-----------+ | 1a702766-9c4c-4a56-8bf8-867b1843e87a | baremetal | 4096 | 40 | 0 | 1 | True | | 41323b6b-190f-4c49-82c5-90c2fb8b71f6 | swift-storage | 4096 | 40 | 0 | 1 | True | | 4ba0262b-a677-4661-afa0-c7f2252d4ce4 | block-storage | 4096 | 40 | 0 | 1 | True | | d9320eb8-f387-464b-9f66-7f101953fd03 | control | 4096 | 40 | 0 | 1 | True | | dd20586d-07ec-4fb7-ad93-ec88eba2ce69 | ceph-storage | 4096 | 40 | 0 | 1 | True | +--------------------------------------+---------------+------+------+-----------+-------+-----------+
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-1599.html