[ovirt-users] Re: upgrade issue

Hi Jingjie, You're mixing a normal centos host with an ovirt-node installation. If you'd like to use ovirt with centos nodes, you simply need to do yum update. The ovirt-node-ng-image-update is an update rpm for a host that is installed with ovirt-node-ng-installer.iso. Thanks, Yuval On Wed,

[ovirt-users] Re: Upgrading from oVirt-Node 4.2.8 to latest

ntation on how to troubleshot the cause for this ? >> > > it's probably a bug on the update flow missing to update a line with the > version to be displayed but the node should be correctly updated to 4.3.6 > after completion and reboot. > Adding +Nir Levy and +Yuval Turgeman > for

[ovirt-users] Re: ovirt node install

Looks like the fix missed the release, it will be fixed on the next version. For now, you can try to either install the latest nightly iso, or manually install the latest ovirt-node-ng-nodectl rpm on your existing installation On Monday, August 19, 2019, wrote: > I concur with Paul, I got the

[ovirt-users] Re: ovirt node install

You just hit [1] - can you try this with the latest 4.3.5 ? [1] https://bugzilla.redhat.com/show_bug.cgi?id=1728998 On Tue, Aug 13, 2019 at 6:57 PM Staniforth, Paul < p.stanifo...@leedsbeckett.ac.uk> wrote: > Hello, > > on the latest version of the oVirt-node install running >

[ovirt-users] Re: ovirt-engine-appliance ova

What system are you running `make` on ? There's some logic before that iirc (like which repos to install from etc). Basically, ovirt-appliance/automation/build-artifacts.sh is the place to go. On Tuesday, July 23, 2019, Yedidyah Bar David wrote: > On Mon, Jul 22, 2019 at 11:53 PM Jingjie

[ovirt-users] Re: Hosted engine setup: "Failed to configure management network on host Local due to setup networks failure"

Hi Edward, you're hitting [1] - it will be included in the next appliance [1] https://bugzilla.redhat.com/show_bug.cgi?id=1718399 On Monday, June 17, 2019, Edward Berger wrote: > The hosted engine is created in two steps, first as a 192.168.x.x address > as a local VM on the host, then it

[ovirt-users] Re: Installing oVirt on Physical machine V4.3

How are you installing it (iso, pxe) ? On Fri, Feb 22, 2019, 17:15 wrote: > Motherboard : ASUS M5A78L-M/USB3 > UEFI Support: No > Processor : AMD Fx-4300 (3800MGz) > : Virtualization Enabled in BIOS > NIC :

[ovirt-users] Re: update to 4.2.8 fails

It's mentioned in the release notes [1], probably worth to mention it in the general upgrade guide [1] https://ovirt.org/release/4.3.0/#install--upgrade-from-previous-versions On Fri, Feb 15, 2019 at 1:05 PM Greg Sheremeta wrote: > > On Thu, Feb 14, 2019 at 11:06 PM Vincent Royer > wrote: >

[ovirt-users] Re: oVirt Node 4.2.7 upgrade fails with broken dependencies ?

For ovirt-node, the only package that should be downloaded as an update is the ovirt-node-ng-image-update rpm. It's should be set in the yum repo files using includepkgs. On Wed, Nov 14, 2018 at 5:30 PM Sandro Bonazzola wrote: > > > Il giorno mer 14 nov 2018 alle ore 16:27 Jayme ha > scritto:

[ovirt-users] Re: Diary of hosted engine install woes

For debugging purposes try to download directly with curl/wget and if that works, I would try to increase the timeout in yum.conf On Mon, Oct 8, 2018 at 6:05 PM Simone Tiraboschi wrote: > > > On Mon, Oct 8, 2018 at 5:00 PM wrote: > >> Thanks for the suggestion Simone. Tried sudo yum install

[ovirt-users] Re: upgrade 4.2.6 to 4.2.6.1: node status degraded

Wait, root disk's uuid is different ?? On Mon, Sep 24, 2018, 15:39 Yuval Turgeman wrote: > Bootid is there, so that's not the issue.. can you run `imgbase --debug > check` ? > > On Mon, Sep 24, 2018, 15:22 KRUECKEL OLIVER > wrote: > >> >> -----

