(Re-adding the list)

On Sun, Feb 5, 2017 at 12:23 PM, Shalabh Goel <shalabhgoe...@gmail.com> wrote:
> Yes and no. First I did install ovirtrelease41 rpm in both nodes. Then in
> one of the nodes, I started upgrade from the court engine administration
> portal.
> The second node developed some other problem and hence I had to remove it
> from the court engine and I reinstalled ovirt 4.0.3 ng and then upgraded it
> before adding it to the engine. It got upgraded successfully and I rebooted
> and logged into 4.1 too.
>
> But I am getting the same error for both the nodes. The first one was moved
> to non operational state by the engine. The second one is not getting added.
>
> My VMs are in a third storage node *(NFS). I have not yet upgraded it since
> other two upgrades failed.
>
> BTW I have changed the compatibility of cluster and data centre to 4.1.

Your current state is not fully clear. Can you please describe it in detail?

How many hosts do you have? What's the state of each in the engine?

Do you have VMs that are ok? And if so, is it important to not stop them?

In any case, if you have hosts that do not have VMs on them, and in whatever
state, it's probably simplest to move them to maintenance, remove from the
engine, reinstall the OS, then try to add them.

If you try to add a host and it fails, please check/attach engine.log and
host-deploy log.

If you fail to activate a host, please check/attach engine.log.

Best,

>
> Thanks
>
> Shalabh Goel
>
> On 05-Feb-2017 12:19 PM, "Yedidyah Bar David" <d...@redhat.com> wrote:
>>
>> On Fri, Feb 3, 2017 at 6:35 AM, Shalabh Goel <shalabhgoe...@gmail.com>
>> wrote:
>> > Hi can u just confirm something for me? I had to change the existing
>> > ovirt-4.0 repos to ovirt 4.1 (by replacing 40 by 41 in the repo files).
>>
>> That's mostly ok, but generally you should install ovirt-release41.rpm.
>>
>> It will also add/update ovirt-*-dependencies.repo .
>>
>> > And
>> > then I ran yum update. And rebooted the nodes and booted into
>> > ovirt-node4.1.
>>
>> Didn't you move to maintenance? Were your VMs migrated correctly?
>>
>> > Is the procedure correct?
>> >
>> > Thanks
>> >
>> > Shalabh Goel
>> >
>> > On Thu, Feb 2, 2017 at 2:02 PM, Yedidyah Bar David <d...@redhat.com>
>> > wrote:
>> >>
>> >> On Thu, Feb 2, 2017 at 8:14 AM, Shalabh Goel <shalabhgoe...@gmail.com>
>> >> wrote:
>> >> > Hi
>> >> >
>> >> > Ovirt 4.1 has been released, I want to to know how to upgrade the
>> >> > Ovirt
>> >> > nodes to 4.1. I was able to upgrade ovirt-engine but I could not find
>> >> > how to
>> >> > upgrade node.
>> >>
>> >> Something like:
>> >>
>> >> 1. Move node to maintenance
>> >> 2. Add 4.1 repos
>> >> 3. yum update
>> >> 4. reboot
>> >> 5. Activate (exit maintenance)
>> >>
>> >> See also:
>> >>
>> >> https://www.ovirt.org/node/
>> >> http://www.ovirt.org/node/faq/
>> >>
>> >> If in "node" you referred to ovirt-node, and not a regular OS install,
>> >> then
>> >> the flow is exactly the same, but what actually happens inside it is
>> >> very
>> >> different - the entire OS image is replaced.
>> >>
>> >> You might want to check also:
>> >>
>> >>
>> >>
>> >> http://www.ovirt.org/develop/release-management/features/engine/upgrademanager/
>> >>
>> >> Best,
>> >> --
>> >> Didi
>> >
>> >
>> >
>> >
>> > --
>> > Shalabh Goel
>>
>>
>>
>> --
>> Didi



-- 
Didi
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Reply via email to