Hi Matthias,
Basically, ovirt-node-ng is shipped as an image, and imgbased then syncs
some files to the new lv so the user will get a new working image without
breaking his configuration. It could be that some files were sync'ed
across wrong, can you please attache /tmp/imgbased.log ? Also,
Hi Yuval,
i updated my nodes from 4.1.3 to 4.1.6 today and noticed that the
> /etc/yum.repos.d/ovirt-4.1-pre-dependencies.repo
> /etc/yum.repos.d/ovirt-4.1-pre.repo
files i moved away previously reappeared after rebooting, so i'm getting
updates to
Yes that would do it, thanks for the update :)
On Thu, Aug 31, 2017 at 5:21 PM, Matthias Leopold <
matthias.leop...@meduniwien.ac.at> wrote:
> Hi,
>
> all of the nodes that already made updates in the past have
>
> /etc/yum.repos.d/ovirt-4.1-pre-dependencies.repo
>
Hi,
all of the nodes that already made updates in the past have
/etc/yum.repos.d/ovirt-4.1-pre-dependencies.repo
/etc/yum.repos.d/ovirt-4.1-pre.repo
i went through the logs in /var/log/ovirt-engine/host-deploy/ and my own
notes and discovered/remembered that this being presented with RC
Hi,
Don't quite understand how you got to that 4.1.6 rc, it's only available in
the pre release repo, can you paste the yum repos that are enabled on your
system ?
Thanks,
Yuval.
On Thu, Aug 31, 2017 at 4:19 PM, Matthias Leopold <
matthias.leop...@meduniwien.ac.at> wrote:
> Hi,
>
> thanks a
Hi,
thanks a lot.
So i understand everything is fine with my nodes and i'll wait until the
update GUI shows the right version to update (4.1.5 at the moment).
Regards
Matthias
Am 2017-08-31 um 14:56 schrieb Yuval Turgeman:
Hi,
oVirt node ng is shipped with a placeholder rpm preinstalled.
Hi,
oVirt node ng is shipped with a placeholder rpm preinstalled.
The image-update rpms obsolete the placeholder rpm, so once a new
image-update rpm is published, yum update will pull those packages. So you
have 1 system that was a fresh install and the others were upgrades.
Next, the post
hi,
i still don't completely understand the oVirt Node update process and
the involved rpm packages.
We have 4 nodes, all running oVirt Node 4.1.3. Three of them show as
available updates
'ovirt-node-ng-image-update-4.1.6-0.1.rc1.20170823083853.gitd646d2f.el7.centos'
(i don't want run
8 matches
Mail list logo
