[Users] [ovirt-test-day-2] Testing all-in-one feature on f19

[Yedidyah Bar David]

----- Original Message -----
> From: "Itamar Heim" <iheim at redhat.com>
> To: awels at redhat.com, users at ovirt.org
> Sent: Tuesday, February 11, 2014 6:40:33 PM
> Subject: Re: [Users] [ovirt-test-day-2] Testing all-in-one feature on f19
> 
> On 02/11/2014 06:19 PM, Alexander Wels wrote:
> > Same issue for me, I did a minimum fedora 19 install added the appropriate
> > repositories. Completed almost successfully, host didn't come up with vdsm
> > compatibility error message.
> >
> > The vdsm on the host is: vdsm-4.13.3-3.fc19.x86_64
> >
> > I tried the same 3.3 dc/cluster and the host came up immediately.
> >
> > Alexander
> >
> > On Tuesday, February 11, 2014 11:02:37 AM Moti Asayag wrote:
> >> Hi,
> >>
> >> In the 3.4 ovirt-test-day-2 I've tested the all-in-one feature.
> >> I installed the all-in-one setup on a vm.
> >>
> >> The installation ended almost successfully, except of the vdsm service,
> >> where the the host didn't become operational due to lack of support
> >> in clusterLevel >= 3.4:
> >>
> >> Feb 11 15:51:52 localhost vdsm root ERROR VIR_MIGRATE_ABORT_ON_ERROR not
> >> found in libvirt, support for clusterLevel >= 3.4 is disabled. For Fedora
> >> 19 users, please consider upgrading libvirt from the virt-preview
> >> repository
> >>
> >> Once I created a new 3.3 DC and configured a local storage, the local host
> >> become operational and I was able to create a vm and to run it.
> >>
> >> Thanks,
> >> Moti
> >> _______________________________________________
> >> Users mailing list
> >> Users at ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/users
> >
> > _______________________________________________
> > Users mailing list
> > Users at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
> 
> no one tested on .el6?

I know that <OaaSvc> did, had a problem with enabling it during upgrade
(as opposed to during a clean setup), and I reproduced and opened a bug [1]
and pushed a fix [2]. With the fix I had another problem [3] which seems
to Yaniv like a duplicate and is probably solved in vdsm master branch.

As you can see in [1], Alon objected to allowing all-in-one during upgrade,
which led me to wonder what we need all-in-one for at all. I still didn't
test adding to the engine as a host the host on which it's installed, but if
indeed this works well, there is practically no reason for all-in-one anymore,
and we might better get rid of it, as adding the host after setup is probably
simpler.

[1] https://bugzilla.redhat.com/1063869 - allinone fails on upgrade - no admin password
[2] http://gerrit.ovirt.org/24334 - ask for admin password
[3] https://bugzilla.redhat.com/1063886 - 'vdsm-tool configure --force' does not configure sanlock sometimes
-- 
Didi