Bug 1411866 - [Docs][NFV] Fix publishing issue with Chapter 5/6 in NFV Product Guide
Summary: [Docs][NFV] Fix publishing issue with Chapter 5/6 in NFV Product Guide
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Sandra McCann
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-10 16:24 UTC by Sandra McCann
Modified: 2017-01-12 01:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-12 01:29:10 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Sandra McCann 2017-01-10 16:24:27 UTC
Description of problem:

Scroll 1/2 way down this chapter:
https://access.redhat.com/documentation/en/red-hat-openstack-platform/10/paged/network-functions-virtualization-product-guide/chapter-5-nfv-tuning-for-performance

You will see == Finding More Information.

This is actually the start of another chapter but isn't showing up properly.

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

How reproducible:


Steps to Reproduce:
1. Scroll 1/2 way down this chapter:
https://access.redhat.com/documentation/en/red-hat-openstack-platform/10/paged/network-functions-virtualization-product-guide/chapter-5-nfv-tuning-for-performance

2. Search for == Finding More Information


Actual results:

You will see == Finding More Information.  This is actually the start of a new chapter but isn't showing up properly. 

Also - Table 4.1 is 'hard coded' into the text when this chapter would actually be chapter 6.


Expected results:
Finding More Information should start a new HTML page for multipage html format. (or Level2 header in PDF).

"Table 4.1" should be automatically numbered by the publishing system.

Additional info:


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