Bug 1024129
| Summary: | Documentation does not mention quota permission requirement for Satellite 5.6.0 using an external Oracle database | ||
|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Joe Thompson <jthompso> |
| Component: | Docs Installation Guide | Assignee: | Dan Macpherson <dmacpher> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Dan Macpherson <dmacpher> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 560 | CC: | gcheng, redhat-bugs |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-10-21 02:44:51 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1018166 | ||
|
Description
Joe Thompson
2013-10-28 23:21:25 UTC
(In reply to Joe Thompson from comment #0) > Description of problem: When attempting to install Satellite 5.6 using an > external Oracle DB, the tablespace was set up in accordance with the > requirements in section 2.3.3.2 of the install guide, however the install > still would not progress past testing the connection to the database. After > examining the database logs and some basic tests, the Satellite database > user was granted unlimited quota on the tablespace and the install proceeded > normally. > > Version-Release number of selected component (if applicable): 5.6.0 > > > How reproducible: 100% > > > Steps to Reproduce: > 1. Create an Oracle 11g tablespace for Satellite 5.6.0 in strict accord with > the installation requirements but with a tightly-restricted user quota > rather than the default (no quota). In fairness your reproducer says that the DBA has to do something beyond 'default' for the user to break our documentation, which specifically, is restrict its quota. > 2. Attempt to install Satellite 5.6.0. > > Actual results: Install fails at testing the connection to the database. > > > Expected results: When all Installation Guide documented requirements are > met, the install should succeed. So, really, the documentation today is sufficient, unless we than add an addendum saying 'We assume all defaults and cannot account for each potential variable, which may break our requirements, such as user quotas' Cliff > > > Additional info: I think assigning quotas to users is fairly common, though, as it's part of Oracle's basic security guidance (see e.g. http://docs.oracle.com/cd/B28359_01/network.111/b28531/users.htm#DBSEG10220). So we should call that (and maybe a couple of other things -- that just happened to be the one that bit in this instance) out specifically as a thing that may need altering to allow Satellite to install. Something like your last sentence would probably do the job, but it's probably worth getting into paragraph-sized detail in. "Some common database configuration items that may cause Satellite install to fail are: ..." This bug can be worked on early during the planning stages for Satellite 5.7. Released with Satellite 5.7 |