[ovirt-users] Re: upgrade 4.2.6 to 4.2.6.1: node status degraded

Bootid is there, so that's not the issue.. can you run `imgbase --debug check` ? On Mon, Sep 24, 2018, 15:22 KRUECKEL OLIVER wrote: > > -- > *Von:* Yuval Turgeman > *Gesendet:* Montag, 24. September 2018 11:29:31 > *An:* Sandro Bonazzola > *Cc

[ovirt-users] Re: upgrade 4.2.6 to 4.2.6.1: node status degraded

Can you share the output from `cat /proc/cmdline` and perhaps the grub.conf ? Imgbased adds a bootid and perhaps it's missing for some reason On Mon, Sep 24, 2018, 11:59 Sandro Bonazzola wrote: > Adding some people who may help understanding what happened and work on a > solution for this. > >

[ovirt-users] Re: Unable to upgrade ovirt-node from 4.2.3

Glad to hear, thanks for the update ! On Mon, Sep 17, 2018, 18:13 Benedetto Vassallo wrote: > Thank you guys, it worked! > > > Def. Quota Yuval Turgeman : > > Try to first remove the LV for /var/crash or mount it, then remove any > base that is not used (imgbase base --remo

[ovirt-users] Re: Unable to upgrade ovirt-node from 4.2.3

Try to first remove the LV for /var/crash or mount it, then remove any base that is not used (imgbase base --remove ), then yum update again. Documented here (for other LVs):

[ovirt-users] Re: [ANN] oVirt Engine 4.2.6 async update is now available

The failure was caused because you had /var/log LV that was not mounted for some reason (was that manual by any chance?). onn/var_crash was created during the update and removed successfully because of the var_log issue. The only question is why it didn't clean up the onn/ovirt-node-ng-4.2.6,

[ovirt-users] Re: [ANN] oVirt Engine 4.2.6 async update is now available

Hi Paul, Can you share the entire imgbased.log ? Thanks, Yuval On Thu, Sep 13, 2018 at 4:51 PM, Sandro Bonazzola wrote: > > Il giorno gio 13 set 2018 alle ore 15:33 > ha scritto: > >> Hello, >> I can't upgrade to 4.2.6 it doesn't have the base layer and I >> have to "lvremove

[ovirt-users] Re: oVirt Node 4.2.3.1. to 4.2.5 upgrade trouble, log attached

l send as clear > of a bug report with logs as possible. > > Thank you for your help, > > Matt > > > > > On 08/27/2018 12:37 AM, Yuval Turgeman wrote: > > Hi Matt, > > I just went over the log you sent, couldn't find anything else other than > the seman

[ovirt-users] Re: oVirt Node 4.2.3.1. to 4.2.5 upgrade trouble, log attached

ing this I'm happy to assist in finding the > cause. > > Is there anything else I can do to assist? > > Thanks, > > Matt > > > > > > On 08/21/2018 12:38 AM, Yuval Turgeman wrote: > > Hi again Matt, > > I was wondering what `semanage permissive -a setfil

[ovirt-users] Re: ovirt-node-ng-image-update 4.2.4 to 4.2.5.1 fails

Thanks for the update, Glenn, I'm glad it works ! :) On Wed, Aug 22, 2018 at 10:54 PM, Glenn Farmer wrote: > Yuval, thanks for you assistance & guidance. > > I just wanted to confirm that with /var/crash mounted (and leftover > v4.2.5.1 LV from previous failed installation removed) - I was able

[ovirt-users] Re: oVirt Node 4.2.3.1. to 4.2.5 upgrade trouble, log attached

les_t > [ ~]# echo $? > 0 > > Please let me know if there is anything else I can do to assist, > > Matt > > > > > > On 08/20/2018 08:19 AM, Yuval Turgeman wrote: > > Hi Matt, > > Can you attach the output from the following line > > # sema

[ovirt-users] Re: oVirt Node 4.2.3.1. to 4.2.5 upgrade trouble, log attached

Hi Matt, Can you attach the output from the following line # semanage permissive -a setfiles_t Thanks, Yuval. On Fri, Aug 17, 2018 at 2:26 AM, Matt Simonsen wrote: > Hello all, > > I've emailed about similar trouble with an oVirt Node upgrade using the > ISO install. I've attached the

[ovirt-users] Re: ovirt-node-ng-image-update 4.2.4 to 4.2.5.1 fails

Hi Glenn, Can you please attach /var/log/imgbased.log ? Thanks, Yuval. On Mon, Aug 20, 2018 at 5:40 PM, Douglas Schilling Landgraf < dland...@redhat.com> wrote: > Adding Yuval and Ryan. > > On Sun, 2018-08-19 at 07:34 +, Glenn Farmer wrote: > > yum update ends with: > > > > warning:

[ovirt-users] Re: oVirt 4.2.3 to 4.2.4 failed

trims also LV thin pool volumes, nice :-) > > Many thanks to you, i have learned a lot of lvm. > > Oliver > > > Am 03.07.2018 um 22:58 schrieb Yuval Turgeman : > > > > OK Good, this is much better now, but ovirt-node-ng-4.2.4-0.20180626.0+1 > still exists without its

