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

Bug 1063869

Summary:	allinone fails on upgrade - no admin password
Product:	[Retired] oVirt	Reporter:	Yedidyah Bar David <didi>
Component:	ovirt-engine-installer	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.4	CC:	acathrow, alonbl, gklein, iheim, oschreib, sbonazzo, yeylon
Target Milestone:	---
Target Release:	3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:	ovirt-3.4.0-beta3	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-03-31 12:33:15 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 Yedidyah Bar David 2014-02-11 15:07:34 UTC

Description of problem:

allinone needs the admin password but does not have it during upgrades.

Version-Release number of selected component (if applicable):

3.4, probably even 3.3 (didn't try)

How reproducible:

Always

Steps to Reproduce:
1. engine-setup without allinone installed
2. install allinone plugin
3. engine-setup and choose to configure vdsm

Actual results:

setup fails

Expected results:

setup succeeds

Additional info:

We should probably either keep the password during setup (not sure where, in a 0600 file) or ask for it. Currently pushed http://gerrit.ovirt.org/24334 which asks for it.

Verified that this works, failed later for what seems like an unrelated reason, will check and might open another bug.

Comment 1 Alon Bar-Lev 2014-02-11 15:31:17 UTC

I would have disabled the all-in-one plugin if not new database, as there is no sense in doing post install of all-in-one, a simple add-host within the ui is much easier and much better supported.

Comment 2 Yedidyah Bar David 2014-02-11 15:38:17 UTC

(In reply to Alon Bar-Lev from comment #1)
> I would have disabled the all-in-one plugin if not new database, as there is
> no sense in doing post install of all-in-one, a simple add-host within the
> ui is much easier and much better supported.

I was under the impression that installing an engine on a host and later adding it as a host to the engine breaks stuff. Otherwise, why do we need allinone at all?

Comment 3 Alon Bar-Lev 2014-02-11 15:49:15 UTC

(In reply to Yedidyah Bar David from comment #2)
> (In reply to Alon Bar-Lev from comment #1)
> > I would have disabled the all-in-one plugin if not new database, as there is
> > no sense in doing post install of all-in-one, a simple add-host within the
> > ui is much easier and much better supported.
> 
> I was under the impression that installing an engine on a host and later
> adding it as a host to the engine breaks stuff. Otherwise, why do we need
> allinone at all?

1. aio was designed by PM to have working environment right out of installation.

2. aio was introduced as in the past regular host-deploy required rebooting the host.

While (2) is not valid any more, (1) is not something I can address, but sure the meaning was not to do that at upgrade.

Comment 4 Yedidyah Bar David 2014-02-17 15:08:22 UTC

Changed 24334 to prevent all-in-one during upgrade.

Comment 5 Sandro Bonazzola 2014-02-19 12:27:58 UTC

This bug is referenced in ovirt-engine-3.4.0-beta3 logs. Moving to ON_QA

Comment 6 Sandro Bonazzola 2014-03-31 12:33:15 UTC

this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released