Bug 1560515 - Regression-router HA field display "False" on HA setup
Summary: Regression-router HA field display "False" on HA setup
Keywords:
Status: CLOSED DUPLICATE of bug 1568341
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
low
high
Target Milestone: ---
: ---
Assignee: Brian Haley
QA Contact: Toni Freger
URL:
Whiteboard:
Depends On:
Blocks: 1568341
TreeView+ depends on / blocked
 
Reported: 2018-03-26 11:49 UTC by Eran Kuris
Modified: 2018-05-10 21:15 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1568341 (view as bug list)
Environment:
Last Closed: 2018-05-10 21:15:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1689510 0 None None None 2018-04-02 15:28:41 UTC

Description Eran Kuris 2018-03-26 11:49:14 UTC
Description of problem:
on HA setup (3 controllers) router that created should be HA router.
The expected is user get the inforametion that the router is HA. 
(overcloud) [stack@undercloud-0 ~]$ . stackrc 
(undercloud) [stack@undercloud-0 ~]$ openstack server list
+--------------------------------------+--------------+--------+------------------------+----------------+------------+
| ID                                   | Name         | Status | Networks               | Image          | Flavor     |
+--------------------------------------+--------------+--------+------------------------+----------------+------------+
| 302e16cb-b3e3-4921-96ea-c834bd2c5f36 | controller-0 | ACTIVE | ctlplane=192.168.24.12 | overcloud-full | controller |
| 50e52595-a371-4d28-bb0e-4101af7fd708 | controller-1 | ACTIVE | ctlplane=192.168.24.7  | overcloud-full | controller |
| 18760968-0769-4c66-bba0-3abdd9c9ebba | compute-0    | ACTIVE | ctlplane=192.168.24.16 | overcloud-full | compute    |
| b112b330-6bc8-4fbf-b19b-36cab8e45fa6 | compute-1    | ACTIVE | ctlplane=192.168.24.10 | overcloud-full | compute    |
| d970af47-0d21-4694-971c-c83db20cdd96 | controller-2 | ACTIVE | ctlplane=192.168.24.11 | overcloud-full | controller |
+--------------------------------------+--------------+--------+------------------------+----------------+------------+
(undercloud) [stack@undercloud-0 ~]$ openstack router list
NotFoundException: Unknown error
(undercloud) [stack@undercloud-0 ~]$ . overcloudrc 
(overcloud) [stack@undercloud-0 ~]$ openstack router list
+--------------------------------------+-------------+--------+-------+-------------+-------+----------------------------------+
| ID                                   | Name        | Status | State | Distributed | HA    | Project                          |
+--------------------------------------+-------------+--------+-------+-------------+-------+----------------------------------+
| a51f842c-9c67-4143-b13c-8b35fc632913 | Router_eNet | ACTIVE | UP    | False       | False | aa3fe6a7406d4b18b9ba9ad9de63edb3 |
+--------------------------------------+-------------+--------+-------+-------------+-------+----------------------------------+


Version-Release number of selected component (if applicable):
OSP13 -p 2018-03-02.2

How reproducible:
always

Steps to Reproduce:
1. create network & subnet
2. create router
3. show router details


Actual results:
ha false

Expected results:
ha true

Additional info:

Comment 2 Brian Haley 2018-04-02 15:28:42 UTC
Here is my comment from the upstream bug opened for the same issue last year:

"So this is a bug in openstacksdk and/or python-openstackclient code, by default it is showing both "distributed" and "ha" values (with defaults to False), even if they are not in the JSON body returned from neutron-server. I don't know of an easy way to fix that by specifying not to show it in that case."

Comment 3 Miguel Angel Ajo 2018-04-16 12:51:26 UTC
Also, networking-ovn won't show such field, because we don't expose it on the routers. The routers are HA as soon as we have more than one available network node.

Comment 4 Eran Kuris 2018-04-16 14:31:19 UTC
(In reply to Miguel Angel Ajo from comment #3)
> Also, networking-ovn won't show such field, because we don't expose it on
> the routers. The routers are HA as soon as we have more than one available
> network node.

so let's remove this field from the display.

Comment 5 Daniel Alvarez Sanchez 2018-04-17 09:22:29 UTC
(In reply to Eran Kuris from comment #4)
> (In reply to Miguel Angel Ajo from comment #3)
> > Also, networking-ovn won't show such field, because we don't expose it on
> > the routers. The routers are HA as soon as we have more than one available
> > network node.
> 
> so let's remove this field from the display.

Shall you then clone this to python-networking-ovn component?

Comment 6 Eran Kuris 2018-04-17 09:40:13 UTC
(In reply to Daniel Alvarez Sanchez from comment #5)
> (In reply to Eran Kuris from comment #4)
> > (In reply to Miguel Angel Ajo from comment #3)
> > > Also, networking-ovn won't show such field, because we don't expose it on
> > > the routers. The routers are HA as soon as we have more than one available
> > > network node.
> > 
> > so let's remove this field from the display.
> 
> Shall you then clone this to python-networking-ovn component?

cloned

Comment 7 Brian Haley 2018-04-17 14:06:19 UTC
Eran - I'm not sure what you mean by "remove it from the display".  Do you just mean by default don't show it (along with distributed)?  I think that is Ok.  The admin should be able to see it, and others can always query it, they will just always get False.

I guess in the end we want the openstackclient to behave like the neutronclient - don't show these values unless they are in the JSON body.

Comment 8 Eran Kuris 2018-04-18 04:41:15 UTC
(In reply to Brian Haley from comment #7)
> Eran - I'm not sure what you mean by "remove it from the display".  Do you
> just mean by default don't show it (along with distributed)?  I think that
> is Ok.  The admin should be able to see it, and others can always query it,
> they will just always get False.
> 
> I guess in the end we want the openstackclient to behave like the
> neutronclient - don't show these values unless they are in the JSON body.

Yes, I meant that by default don't show it for OVN setup.

Comment 9 Brian Haley 2018-05-10 21:15:24 UTC
This work is being tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1568341 which was actually a clone of this bug.  Since I think the upstream changes associated with that will fix this, will mark as a duplicate.

Hopefully bugzilla doesn't have any problem with being a duplicate of the parent.

Comment 10 Brian Haley 2018-05-10 21:15:51 UTC

*** This bug has been marked as a duplicate of bug 1568341 ***


Note You need to log in before you can comment on or make changes to this bug.