[ovirt-users] Re: oVirt 4.2.3 to 4.2.4 failed

gt; I did it, with issues, see attachment. > > > > > Am 03.07.2018 um 22:25 schrieb Yuval Turgeman : > > Hi Oliver, > > I would try the following, but please notice it is *very* dangerous, so a > backup is probably a good idea (man vgcfgrestore)... > > 1. vgcfgrestore

[ovirt-users] Re: oVirt 4.2.3 to 4.2.4 failed

?) 7. nodectl info to make sure everything is ok 8. reinstall the image-update rpm Thanks, Yuval. On Tue, Jul 3, 2018 at 10:57 PM, Yuval Turgeman wrote: > Hi Oliver, > > The KeyError happens because there are no bases for the layers. For each > LV that ends with a +1, there shou

[ovirt-users] Re: oVirt 4.2.3 to 4.2.4 failed

-monster Twi-ao <279,38g > > > [pool00_tmeta] onn_ovn-monster ewi-ao 1,00g > > > root onn_ovn-monster Vwi-a-tz-- <252,38g > pool00 1,24 > > swap

[ovirt-users] Re: oVirt 4.2.3 to 4.2.4 failed

stions on how to move forward with the > error regarding the pool capacity? I'm not sure if this is a legitimate > error or problem in the upgrade process. > > Thanks, > > Matt > > > > > On 07/03/2018 03:58 AM, Yuval Turgeman wrote: > > Not sure this is the pr

[ovirt-users] Re: oVirt 4.2.3 to 4.2.4 failed

d deactivated var_crash LV. > > * I activated and mount it to /var/crash via /etc/fstab. > * /var/crash was empty, and LV has already ext4 fs. > var_crashonn_ovn-monster Vwi-aotz-- 10,00g > pool002,86 > > > *

[ovirt-users] Re: oVirt 4.2.3 to 4.2.4 failed

/usr/lib/python2.7/site-packages/imgbased/imgbase.py", > line 310, in add_base > > new_base_lv = pool.create_thinvol(new_base.lv_name, size) > > File > > "/tmp/tmp.mzQBYouvWT/usr/lib/python2.7/site-packages/imgbased/lvm.py", > line 324, in create_t

[ovirt-users] Re: oVirt 4.2.3 to 4.2.4 failed

ot create > new thin volume, free space in thin pool onn_node1-g8-h4/pool00 reached > threshold. > > 2018-07-02 12:21:10,069 [DEBUG] (MainThread) Calling binary: (['umount', > '-l', u'/tmp/mnt.ZYOjC'],) {} > > > Thanks > > Matt > > > > > > On 07/02/2018 10

[ovirt-users] Re: oVirt 4.2.3 to 4.2.4 failed

e space in thin pool onn_node1-g8-h4/pool00 reached > threshold. > > 2018-07-02 12:21:10,069 [DEBUG] (MainThread) Calling binary: (['umount', > '-l', u'/tmp/mnt.ZYOjC'],) {} > > > Thanks > > Matt > > > > > > On 07/02/2018 10:55 AM, Yuval Turgeman wrot

