Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1218773 - [Docs] [Admin] Section on History Database not valid in 3.5
[Docs] [Admin] Section on History Database not valid in 3.5
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation (Show other bugs)
3.5.0
Unspecified Unspecified
medium Severity high
: ---
: 3.5.3
Assigned To: Lucy Bopf
Julie
:
Depends On:
Blocks: 1234671
  Show dependency treegraph
 
Reported: 2015-05-05 16:19 EDT by Anitha Udgiri
Modified: 2015-07-23 09:29 EDT (History)
12 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-06-12 00:08:05 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 Anitha Udgiri 2015-05-05 16:19:02 EDT
Description of problem:

23.2.5. Connecting to the History Database :
The above section in the Administration Guide in RHEV 3.5 is no longer valid.
References to /var/lib/ovirt-engine/delpoyments is not present in 3.5 and hence needs to be corrected to what is correct and supported.

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.5/html/Administration_Guide/sect-History_Database.html
Comment 1 Andrew Dahms 2015-05-19 00:54:52 EDT
Assigning to Lucy for review.

Lucy - looking at the notes, this could just be an issue of the directory having been moved somewhere else, but the method itself may have changed.
Comment 13 Lucy Bopf 2015-06-02 21:45:31 EDT
Thanks, Andrew.

I've now removed the topic from the Administration Guide:

Administration Guide [23027-760340]
Revision History [34613-760339]

Since this is a simple removal, I am making the changes to the guide myself, and moving this bug straight to RELEASE_PENDING.
Comment 15 Lucy Bopf 2015-06-12 00:08:05 EDT
Change appears in most recent async release.

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