Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1085572

Summary:	[Docs] [Install] Is it possible to install and configure rhevm-websocket-proxy after doing the 3.2 -> 3.3 upgrade?
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Gajanan <gchakkar>
Component:	Documentation	Assignee:	Andrew Dahms <adahms>
Status:	CLOSED DUPLICATE	QA Contact:	ecs-bugs
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.3.0	CC:	acathrow, yeylon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-04-09 22:31:23 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:

Description Gajanan 2014-04-08 23:51:17 UTC

Description of problem:

From the rhev documentaion link its mentioned that "Make sure that the ovirt-engine-websocket-proxy package was installed prior to installing the engine, otherwise it won't be correctly configured."


Expected: There should be a way to install the same after installing the engine. 

Refer the below documentation link to Configure the websockets proxy: 

https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.3/html-single/Installation_Guide/index.html

Here: B.7. Squid Proxy
B.7.1. Installing and Configuring a Squid Proxy

Go To: Point 6: Configure the websockets proxy

Comment 2 Andrew Dahms 2014-04-09 22:31:23 UTC

Hi Gajanan,

Thank you for raising this bug.

Since the last release of the documentation, content has been added on how to manually configure the websocket proxy both during installation or upgrade and after installation or upgrade.
This content was addressed in Bug #1062795.

I will close this bug for now, but please let me know if you feel the updated content requires additional information when it is released and I would be happy to review the section for you.

Kind regards,

Andrew

*** This bug has been marked as a duplicate of bug 1062795 ***