Bug 1803437 - [Doc] Correct the Octavia support matrix version from documentation.
Summary: [Doc] Correct the Octavia support matrix version from documentation.
Keywords:
Status: CLOSED DUPLICATE of bug 1792885
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-octavia
Version: 16.0 (Train)
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Assaf Muller
QA Contact: Bruna Bonguardo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-16 08:54 UTC by rohit londhe
Modified: 2020-02-16 09:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-16 09:22:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description rohit londhe 2020-02-16 08:54:13 UTC
Description of problem:

In the below RHOSP16 documentation[1] the Octavia support matrix section 15.3.1. "Octavia support matrix" from Table 15.1. "Octavia support matrix", Column contains the wrong RHOSP version. It should be RHOSP16 and not RHOSP13.

The same typo mistakes are repeated in RHOSP14[2] and RHOSP15[3] documentation as well.

[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html/networking_guide/sec-octavia

[2] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15/html-single/networking_guide/index#sec-octavia

[3] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/14/html/networking_guide/sec-octavia#octavia_support_matrix

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
Present version RHOSP13

Expected results:
Correct version to RHOSP16

Additional info:

Comment 1 Carlos Goncalves 2020-02-16 09:22:56 UTC
Thank you for reporting this issue, Rohit!

I believe this is a duplicate of BZ #1792885. Please kindly refer to it.

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


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