[ovirt-users] Re: oVirt 4.2.3 to 4.2.4 failed

ide/recovering_from_failed_nist-800_upgrade On Mon, Jul 2, 2018 at 8:12 PM, Oliver Riesener < oliver.riese...@hs-bremen.de> wrote: > Hi, > > i attached my /tmp/imgbased.log > > Sheers > > Oliver > > > > Am 02.07.2018 um 13:58 schrieb Yuval Turgeman : > > Looks like the upgrade

[ovirt-users] Re: oVirt 4.2.3 to 4.2.4 failed

File > "/tmp/tmp.mzQBYouvWT/usr/lib/python2.7/site-packages/imgbased/utils.py", > line 390, in lvcreate > return self.call(["lvcreate"] + args, **kwargs) > File > "/tmp/tmp.mzQBYouvWT/usr/lib/python2.7/site-packages/imgbased/utils.py", > line 378,

[ovirt-users] Re: oVirt 4.2.3 to 4.2.4 failed

Looks like the upgrade script failed - can you please attach /var/log/imgbased.log or /tmp/imgbased.log ? Thanks, Yuval. On Mon, Jul 2, 2018 at 2:54 PM, Sandro Bonazzola wrote: > Yuval, can you please have a look? > > 2018-06-30 7:48 GMT+02:00 Oliver Riesener : > >> Yes, here is the same. >>

Re: [ovirt-users] oVirt Node 4.1.8 -> 4.2 upgrade

Hi Luca, We updated the FAQ [1] with a small script to help upgrade between major releases. [1] https://www.ovirt.org/node/faq/ On Mon, Jan 15, 2018 at 10:21 AM, Luca 'remix_tj' Lorenzetto < lorenzetto.l...@gmail.com> wrote: > > > On Thu, Jan 11, 2018 at 2:31 PM, Ryan Barry

Re: [ovirt-users] oVirt NGN image customization troubles

Recent versions of livemedia-creator use qemu directly instead of libvirt, and I think I saw a problem there also, but didn't get to fix it just yet. You can use virt-builder to install a centos vm, or use an el7-based mock environment. You can follow the jenkins job here [1], basically you need

Re: [ovirt-users] How to simulate update of ng node from 4.1.7 to 4.1.8

Install using the iso as you would, and if you can, try to grab the image update rpm for 4.1.8 [1], and just install it with `rpm -Uhv`. If you'd rather use the iso, you will need to mount it, and install the ovirt-node-ng squashfs in the same manner that the image-update rpm installs it (rpm -qp

Re: [ovirt-users] Ovirt 4.2 and host console

Hi As you can see from the systemctl status, the difference is caused due to the preset rule for cockpit.socket, which is enabled on the node-ng based system, and disabled on your regular centos based system. If you take a look at the cockpit postinstall script, you'd see something like:

Re: [ovirt-users] Failed to open grubx64.efi

Glad to hear, thanks for the update ! :) On Tue, Dec 12, 2017 at 1:20 PM, Luca 'remix_tj' Lorenzetto < lorenzetto.l...@gmail.com> wrote: > On Thu, Nov 23, 2017 at 10:41 AM, Luca 'remix_tj' Lorenzetto > <lorenzetto.l...@gmail.com> wrote: > > > > On Wed, Nov 22, 20

Re: [ovirt-users] oVirt Node ng upgrade failed

ext week. Thanks for your help ;) ------ *Von:* Yuval Turgeman <yuv...@redhat.com> *Gesendet:* Donnerstag, 30. November 2017 09:22:39 *An:* Kilian Ries *Cc:* users *Betreff:* Re: [ovirt-users] oVirt Node ng upgrade failed Looks like it, yes - we try to add setfiles_t to

Re: [ovirt-users] ovirt-node-ng-update

2 more questions - 1. Which ovirt repos are enabled on your node ? 2. Can you share the output from `rpm -qa | grep ovirt-node-ng` ? Thanks, Yuval. On Thu, Nov 30, 2017 at 11:02 AM, Nathanaël Blanchet <blanc...@abes.fr> wrote: > > > Le 30/11/2017 à 08:58, Yuval Turgeman a

