Red Hat Bugzilla – Bug 1006948
Setup - When creating read only user, setup doesn't make sure preserved user names are not used.
Last modified: 2014-01-21 09:59:33 EST
Description of problem:
When creating read only user, setup doesn't make sure preserved user names are not used. We need to decide, if to fail install on existing user, so roles can be recreated with different password, or disallowing just the preserved user names.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run setup
2. Enter user 'engine' to be create as read only.
Setup fail on user drop
Should not allow existing user or selecting 'engine', 'engine_reports' and 'engine_history'.
Merged into master; http://gerrit.ovirt.org/gitweb?p=ovirt-dwh.git;a=commit;h=04e82796593ec4c69f5107d76184aea51346295e
verified on IS22:
This utility can configure a read only user for DB access. Would you like to do so? (yes|no): y
Provide a username for read-only user : engine
engine is a reserved username and cannot be used for creating read only user.
This bug is currently attached to errata RHEA-2013:15116. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
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.