On Mon, Jun 15, 2020 at 8:20 PM Gilboa Davara <gilboad(a)gmail.com> wrote:
On Mon, Jun 15, 2020 at 5:18 PM Yedidyah Bar David <didi(a)redhat.com> wrote:
>
> On Mon, Jun 15, 2020 at 4:54 PM Gilboa Davara <gilboad(a)gmail.com> wrote:
> >
> > On Mon, Jun 15, 2020 at 11:46 AM Yedidyah Bar David <didi(a)redhat.com>
wrote:
> > >
> > > Ok, it's failing in the task "Install oVirt Engine package",
which
> > > tries to install/upgrade the package 'ovirt-engine' on the engine
VM.
> > > Can you try to do this manually and see if it works?
> > >
> > > At this stage, the engine VM is on libvirt's default network
> > > (private), you can find the temporary address by searching the log for
> > > local_vm_ip, which is 192.168.1.173, in your log.
> > >
> > > Good luck and best regards,
> > > --
> > > Didi
> > >
> >
> > You are correct.
> > $ dnf install -y ovirt-engine
> > Problem: package ovirt-engine-4.4.0.3-1.el8.noarch requires
> > apache-commons-jxpath, but none of the providers can be installed
> > - conflicting requests
> > - package apache-commons-jxpath-1.3-29.module_el8.0.0+30+832da3a1.noarch
> > is excluded
> > (try to add '--skip-broken' to skip uninstallable packages or
> > '--nobest' to use not only best candidate packages)
>
> Is this on the engine machine? Or elsewhere?
>
> Generally speaking, you need, for this, to first enable the module
> 'javapackages-tools'. But assuming that you are deploying the engine
> VM from ovirt-engine-appliance, the image should already have this
> done, so above error should not happen there. No idea why it does, if
> indeed it's there and not e.g. on the host (where you should not need
> to install the engine). Can you please clarify where you try this?
>
> Best regards,
> --
> Didi
>
Managed to find the reason for the failure.
Wrong documentation order in one document [1], missing documentation
on another [2].
[1]
https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_eng...
[2]
https://www.ovirt.org/documentation/installing_ovirt_as_a_self-hosted_eng...
The the first document, the cockpit part (5.2) actually precedes the
oVirt engine module list (5.3).
Section 5.3 is not actually needed, the appliance already includes it.
The second document is missing the modules part.
(Seems to me to include it as well, but again, it's not needed)
Now I can manually install ovirt-engine on the host.
I think you got it wrong. Please see my previous posts in this thread.
In particular:
1. You do not need to install ovirt-engine on the host.
2. You should try to see why it failed, on the engine VM.
3. This engine vm should be left running by the failed deploy process,
and you can find its IP address by searching the setup logs for
'local_vm_ip'. So please find it, ssh to it from the host (using the
root password you supplied), then try 'dnf install ovirt-engine'. If
it fails, try to fix the problem. My guess: Some kind of
networking/mirror/proxy/whatever issue.
For an overview of the current hosted-engine deploy process, you can
have a look at "Hosted Engine 4.3 Deep Dive (Simone Tiraboschi)" in:
https://www.ovirt.org/community/get-involved/resources/slide-decks.html
It was written for 4.3, but most of it applies also for 4.4.
Also:
The engine package is already part of the appliance, so strictly
speaking, we should not try to install it. This is done so that if a
newer version is available (e.g. because you installed an older
appliance image rpm), you upgrade to the newer version.
We have a bug open for allowing to prevent this, not sure about its
current status - see also the discussion in the linked github issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1816619
That said, still no go.
Both cockpit based deployment and command line based deployment (on
the first node) fails.
Log attached.
Thanks. As you can see there, it's still failing for the same reason:
Failed to download metadata for repo 'AppStream'
Good luck and best regards,
--
Didi