On Tue, May 14, 2019 at 2:33 PM wrote:
> Hi,
>
> thanks to both - downgrading did not work, there is too much that needs to
> be removed and the old repos are deprecated and only available via eus. So,
> I'll setup the three node first and try to import the old domain there.
>
> > Yes, for this
Hi,
thanks to both - downgrading did not work, there is too much that needs to be
removed and the old repos are deprecated and only available via eus. So, I'll
setup the three node first and try to import the old domain there.
> Yes, for this specific case the best option is to use latest
On Tue, May 14, 2019 at 12:25 PM Yedidyah Bar David wrote:
> On Tue, May 14, 2019 at 12:25 PM wrote:
> >
> > > I'd personally first try to fix the engine<->vdsm comm issue.
> >
> > I fully agree. I might then take exports of all VMs and do a fresh start
> over. I'm not sure the upgrade
On Tue, May 14, 2019 at 12:25 PM wrote:
>
> > I'd personally first try to fix the engine<->vdsm comm issue.
>
> I fully agree. I might then take exports of all VMs and do a fresh start
> over. I'm not sure the upgrade instructions work, as the upgrade for 3.6->4.0
> already activates much newer
> I'd personally first try to fix the engine<->vdsm comm issue.
I fully agree. I might then take exports of all VMs and do a fresh start over.
I'm not sure the upgrade instructions work, as the upgrade for 3.6->4.0 already
activates much newer content. For example the quoted --upgrade-appliance
On Tue, May 14, 2019 at 11:10 AM wrote:
>
> Hi,
>
> yes, the host seems to have been updated.
>
> vdsm-api-4.30.13-1.el7ev.noarch
> vdsm-http-4.30.13-1.el7ev.noarch
> vdsm-hook-vmfex-dev-4.30.13-1.el7ev.noarch
> vdsm-network-4.30.13-1.el7ev.x86_64
> vdsm-common-4.30.13-1.el7ev.noarch
>
Hi,
yes, the host seems to have been updated.
vdsm-api-4.30.13-1.el7ev.noarch
vdsm-http-4.30.13-1.el7ev.noarch
vdsm-hook-vmfex-dev-4.30.13-1.el7ev.noarch
vdsm-network-4.30.13-1.el7ev.x86_64
vdsm-common-4.30.13-1.el7ev.noarch
vdsm-yajsonrpc-4.30.13-1.el7ev.noarch
On Tue, May 14, 2019 at 9:20 AM wrote:
>
> Hi,
>
> update: I managed to get the old engine running (3.6), but it is not
> communicating with the host. Do I need to downgrade the host and/or somehow
> re-enroll it to the engine?
I didn't understand the current state of your host, but if it's
Hi,
update: I managed to get the old engine running (3.6), but it is not
communicating with the host. Do I need to downgrade the host and/or somehow
re-enroll it to the engine?
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to
If you can: restart your setup from scratch with at least 3 hosts. Really. If
you don't face harsh consequences for doing so. It isn't just worth the hassle
and pain. Use at least 3 hosts because: A node can corrupt due to many reasons.
Natural causes, self inflicted ones. A corrupt node can
10 matches
Mail list logo
