Description of problem:
when assigning FIP to VM when there is no external gateway we get unclear error message:
openstack floating ip set --port 64488a67-b79c-4bfa-a542-e7c607e762e3 9a868c30-1c7b-484c-9784-cb7ef9db556f
NotFoundException: Unknown error
Version-Release number of selected component (if applicable):
(overcloud) [stack@undercloud-0 ~]$ rpm -qa |grep openstackclient
There is an upstream bug tracking this, linked. I'll ping the owner again and re-assign if he's not making progress.
*** Bug 1582180 has been marked as a duplicate of this bug. ***
The two patches for python-openstacksdk have merged that fix this issue. I am assuming they would need to be cherry-picked downstream, will have to find out if this component is different.
*** Bug 1619384 has been marked as a duplicate of this bug. ***
Changed should all be in stable/queens now, so will flow downstream in the next rebase.
(In reply to Brian Haley from comment #8)
> Changed should all be in stable/queens now, so will flow downstream in the
> next rebase.
https://review.openstack.org/#/c/555142/ is only on upstream master. Does it need to be backported to stable/queens to fix this bug?
Picked to upstream stable/queens.
This is in the downstream version of the openstacksdk library:
python-openstacksdk is currently pinned in RDO Queens Trunk pipeline to 0.11.3 tag
so a tag upstream from the stable/queens branch or a bump to rdoinfo would be needed to start testing with this patch in RDO Queens Trunk CI.
Proposed https://review.opendev.org/#/c/688713/ to openstack-releases for openstack queens 0.11.4
There was an issue when tagging openstacksdk from PS19, but another was proposed and just merged.
So there should be a 0.11.4 tag in stable/queens we can import.
I realize my original patch was reverted, but there was a new one merged for openstacksdk queens 0.11.4, https://review.opendev.org/#/c/689608/
Hopefully that's all we need?
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.