You can safely upgrade all machines, this is just version check error.

On 09.12.2015 17:30, Prasun Gera wrote:
Thanks! That worked. The command passed, and I don't see any other odd behaviour yet. I'll wait for a new fixed errata before upgrading the other node. That should be OK right ? i.e. Running replicas on slightly different versions.

On Wed, Dec 9, 2015 at 8:22 AM, Martin Basti <mba...@redhat.com <mailto:mba...@redhat.com>> wrote:

    Run upgrade manually, this is just error in checking function,
    obviously 4.2.0-15.el7_2.3 is never than 4.2.0-15.el7


    On 09.12.2015 17:21, Prasun Gera wrote:
    Before I try this on the actual node, would it be better to roll
    back the last yum transaction ? I want to do whatever is safer.

    On Wed, Dec 9, 2015 at 8:14 AM, Martin Basti <mba...@redhat.com
    <mailto:mba...@redhat.com>> wrote:



        On 09.12.2015 16:32, Prasun Gera wrote:
        Ran yum update today. Pulled in
        https://rhn.redhat.com/errata/RHBA-2015-2562.html.

        Seeing this error:

        2015-12-09T15:21:02Z DEBUG The ipa-server-upgrade command
        failed, exception: ScriptError: ("Unable to execute IPA
        upgrade: data are in newer version than IPA (data version
        '4.2.0-15.el7', IPA version '4.2.0-15.el7_2.3')", 1)
        2015-12-09T15:21:02Z ERROR ("Unable to execute IPA upgrade:
        data are in newer version than IPA (data version
        '4.2.0-15.el7', IPA version '4.2.0-15.el7_2.3')", 1)
        "/var/log/ipaupgrade.log" 54696L, 5389464C

        ipactl won't start now. Luckily, I ran the update only on
        one replica. The other node is still running.


        Hello, this is not good, something terrible wrong happened
        with parsing versions.

        You can run upgrade with ipa-server-upgrade
        --skip-version-check or --force





-- 
Manage your subscription for the Freeipa-users mailing list:
https://www.redhat.com/mailman/listinfo/freeipa-users
Go to http://freeipa.org for more info on the project

Reply via email to