Bug 1253544 - Typo sued should be used
Typo sued should be used
Status: CLOSED WONTFIX
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation (Show other bugs)
unspecified
Unspecified Unspecified
low Severity low
: async
: 2.0 Folsom
Assigned To: RHOS Documentation Team
RHOS Documentation Team
: Documentation
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-14 01:14 EDT by Warren
Modified: 2015-08-15 22:40 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-15 22:40:24 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Warren 2015-08-14 01:14:24 EDT
Description of problem:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/2/html/Getting_Started_Guide/chap-Deploying_Identity_Services.html contains a typo.


How reproducible:
100%

Additional info:

Text reads: 
Keystone uses a MySQL database. Use the openstack-db utility to create and initialize the tables for Keystone. If MySQL has not yet been installed on this server, the script will manage that as well. Ensure that you replace PASSWORD with a secure password to be sued by the service when connecting to the database:

should be:
Keystone uses a MySQL database. Use the openstack-db utility to create and initialize the tables for Keystone. If MySQL has not yet been installed on this server, the script will manage that as well. Ensure that you replace PASSWORD with a secure password to be used by the service when connecting to the database:
Comment 3 Andrew Dahms 2015-08-15 22:40:24 EDT
Hi Warren,

Thank you for raising this bug.

Unfortunately, as a general rule we do not update documentation more than one or two versions older than the latest version unless there is a pressing issue that must be addressed.

As such, I will be closing this bug now, but we will revisit this issue should an opportunity to update this version arise.

Kind regards,

Andrew

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