Thanks for the input,
It's weird that you see this bug
https://bugzilla.redhat.com/show_bug.cgi?id=1528906 on 4.2.1.6 because it
was already tested and verified on 4.2.1.1
I will check this again..
On Tue, Feb 13, 2018 at 3:09 PM, wrote:
>
> I did not see I had to enable
I did not see I had to enable another repo to get this update, so I was sure I
had the latest version available !
After adding it, things went a lot better and I was able to update the engine
and all the nodes flawlessly to version 4.2.1.6-1.el7.centos Thanks a lot for
your help ! The "no
"no default route" bug was fixed only on 4.2.1
Your current version doesn't have the fix
On Mon, Feb 12, 2018 at 11:09 AM, wrote:
>
>
>
>
> Le 12-Feb-2018 08:06:43 +0100, jbe...@redhat.com a écrit:
>
> > This option relevant only for the upgrade from 3.6 to 4.0(engine had
Le 12-Feb-2018 08:06:43 +0100, jbe...@redhat.com a crit:
> This option relevant only for the upgrade from 3.6 to 4.0(engine had
> different OS major versions), it all other cases the upgrade flow very
> similar to upgrade flow of standard engine environment.
>
>
> 1. Put hosted-engine
Hi, This is the whole message. Here you get the whole output of the process. I
runned these commands on the node hosting the engine vm. But if there is a more
efficient workflow, I am interrested in it ! # yum -y update Modules
complmentaires chargs : fastestmirror
base | 3.6 kB 00:00:00
> This option relevant only for the upgrade from 3.6 to 4.0(engine had
> different OS major versions), it all other cases the upgrade flow very
> similar to upgrade flow of standard engine environment.
>
>
> 1. Put hosted-engine environment to GlobalMaintenance(you can do it via
> UI)
>
This option relevant only for the upgrade from 3.6 to 4.0(engine had
different OS major versions), it all other cases the upgrade flow very
similar to upgrade flow of standard engine environment.
1. Put hosted-engine environment to GlobalMaintenance(you can do it via
UI)
2. Update engine
Jiri, can you maybe assist the user with his upgrade problem?
I'm not familiar with the error and not sure how could it be that he is
already has a cluster version 4.2 prior upgrading the engine to 4.2..unless
i didn't understood it completely..
Thanks,
On Fri, Feb 9, 2018 at 1:21 PM,
Hi, Could someone explain me at least what "Cluster PROD is at version 4.2
which is not supported by this upgrade flow. Please fix it before upgrading."
means ? As far as I know 4.2 is the most recent branch available, isn't it ?
Regards
Le 08-Feb-2018 09:59:32 +0100, mbur...@redhat.com a
In fact I don't know what flow should be followed. I have found several
documentations, but most deal with older version so I am not sure I am doing
right.
Is there a working documented procedure somewhere ?
Le 08-Feb-2018 11:17:06 +0100, mbur...@redhat.com a crit:
Thanks, I'm not so
Thanks,
I'm not so familiar with the hosted-engine --upgrade-appliance flow, can
someone from the list that is familiar with such flow assist?
On Thu, Feb 8, 2018 at 12:10 PM, wrote:
> Hi,
>
> I installed my nodes with the latest packages available in repositories.
> Then
Hi, I installed my nodes with the latest packages available in repositories.
Then I installed the self-hosted engine on one of them, created the cluster and
added the second node. When I encountered these network config problems and
saw your answer, I thougt it was time to update some
Not sure i understand from which version you trying to upgrade and what is
the exact upgrade flow, if i got it correctly, it is seems that you
upgraded the hosts to 4.2, but engine still 4.1?
What exactly the upgrade steps, please explain the flow., what have you
done after upgrading the hosts? to
Hi, Thanks a lot for your answer.I applied some updates at node level, but
I forgot to upgrade the engine ! When I try to do so I get a strange error :
"Cluster PROD is at version 4.2 which is not supported by this upgrade flow.
Please fix it before upgrading." Here are the installed
Hi
This is a bug and it was already fixed in 4.2.1.1-0.1.el7 -
https://bugzilla.redhat.com/show_bug.cgi?id=1528906
The no default route bug was fixed in -
https://bugzilla.redhat.com/show_bug.cgi?id=1477589
Thanks,
On Wed, Feb 7, 2018 at 1:15 PM, wrote:
>
> Hi,
> I am
15 matches
Mail list logo