Bug 1846279

Summary:	[TRACKER] Upgrade of separate machines
Product:	[oVirt] ovirt-engine	Reporter:	Yedidyah Bar David <didi>
Component:	Documentation	Assignee:	Steve Goodman <sgoodman>
Status:	CLOSED DUPLICATE	QA Contact:	Guilherme Santos <gdeolive>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.4.1	CC:	adahms, bugs, gdeolive, lleistne, sbonazzo, sgordon
Target Milestone:	ovirt-4.4.7	Keywords:	Documentation, TestOnly, Tracking, ZStream
Target Release:	---	Flags:	pm-rhel: ovirt-4.4+ gdeolive: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-06-17 07:21:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1874904
Bug Blocks:

Description Yedidyah Bar David 2020-06-11 09:33:09 UTC

Description of problem:

We have documentation for setup of some components (DWH, Websocket-Proxy, perhaps Grafana in the future) on separate machines (from the engine), but do not have documentation on upgrading them.

Opening this tracker for:

1. Deciding whether we want to document this. If so, perhaps open a separate bug per component.

2. Deciding if we want code changes in the relevant flows. Similary, open bugs as needed.

In particular, some issues I ran into, thus deciding to open this bug:

1. Upgrading DWH on separate machine requires a flow similar to the engine itself - update setup packages, run engine-setup, update the rest. Without this, DWH's database will not be updated.

2. Websocket-Proxy does not require engine-setup - updating the packages should be enough. But: If users do run engine-setup (either because we do not document that this isn't needed, or because it's on the same separate machine as DWH, or any other reason), we ask them again the engine FQDN, although we do not need it. For DWH, we have code specifically for not doing this (was done for bug 1318665, env key REMOTE_ENGINE_CONFIGURED). Perhaps we should have something like this for WSP, or perhaps we should make this code common, which will also require changing/coordinating with DWH code.

Comment 1 Yedidyah Bar David 2020-08-19 09:50:34 UTC

Partial workaround:

Now tried separate dwh upgrade using backup/restore, and it failed, see the flow in bug 1870055.

Managed to make it work by:

1. Restore
2. Remove the line with remoteEngineConfigured from /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf
3. engine-setup

Comment 2 Yedidyah Bar David 2020-08-31 12:39:53 UTC

(In reply to Yedidyah Bar David from comment #1)
> Partial workaround:
> 
> Now tried separate dwh upgrade using backup/restore, and it failed, see the
> flow in bug 1870055.
> 
> Managed to make it work by:
> 
> 1. Restore
> 2. Remove the line with remoteEngineConfigured from
> /etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf
> 3. engine-setup

Now looked at his a bit.

I don't remember anymore why I added remoteEngineConfigured at the time ([1], for bug 1318665).

I think I'll try again the relevant flows, and just remove this altogether - perhaps will have to think about some other means to decide whether to configure remote engine, will need to check. If it turns out to be needed, or too complex to remove, we should probably duplicate this var to grafana, and not reuse in both. Noting also that in websocket-proxy we do not have something similar.

[1] https://gerrit.ovirt.org/56465

Comment 3 Sandro Bonazzola 2020-09-02 14:51:04 UTC

Opened separate bug for DWH (Bug #1874904) and Websocket Proxy (Bug #1874905)

Comment 4 Steve Goodman 2021-04-20 15:14:34 UTC

(In reply to Sandro Bonazzola from comment #3)
> Opened separate bug for DWH (Bug #1874904) and Websocket Proxy (Bug #1874905)

Sadnro, what is this current bug still tracking?

Comment 5 Sandro Bonazzola 2021-04-20 15:42:55 UTC

After all the dependencies removals, this is practically tracking bug #1874904 only.
Once the documentation is updated, we need QE to test the full workflow.

Comment 6 Sandro Bonazzola 2021-06-10 06:36:06 UTC

Re-targeting to 4.4.7 since oVirt 4.4.6 was released.

Comment 7 Sandro Bonazzola 2021-06-17 07:21:03 UTC


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