Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1141269

Summary: Typos in help text for Create Network dialogue for Allocation Pools and Host Routes
Product: Red Hat OpenStack Reporter: Jeff Needle <jneedle>
Component: python-django-horizonAssignee: Matthias Runge <mrunge>
Status: CLOSED ERRATA QA Contact: Ido Ovadia <iovadia>
Severity: medium Docs Contact:
Priority: low    
Version: 5.0 (RHEL 6)CC: aberezin, aortega, athomas, mreid, mrunge, ohochman, sclark, yeylon
Target Milestone: z3Keywords: Triaged, ZStream
Target Release: 6.0 (Juno)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-django-horizon-2014.2.2-3.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-05-05 13:09:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Allocation Pools text
none
Host Routes text none

Description Jeff Needle 2014-09-12 15:09:25 UTC
Seems like there are typos in the Allocation Pools and Host Routes help text (3rd step in Create Network dialogue). "IP address allocation pools. Each entry is &lt;start_ip_address&gt;,&lt;end_ip_addr (eg., 192.168.1.100,192.168.1.120) and one entry per line." I'm not sure if the end_ip_addr part is cut off and runs off the bubble it's set within or if that's showing everything there is. "Addtional routes announced to the hosts. Each entry is &lt;destination_cidr&gt;,&lt;nexthop&gt; (e.g., 192.168.200.0/24,10.56.1.254)"

Comment 2 Matt Reid 2014-09-12 17:40:14 UTC
Created attachment 937023 [details]
Allocation Pools text

Comment 3 Matt Reid 2014-09-12 17:40:35 UTC
Created attachment 937024 [details]
Host Routes text

Comment 4 Julie Pichon 2014-09-18 06:52:12 UTC
This is fixed upstream in Juno (to be RHEL 6.0), in itself the fix is simple and easy to backport but because it impacts existing strings, it's going to invalidate the translations. I need to check with the translation team.

Comment 5 Julie Pichon 2014-12-04 13:28:55 UTC
This was backported upstream, we'll pick it up in the next rebase in February. The translation teams probably won't be looking at it though as upstream only support n and n-1 for translations.

Comment 7 Matthias Runge 2015-03-18 10:47:47 UTC
The fix was merged into juno, translation team doesn't look back at older releases.

Comment 9 Ido Ovadia 2015-04-19 15:03:11 UTC
Verified
========
python-django-horizon-2014.2.3-2.el7ost.noarch

Comment 11 errata-xmlrpc 2015-05-05 13:09:35 UTC
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/RHBA-2015-0933.html