Bug 1160310 - [Docs] [Install] Requirement to install rhevm-websocket-proxy not listed as an optional prerequisite of installation or upgrade to RHEV 3.3
Summary: [Docs] [Install] Requirement to install rhevm-websocket-proxy not listed as a...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-3.6.2
: 3.6.0
Assignee: rhev-docs@redhat.com
QA Contact: Robert McSwain
URL:
Whiteboard: docs
Depends On: 1062795
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-04 14:27 UTC by Robert McSwain
Modified: 2019-08-15 15:43 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1062795
Environment:
Last Closed: 2016-01-24 23:41:35 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 718653 0 None None None Never

Comment 1 Andrew Dahms 2015-08-18 23:36:16 UTC
Updated the target release; content to be backported as the schedule allows.

Comment 2 Red Hat Bugzilla Rules Engine 2015-10-20 15:37:52 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 3 Sandro Bonazzola 2015-10-26 12:40:26 UTC
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015.
Please review this bug and if not a blocker, please postpone to a later release.
All bugs not postponed on GA release will be automatically re-targeted to

- 3.6.1 if severity >= high
- 4.0 if severity < high

Comment 5 Yaniv Lavi 2015-11-18 13:53:44 UTC
Can you help with verifying the docs changes from the link in comment #4 and corrections from description?

Comment 6 Andrew Dahms 2015-12-01 05:59:26 UTC
Assigning to the default assignee and returning to status new to be re-triaged as the schedule allows.

Comment 7 Michal Skrivanek 2016-01-22 15:17:30 UTC
(In reply to Yaniv Dary from comment #5)
> Can you help with verifying the docs changes from the link in comment #4 and
> corrections from description?

current doc about websocket proxy looks good to me, however this is not the point of the original bug description. spice proxy seems updated ok

Comment 8 Yaniv Lavi 2016-01-24 09:32:28 UTC
(In reply to Michal Skrivanek from comment #7)
> (In reply to Yaniv Dary from comment #5)
> > Can you help with verifying the docs changes from the link in comment #4 and
> > corrections from description?
> 
> current doc about websocket proxy looks good to me, however this is not the
> point of the original bug description. spice proxy seems updated ok

I think we can closed this based on comment #7

Comment 9 Andrew Dahms 2016-01-24 23:41:35 UTC
Hi Yaniv,

Thank you for the needinfo request.

Agreed - I will close this bug, and we will revist the topic of the websocket proxy as the schedule allows to review all content on the topic.

Kind regards,

Andrew


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