Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1371349 - [Tracker] - rhevm-doc Batch Update - 4.0.4
[Tracker] - rhevm-doc Batch Update - 4.0.4
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhevm-doc (Show other bugs)
4.0.3
Unspecified Unspecified
unspecified Severity medium
: ovirt-4.0.4
: 4.0.4
Assigned To: Greg Sheremeta
Pavol Brilla
: Rebase, Tracking, ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-08-29 21:04 EDT by Greg Sheremeta
Modified: 2016-09-28 18:18 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-09-28 18:18:24 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: UX
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:1955 normal SHIPPED_LIVE Updated documentation and context-sensitive help for RHV 4.0.4 2016-09-28 21:34:49 EDT

  None (edit)
Description Greg Sheremeta 2016-08-29 21:04:46 EDT
Description of problem:
[Tracker] - rhevm-doc Batch Update - 4.0.4
Comment 1 Greg Sheremeta 2016-08-29 21:06:45 EDT
@Oved, please set 4.0.z+, thanks!
Comment 2 Pavol Brilla 2016-09-22 03:52:23 EDT
Builds found in erratum: 
rhevm-doc-4.0.4-1.el7ev
rhevm-doc-ja-JP-4.0.4-1.el7ev
rhevm-doc-ko-KR-4.0.4-1.el7ev
rhevm-doc-zh-CN-4.0.4-1.el7ev
Comment 4 errata-xmlrpc 2016-09-28 18:18:24 EDT
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/RHEA-2016-1955.html

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