Re: [ovirt-users] oVirt Node ng upgrade failed

e problem? :/ > -- > *Von:* Yuval Turgeman <yuv...@redhat.com> > *Gesendet:* Donnerstag, 30. November 2017 09:13:34 > *An:* Kilian Ries > *Cc:* users > > *Betreff:* Re: [ovirt-users] oVirt Node ng upgrade failed > > Kilian, did you disable selinux by any chance ? (selinux=0 o

Re: [ovirt-users] oVirt Node ng upgrade failed

Kilian, did you disable selinux by any chance ? (selinux=0 on boot) ? On Thu, Nov 30, 2017 at 9:57 AM, Yuval Turgeman <yuv...@redhat.com> wrote: > Looks like selinux is broken on your machine for some reason, can you > share /etc/selinux ? > > Thanks, > Yuval. > > On T

Re: [ovirt-users] ovirt-node-ng-update

Hi, Which version are you using ? Thanks, Yuval. On Wed, Nov 29, 2017 at 4:17 PM, Nathanaël Blanchet wrote: > Hi all, > > I didn't find any explicit howto about upgrade of ovirt-node, but I may > mistake... > > However, here is what I guess: after installing a fresh

Re: [ovirt-users] oVirt Node ng upgrade failed

Looks like selinux is broken on your machine for some reason, can you share /etc/selinux ? Thanks, Yuval. On Tue, Nov 28, 2017 at 6:31 PM, Kilian Ries <m...@kilian-ries.de> wrote: > @Yuval Turgeman > > > ### > > > [17:27:10][root@vm5:~]$semanage permissive -a set

Re: [ovirt-users] oVirt Node ng upgrade failed

Hi, Can you try to run on your 4.1.1 `semanage permissive -a setfiles_t` and share your output ? Thanks, Yuval On Fri, Nov 24, 2017 at 11:01 AM, Kilian Ries wrote: > This is the imgbased.log: > > > https://www.dropbox.com/s/v9dmgz14cpzfcsn/imgbased.log.tar.gz?dl=0 > > Ok,

Re: [ovirt-users] Failed to open grubx64.efi

t.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/drivers/firmware/efi/efi.c?h=v3.10.108#n90 [3] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/arch/x86/kernel/setup.c#n930 On Tue, Nov 21, 2017 at 8:57 PM, Yuval Turgeman <yuv...@redhat.com> wro

Re: [ovirt-users] Failed to open grubx64.efi

> On Tue, Nov 21, 2017 at 4:54 PM, Yuval Turgeman <yuv...@redhat.com> wrote: > > Hi, > > > > I tried to recreate this without success, i'll try with different hw > > tomorrow. > > The thing is, autopart with thinp doesn't mean that everything is > lv

Re: [ovirt-users] Failed to open grubx64.efi

Hi, I tried to recreate this without success, i'll try with different hw tomorrow. The thing is, autopart with thinp doesn't mean that everything is lvm-thin - /boot should be a regular (primary) partition (for details you can check anaconda's ovirt install class) This could be a bug in anaconda

Re: [ovirt-users] oVirt Node 4.1.6 on IBM x3650 M3

Hi, We did have some problems in the past with efi, but they should be fixed by now. Did you use the ISO for installation ? What error are you seeing - which file is missing there ? Thanks, Yuval. On Thu, Oct 26, 2017 at 11:03 PM, Jonathan Baecker wrote: > Thank you, good

Re: [ovirt-users] oVirt Node update question

ed. the > practical question for me is: how do i get _permanently_ rid of these files > in path "/etc/yum.repos.d/"? > > thanks > matthias > > Am 2017-08-31 um 16:24 schrieb Yuval Turgeman: > >> Yes that would do it, thanks for the update :) &g

Re: [ovirt-users] failed upgrade oVirt node 4.1.3 -> 4.1.5

Hi, Seems to be a bug that was resolved here https://gerrit.ovirt.org/c/80716/ Thanks, Yuval. On Fri, Sep 1, 2017 at 3:55 PM, Matthias Leopold < matthias.leop...@meduniwien.ac.at> wrote: > hi, > > i'm sorry to write to this list again, but i failed to upgrade a freshly > installed oVirt Node

Re: [ovirt-users] oVirt Node update question

seems fine > > Regards > Matthias > > Am 2017-08-31 um 15:25 schrieb Yuval Turgeman: > >> 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 >> you

Re: [ovirt-users] oVirt Node update question

gt; > 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, &g

Re: [ovirt-users] oVirt Node update question

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

Re: [ovirt-users] Python errors with ovirt 4.1.4

Hi, The problem should be solved here: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.1_build-artifacts-el7-x86_64/lastSuccessfulBuild/artifact/exported-artifacts/ Thanks, Yuval. On Fri, Aug 4, 2017 at 12:37 PM, Staniforth, Paul < p.stanifo...@leedsbeckett.ac.uk> wrote: > Hello, > >

Re: [ovirt-users] Python errors with ovirt 4.1.4

Hi David, It's a known bug in nodectl, it was addressed in [1]. If `imgbase check` is ok, your system should be fine. Thanks, Yuval. [1] https://gerrit.ovirt.org/#/c/80037/ On Wed, Aug 2, 2017 at 12:48 PM, david caughey wrote: > Hi Folks, > > I'm testing out the new

Re: [ovirt-users] Regarding Ovirt Node ISO

Hi, Yes, you can find a manifest-rpm file in the exported artifacts for the ovirt-node-ng jobs. Thanks, Yuval. On Jul 28, 2017 8:41 AM, "TranceWorldLogic ." wrote: > Hi, > > I want to know packages list in ovirt node ISO. > Do we have some documentation or some

Re: [ovirt-users] oVirt Node 4.1.2 offering RC update?

Hi, The GA iso is 4.1-2017070915 Thanks, Yuval. On Tue, Jul 11, 2017 at 1:13 AM, Vinícius Ferrão wrote: > May I ask another question? > > I’ve noted two new ISO images of 4.1.3 Node version over here: > http://resources.ovirt.org/pub/ovirt-4.1/iso/ovirt- >

Re: [ovirt-users] node ng upgrade failed

Hi, Can you please attach /tmp/imgbased.log ? Thanks, Yuval. On Mon, Jul 10, 2017 at 11:27 AM, Grundmann, Christian < christian.grundm...@fabasoft.com> wrote: > Hi, > > I tried to update to node ng 4.1.3 (from 4.1.1) which failed > > > > Jul 10 10:10:49 imgbased: 2017-07-10 10:10:49,986

Re: [ovirt-users] ovirt-ng upgrade

Hi, Node-ng is tested and shipped as a complete operating system image, so enabling packages other than the ones listed in the repos is not a good idea and will probably break your system. Thanks, Yuval. On Fri, Jul 7, 2017 at 1:13 PM, Nathanaël Blanchet wrote: > Hello, > >

Re: [ovirt-users] hosted engine local disk estimate for OVA file

On Sun, Jun 25, 2017 at 1:31 PM, Yaniv Kaul wrote: > > > On Sun, Jun 25, 2017 at 12:38 PM, Ben De Luca wrote: > >> Hi, >> I am in the middle of a disaster recovery situation trying to >> install ovirt 4.1 after a failure of some of our NFS systems. So I

Re: [ovirt-users] unsuccessful hosted engine install

HI Brendan, Can you please send the output for systemctl status vdsmd and journalctl -u vdsmd.service ? Thanks, On Wed, Jun 7, 2017 at 9:32 AM, Sandro Bonazzola wrote: > > > On Tue, Jun 6, 2017 at 2:56 PM, Brendan Hartzell wrote: > >> Upon login to the

Re: [ovirt-users] Upgrade 4.0.6 to 4.1.1 -- How to Update oVirt Node (4.x) Hosts?

rt-release41 from the > URL, and then re-installed ovirt-node-ng-image-update, which installed > ovirt-node-ng-image as a dependency. The install did not report any errors. > It put the 4.1.1 layers back in. I’ve uploaded the latest > /tmp/imgbased.log. > > > > Thanks, > >

Re: [ovirt-users] New oVirt Node install on oVirt Cluster 4.0.5 - How can I install oVirt Node with same 4.0.5 version ???

I take it updating everything to 4.0.6 is not an option ? Thanks, Yuval On May 5, 2017 6:16 PM, "Rogério Ceni Coelho" wrote: > I can think in two ways. Please let me know if have a change to go ok. > > First, download ovirt-node-ng-image-update and

Re: [ovirt-users] Upgrade 4.0.6 to 4.1.1 -- How to Update oVirt Node (4.x) Hosts?

onn_labvmhostt05 Vwi---tz-- > 335.92g pool00 > > > swap onn_labvmhostt05 -wi-ao 4.00g > > > > var onn_labvmhostt05 Vwi-aotz-- 15.00g > pool008.47 > > > > T

Re: [ovirt-users] Upgrade 4.0.6 to 4.1.1 -- How to Update oVirt Node (4.x) Hosts?

e there are no valid bootloader > entries. Please ensure this is fixed before rebooting. > > Layer boot entries ... FAILED - No bootloader entries which point to > imgbased layers > > Valid boot entries ... FAILED - No valid boot entries for imgbased > layers or non-imgbased

Re: [ovirt-users] Upgrade 4.0.6 to 4.1.1 -- How to Update oVirt Node (4.x) Hosts?

ownload that will > install the appropriate repos? > > > > Thanks, > > Daniel > > > > *From: *Yuval Turgeman <yuv...@redhat.com> > *Date: *Tuesday, May 2, 2017 at 2:56 PM > *To: *"Beckman, Daniel" <daniel.beck...@ingramcontent.com> >

Re: [ovirt-users] Upgrade 4.0.6 to 4.1.1 -- How to Update oVirt Node (4.x) Hosts?

Looks like your repos are not set up correctly. oVirt node is an image and the update is a complete image as well, containing a set packages that were tested and known to work well together. This means that when you yum update your system, a single "ovirt-node-ng-image-update" rpm should be

Re: [ovirt-users] Upgrade 4.0.6 to 4.1.1 -- How to Update oVirt Node (4.x) Hosts?

Looks like something went wrong during the update process, can you please attach /tmp/imgbased.log ? Regarding nodectl, I'm not sure, adding Ryan. Basically, it's a python 2.7 module, not sure why it's running in python3. How are you trying to run this ? On Sun, Apr 30, 2017 at 8:44 AM,

Re: [ovirt-users] Upgrade hypervisor to 4.1.1.1

restorecon on virtlogd.conf would be enough On Apr 10, 2017 2:51 PM, "Misak Khachatryan" wrote: > Is it node setup? Today i tried to upgrade my one node cluster, after that > VM's fail to start, it turns out that selinux prevents virtlogd to start. > > ausearch -c 'virtlogd'

Re: [ovirt-users] Error on Node upgrade 2

t; Fernando > > On 15/03/2017 10:06, FERNANDO FREDIANI wrote: > > Find it attached Yuval. > > Fernando > > > On 14/03/2017 18:21, Yuval Turgeman wrote: > > Adding Ryan, Fernando, can you please attach /tmp/imgbased.log ? > > On Mar 13, 2017 2:43 PM, "FERNAN

Re: [ovirt-users] Error on Node upgrade 2

Adding Ryan, Fernando, can you please attach /tmp/imgbased.log ? On Mar 13, 2017 2:43 PM, "FERNANDO FREDIANI" wrote: > Hi Yedidyah. > Running oVirt-Node *4.1.0--0.20170201.0+1* on the nodes and tried a > normal upgrade. It detected it has to upgrade to >

Re: [ovirt-users] Upgrading oVirt-Node-NG from 4.0.3 to 4.0.6

Hi, so 4.0.6 was downloaded but it is not upgrading the node ? On Fri, Feb 3, 2017 at 11:58 PM, Thomas Kendall wrote: > We recently migrated from 3.6 to 4.0, but I'm a little confused about how > to keep the nodes up to date. I see the auto-updates come through for my >