Got the octopi error fixed by downgrading until I found a version that the
3.2 yum pkgs played nice with. Trying to get past a new problem with the
version of jboss:
**Error: Upgrade failed, rolling back**
**Reason: Test Transaction Errors: file
/usr/share/jboss-as-7.1.1.Final/bin/init.d/jboss-as.conf from install of
jboss-as-7.1.1-11.el6.x86_64 conflicts with file from package
ovirt-engine-jbossas711-1-3.el6.alt.x86_64
**
Will work on the conflict but any help is appreciated.
On 11/30/13, 11:17 PM, "Karl Mozurkewich" <karl(a)utropicmedia.com> wrote:
Finally got the downgrades cleaned up and see this in the error log
for
engine-upgrade:
YumBaseError: [u'otopi-java-1.1.0-0.0.master.el6.noarch requires otopi =
1.1.0-0.0.master.el6’]
Thoughts?
Already have this installed:
Package matching otopi-1.1.0-0.0.master.el6.noarch already installed.
Checking for update.
On 11/26/13, 2:33 AM, "Sandro Bonazzola" <sbonazzo(a)redhat.com> wrote:
>Il 25/11/2013 16:53, Karl Mozurkewich ha scritto:
>> I¹m on Cent 6.4 and used the AIO rpm install.
>>
>> How do I upgrade to 3.2 then to 3.3? (engine-udgrade? Etc.)
>
>For upgrading to 3.2 you'll need 3.2 stable repository.
>So, first step is disable 3.3 / stable repository and enable 3.2:
>
>[ovirt-32]
>name=Stable builds of the oVirt 3.2 project
>baseurl=http://ovirt.org/releases/3.2/rpm/EL/$releasever/
>enabled=1
>skip_if_unavailable=1
>gpgcheck=0
>
>Then "yum update ovirt-engine-setup" it should install
>ovirt-engine-setup-3.2.3-1.el6.noarch.rpm
>
>if you have already updated to 3.3.x please use distro-sync or downgrade
>instead of update.
>
>Then run engine-upgrade. This will upgrade your system to latest 3.2.
>
>Once you've all working on 3.2, enable 3.3/stable repository, then just
>"yum update ovirt-engine-setup" followed by engine-setup will upgrade to
>latest 3.3.
>
>
>
>>
>>
>> Thanks.
>>
>>
>>
>>
>>
>>
>>
>> On 11/25/13, 4:25 AM, "Sandro Bonazzola" <sbonazzo(a)redhat.com>
wrote:
>>
>>> Il 25/11/2013 03:30, Karl Mozurkewich ha scritto:
>>>> Hi,
>>>>
>>>>
>>>> Trying to upgrade from 3.1 to 3.3 and am running engine-setup, but
>>>>it¹s
>>>> bombing at the following:
>>>
>>> Hi,
>>> just to be sure, are you on Fedora and just running yum upgrade from
>>>the
>>> 3.1 version provided by Fedora?
>>> Because if you're not just updating rpms, the direct upgrade process
>>>from
>>> 3.1 to 3.3 through engine-setup is not supported.
>>> In this case you should upgrade to 3.2 before upgrading to 3.3.
>>>
>>>
>>>>
>>>>
>>>> [ INFO ] Stage: Setup validation
>>>> During execution engine service will be stopped (OK,
>>>>Cancel)
>>>> [OK]:
>>>> [ ERROR ] Failed to execute stage 'Setup validation': Cannot
get
>>>> JAVA_HOME ([])
>>>> [ INFO ] Stage: Clean up
>>>> Log file is located at
>>>> /var/log/ovirt-engine/setup/ovirt-engine-setup-20131124212809.log
>>>> [ INFO ] Stage: Pre-termination
>>>> [ INFO ] Stage: Termination
>>>> [ ERROR ] Execution of upgrade failed
>>>>
>>>>
>>>> Should be a simple fix, but where does it get JAVA_HOME from?
>>>>Setting
>>>> it in the running shell doesn¹t work. (export JAVA_HOME, etc.) Also
>>>> wondering
>>>> why it can¹t find it if the engine is currently workingŠ
>>>>
>>>>
>>>>
>>>> Thanks.
>>>>
>>>> -K
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users(a)ovirt.org
>>>>
http://lists.ovirt.org/mailman/listinfo/users
>>>>
>>>
>>>
>>> --
>>> Sandro Bonazzola
>>> Better technology. Faster innovation. Powered by community
>>>collaboration.
>>> See how it works at
redhat.com
>>
>
>
>--
>Sandro Bonazzola
>Better technology. Faster innovation. Powered by community collaboration.
>See how it works at
redhat.com
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users