<div dir="ltr">Hi, you can try the following:<div><br></div><div>1. Make sure you have a /etc/iscsi/initiatorname.iscsi file. If you don't, create an empty one (to avoid a migration bug)</div><div><div>2. Install the ovirt-release41 rpm (<a href="http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm">http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm</a>)</div><div>3. yum update ovirt-node-ng-image-update</div><div>4. Make sure only 2 rpms are about to be installed (ovirt-node-ng-image-update and ovirt-node-ng-image) ~530M</div></div><div><br></div><div>Save /tmp/imgbased.log in case something fails so we could take a look :)</div><div><br></div><div>Thanks,</div><div>Yuval</div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 3, 2017 at 6:23 PM, Beckman, Daniel <span dir="ltr"><<a href="mailto:Daniel.Beckman@ingramcontent.com" target="_blank">Daniel.Beckman@ingramcontent.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="m_-7744981279227753059WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">I don’t recall doing anything special with the repositories, apart from (recently) adding the oVirt 4.1 repository. These hosts were originally deployed by downloading the oVirt Node 4.0.3
ISO image. <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">How should the repos be setup? Is there an RPM I can download that will install the appropriate repos?
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Thanks,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri">Daniel<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:Calibri"><u></u> <u></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:Calibri;color:black">From: </span>
</b><span style="font-family:Calibri;color:black">Yuval Turgeman <<a href="mailto:yuvalt@redhat.com" target="_blank">yuvalt@redhat.com</a>><br>
<b>Date: </b>Tuesday, May 2, 2017 at 2:56 PM<br>
<b>To: </b>"Beckman, Daniel" <<a href="mailto:Daniel.Beckman@ingramcontent.com" target="_blank">Daniel.Beckman@ingramcontent.<wbr>com</a>><br>
<b>Cc: </b>"<a href="mailto:users@ovirt.org" target="_blank">users@ovirt.org</a>" <<a href="mailto:users@ovirt.org" target="_blank">users@ovirt.org</a>>, Yedidyah Bar David <<a href="mailto:didi@redhat.com" target="_blank">didi@redhat.com</a>>, "<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a>" <<a href="mailto:sbonazzo@redhat.com" target="_blank">sbonazzo@redhat.com</a>><span class=""><br>
<b>Subject: </b>Re: [ovirt-users] Upgrade 4.0.6 to 4.1.1 -- How to Update oVirt Node (4.x) Hosts?<u></u><u></u></span></span></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">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 installed instead of a list of packages like you mentioned. That's probably what messed things up. How did you configure your repos ?<u></u><u></u></p>
</div><div><div class="h5">
<div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">On May 1, 2017 6:15 PM, "Beckman, Daniel" <<a href="mailto:Daniel.Beckman@ingramcontent.com" target="_blank">Daniel.Beckman@ingramcontent.<wbr>com</a>> wrote:<u></u><u></u></p>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt">Hello,<br>
<br>
I’ve attached the log file for one of the hosts from /var/log/ovirt-engine/host-<wbr>deploy.<br>
<br>
As to the manual update: yes, I ran it after removing the ovirt40 repo and adding ovirt41 repo. Here are the packages it updated:<br>
Updated cockpit-ovirt-dashboard-0.10.<wbr>6-1.4.2.el7.centos.noarch ?<br>
Update 0.10.7-0.0.16.el7.centos.<wbr>noarch @ovirt-4.1<br>
Dep-Install collectd-5.7.0-2.el7.x86_64 @centos-opstools-release<br>
Dep-Install collectd-disk-5.7.0-2.el7.x86_<wbr>64 @centos-opstools-release<br>
Dep-Install collectd-netlink-5.7.0-2.el7.<wbr>x86_64 @centos-opstools-release<br>
Dep-Install collectd-virt-5.7.0-2.el7.x86_<wbr>64 @centos-opstools-release<br>
Dep-Install collectd-write_http-5.7.0-2.<wbr>el7.x86_64 @centos-opstools-release<br>
Dep-Install fluentd-0.12.26-2.el7.noarch @centos-opstools-release<br>
Dep-Install gdeploy-2.0.1-13.noarch @rnachimu-gdeploy<br>
Updated glusterfs-3.7.20-1.el7.x86_<wbr>64 ?<br>
Update 3.8.11-1.el7.x86_64 @ovirt-4.1-centos-gluster38<br>
Updated glusterfs-api-3.7.20-1.el7.<wbr>x86_64 ?<br>
Update 3.8.11-1.el7.x86_64 @ovirt-4.1-centos-gluster38<br>
Updated glusterfs-cli-3.7.20-1.el7.<wbr>x86_64 ?<br>
Update 3.8.11-1.el7.x86_64 @ovirt-4.1-centos-gluster38<br>
Updated glusterfs-client-xlators-3.7.<wbr>20-1.el7.x86_64 ?<br>
Update 3.8.11-1.el7.x86_64 @ovirt-4.1-centos-gluster38<br>
Updated glusterfs-fuse-3.7.20-1.el7.<wbr>x86_64 ?<br>
Update 3.8.11-1.el7.x86_64 @ovirt-4.1-centos-gluster38<br>
Updated glusterfs-geo-replication-3.<wbr>7.20-1.el7.x86_64 ?<br>
Update 3.8.11-1.el7.x86_64 @ovirt-4.1-centos-gluster38<br>
Updated glusterfs-libs-3.7.20-1.el7.<wbr>x86_64 ?<br>
Update 3.8.11-1.el7.x86_64 @ovirt-4.1-centos-gluster38<br>
Updated glusterfs-rdma-3.7.20-1.el7.<wbr>x86_64 ?<br>
Update 3.8.11-1.el7.x86_64 @ovirt-4.1-centos-gluster38<br>
Updated glusterfs-server-3.7.20-1.<wbr>el7.x86_64 ?<br>
Update 3.8.11-1.el7.x86_64 @ovirt-4.1-centos-gluster38<br>
Updated imgbased-0.8.11-0.<wbr>201612061451git1b9e081.el7.<wbr>centos.noarch ?<br>
Update 0.9.23-1.el7.centos.noarch @ovirt-4.1<br>
Updated ioprocess-0.16.1-1.el7.x86_<wbr>64 @?ovirt-centos-ovirt41<br>
Update 0.17.0-1.201611101241.<wbr>gitb7e353c.el7.centos.x86_64 @ovirt-4.1<br>
Dep-Install libtomcrypt-1.17-23.el7.x86_<wbr>64 @ovirt-4.1-epel<br>
Dep-Install libtommath-0.42.0-4.el7.x86_<wbr>64 @ovirt-4.1-epel<br>
Dep-Install libtool-ltdl-2.4.2-22.el7_3.<wbr>x86_64 @updates<br>
Updated mom-0.5.8-1.el7.centos.<wbr>noarch @?ovirt-4.1<br>
Update 0.5.9-1.el7.centos.noarch @ovirt-4.1<br>
Dep-Install net-snmp-1:5.7.2-24.el7_3.2.<wbr>x86_64 @updates<br>
Dep-Install net-snmp-agent-libs-1:5.7.2-<wbr>24.el7_3.2.x86_64 @updates<br>
Updated openvswitch-2.5.0-2.el7.x86_<wbr>64 ?<br>
Update 2.7.0-1.el7.centos.x86_64 @ovirt-4.1<br>
Updated otopi-1.5.2-1.el7.centos.<wbr>noarch ?<br>
Update 1.6.1-1.el7.centos.noarch @ovirt-4.1<br>
Updated ovirt-host-deploy-1.5.3-1.<wbr>el7.centos.noarch ?<br>
Update 1.6.3-1.el7.centos.noarch @ovirt-4.1<br>
Updated ovirt-hosted-engine-ha-2.0.6-<wbr>1.el7.centos.noarch ?<br>
Update 2.1.0.5-1.el7.centos.noarch @ovirt-4.1<br>
Updated ovirt-hosted-engine-setup-2.<wbr>0.4.1-1.el7.centos.noarch ?<br>
Update 2.1.0.5-1.el7.centos.noarch @ovirt-4.1<br>
Updated ovirt-imageio-common-0.4.0-1.<wbr>el7.noarch ?<br>
Update 1.0.0-1.el7.noarch @ovirt-centos-ovirt41<br>
Updated ovirt-imageio-daemon-0.4.0-1.<wbr>el7.noarch ?<br>
Update 1.0.0-1.el7.noarch @ovirt-centos-ovirt41<br>
Updated ovirt-node-ng-nodectl-4.0.6-<wbr>0.20170111.0.el7.noarch ?<br>
Update 4.1.0-0.20170406.0.el7.noarch @ovirt-4.1<br>
Updated ovirt-release-host-node-4.0.<wbr>6.1-1.el7.noarch ?<br>
Update 4.1.1.1-1.el7.centos.noarch @ovirt-4.1<br>
Updated ovirt-release41-4.1.1-1.el7.<wbr>centos.noarch @?ovirt-4.1<br>
Update 4.1.1.1-1.el7.centos.noarch @ovirt-4.1<br>
Updated ovirt-setup-lib-1.0.2-1.el7.<wbr>centos.noarch ?<br>
Update 1.1.0-1.el7.centos.noarch @ovirt-4.1<br>
Dep-Install python-babel-0.9.6-8.el7.<wbr>noarch @base<br>
Dep-Install python-dateutil-1.5-7.el7.<wbr>noarch @base<br>
Dep-Install python-httplib2-0.9.1-2.el7.<wbr>noarch @ovirt-centos-ovirt41<br>
Updated python-ioprocess-0.16.1-1.<wbr>el7.noarch @?ovirt-centos-ovirt41<br>
Update 0.17.0-1.201611101242.<wbr>gitb7e353c.el7.centos.noarch @ovirt-4.1<br>
Dep-Install python-jinja2-2.7.2-2.el7.<wbr>noarch @base<br>
Dep-Install python-keyczar-0.71c-2.el7.<wbr>noarch @ovirt-centos-ovirt41<br>
Dep-Install python-markupsafe-0.11-10.el7.<wbr>x86_64 @base<br>
Dep-Install python-setuptools-0.9.8-4.el7.<wbr>noarch @base<br>
Dep-Install python2-crypto-2.6.1-13.el7.<wbr>x86_64 @ovirt-4.1-epel<br>
Dep-Install python2-ecdsa-0.13-4.el7.<wbr>noarch @ovirt-4.1-epel<br>
Dep-Install python2-paramiko-1.16.1-2.el7.<wbr>noarch @ovirt-4.1-epel<br>
Dep-Install python2-passlib-1.6.5-1.el7.<wbr>noarch @ovirt-centos-ovirt41<br>
Dep-Install python2-pyasn1-0.1.9-7.el7.<wbr>noarch @base<br>
Dep-Install rng-tools-5-8.el7.x86_64 @base<br>
Dep-Install ruby-2.0.0.648-29.el7.x86_64 @base<br>
Dep-Install ruby-irb-2.0.0.648-29.el7.<wbr>noarch @base<br>
Dep-Install ruby-libs-2.0.0.648-29.el7.<wbr>x86_64 @base<br>
Dep-Install rubygem-bigdecimal-1.2.0-29.<wbr>el7.x86_64 @base<br>
Dep-Install rubygem-cool.io-1.2.4-2.el7.<wbr>x86_64 @centos-opstools-release<br>
Dep-Install rubygem-fluent-plugin-rewrite-<wbr>tag-filter-1.5.5-5.el7.noarch @centos-opstools-release<br>
Dep-Install rubygem-fluent-plugin-secure-<wbr>forward-0.4.3-1.el7.noarch @centos-opstools-release<br>
Dep-Install rubygem-http_parser.rb-0.6.0-<wbr>1.el7.x86_64 @centos-opstools-release<br>
Dep-Install rubygem-io-console-0.4.2-29.<wbr>el7.x86_64 @base<br>
Dep-Install rubygem-json-1.7.7-29.el7.x86_<wbr>64 @base<br>
Dep-Install rubygem-msgpack-0.5.11-1.el7.<wbr>x86_64 @centos-opstools-release<br>
Dep-Install rubygem-proxifier-1.0.3-1.el7.<wbr>noarch @centos-opstools-release<br>
Dep-Install rubygem-psych-2.0.0-29.el7.<wbr>x86_64 @base<br>
Dep-Install rubygem-rdoc-4.0.0-29.el7.<wbr>noarch @base<br>
Dep-Install rubygem-resolve-hostname-0.0.<wbr>4-1.el7.noarch @centos-opstools-release<br>
Dep-Install rubygem-sigdump-0.2.2-1.el7.<wbr>noarch @centos-opstools-release<br>
Dep-Install rubygem-string-scrub-0.0.5-1.<wbr>el7.x86_64 @centos-opstools-release<br>
Dep-Install rubygem-thread_safe-0.3.4-1.<wbr>el7.noarch @centos-opstools-release<br>
Dep-Install rubygem-tzinfo-1.2.2-2.el7.<wbr>noarch @centos-opstools-release<br>
Dep-Install rubygem-tzinfo-data-1.2014.10-<wbr>2.el7.noarch @centos-opstools-release<br>
Dep-Install rubygem-yajl-ruby-1.2.1-1.el7.<wbr>x86_64 @centos-opstools-release<br>
Dep-Install rubygems-2.0.14.1-29.el7.<wbr>noarch @base<br>
Dep-Install screen-4.1.0-0.23.<wbr>20120314git3c2946.el7_2.x86_<wbr>64 @base<br>
Dep-Install sshpass-1.05-5.el7.x86_64 @ovirt-centos-ovirt41<br>
Dep-Install tcpdump-14:4.5.1-3.el7.x86_64 @base<br>
Updated vdsm-4.18.21-1.el7.centos.<wbr>x86_64 ?<br>
Update 4.19.10.1-1.el7.centos.x86_<wbr>64 @ovirt-4.1<br>
Updated vdsm-api-4.18.21-1.el7.<wbr>centos.noarch ?<br>
Update 4.19.10.1-1.el7.centos.<wbr>noarch @ovirt-4.1<br>
Updated vdsm-cli-4.18.21-1.el7.<wbr>centos.noarch ?<br>
Update 4.19.10.1-1.el7.centos.<wbr>noarch @ovirt-4.1<br>
Dep-Install vdsm-client-4.19.10.1-1.el7.<wbr>centos.noarch @ovirt-4.1<br>
Updated vdsm-gluster-4.18.21-1.el7.<wbr>centos.noarch ?<br>
Update 4.19.10.1-1.el7.centos.<wbr>noarch @ovirt-4.1<br>
Updated vdsm-hook-ethtool-options-4.<wbr>18.21-1.el7.centos.noarch ?<br>
Update 4.19.10.1-1.el7.centos.noarch @ovirt-4.1<br>
Updated vdsm-hook-fcoe-4.18.21-1.el7.<wbr>centos.noarch ?<br>
Update 4.19.10.1-1.el7.centos.<wbr>noarch @ovirt-4.1<br>
Updated vdsm-hook-macspoof-4.18.21-1.<wbr>el7.centos.noarch ?<br>
Update 4.19.10.1-1.el7.centos.<wbr>noarch @ovirt-4.1<br>
Updated vdsm-hook-nestedvt-4.18.21-1.<wbr>el7.centos.noarch ?<br>
Update 4.19.10.1-1.el7.centos.<wbr>noarch @ovirt-4.1<br>
Updated vdsm-hook-openstacknet-4.18.<wbr>21-1.el7.centos.noarch ?<br>
Update 4.19.10.1-1.el7.centos.<wbr>noarch @ovirt-4.1<br>
Dep-Install vdsm-hook-vhostmd-4.19.10.1-1.<wbr>el7.centos.noarch @ovirt-4.1<br>
Updated vdsm-hook-vmfex-dev-4.18.21-<wbr>1.el7.centos.noarch ?<br>
Update 4.19.10.1-1.el7.centos.noarch @ovirt-4.1<br>
Updated vdsm-jsonrpc-4.18.21-1.el7.<wbr>centos.noarch ?<br>
Update 4.19.10.1-1.el7.centos.<wbr>noarch @ovirt-4.1<br>
Updated vdsm-python-4.18.21-1.el7.<wbr>centos.noarch ?<br>
Update 4.19.10.1-1.el7.centos.noarch @ovirt-4.1<br>
Updated vdsm-xmlrpc-4.18.21-1.el7.<wbr>centos.noarch ?<br>
Update 4.19.10.1-1.el7.centos.noarch @ovirt-4.1<br>
Updated vdsm-yajsonrpc-4.18.21-1.el7.<wbr>centos.noarch ?<br>
Update 4.19.10.1-1.el7.centos.<wbr>noarch @ovirt-4.1<br>
Dep-Install vhostmd-0.5-11.el7.x86_64 @ovirt-centos-ovirt41<br>
<br>
Thanks,<br>
Daniel<br>
<br>
On 4/30/17, 12:44 AM, "Yedidyah Bar David" <<a href="mailto:didi@redhat.com" target="_blank">didi@redhat.com</a>> wrote:<br>
<br>
On Thu, Apr 27, 2017 at 6:48 PM, Beckman, Daniel<br>
<<a href="mailto:Daniel.Beckman@ingramcontent.com" target="_blank">Daniel.Beckman@ingramcontent.<wbr>com</a>> wrote:<br>
> Didi,<br>
><br>
> Thanks for the tip on the utilities – I’ll add that for future upgrades. Since you pointed that out, I’m reminded that in a previous upgrade (following one of the developer’s suggestions) I had added this:<br>
> /etc/ovirt-engine/engine.conf.<wbr>d/99-custom-truststore.conf<br>
> So I guess that’s why my https certificate was preserved.<br>
<br>
Good.<br>
<br>
><br>
> As to the documentation, I did submit a pull request (#923) and ‘JohnMarksRH’ added that along with some additional edits. I’ll move any continuing discussion on that to another thread. And yes, the RHV documentation is excellent and I’ve often turned
to it. It’s too bad some of the effort ends up being duplicated. Anyway….<br>
><br>
> Here’s what I did with one of the oVirt nodes:<br>
> yum -y remove ovirt-release40<br>
> yum -y install <a href="http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm" target="_blank">
http://resources.ovirt.org/<wbr>pub/yum-repo/ovirt-release41.<wbr>rpm</a><br>
> cd /etc/yum.repos.d<br>
> # ls<br>
> CentOS-Base.repo CentOS-fasttrack.repo CentOS-Sources.repo cockpit-preview-epel-7.repo<br>
> CentOS-CR.repo CentOS-fasttrack.repo.rpmnew CentOS-Vault.repo ovirt-4.0-dependencies.repo<br>
> CentOS-Debuginfo.repo CentOS-Media.repo CentOS-Vault.repo.rpmnew ovirt-4.0.repo<br>
> rm -f ovirt-4.0*<br>
><br>
> After doing that, when I check again in the admin GUI for an upgrade, it shows one available (4.1.1.1). From the GUI I tell it to upgrade, and it runs along with no errors, seems to finish, and then reboots the host.<br>
><br>
> When the host comes back up, it’s still running 4.0.6. When I check again for an available upgrade, it doesn’t see it available. I’m attaching the installation log that is referenced in Events in the GUI.<br>
><br>
> If I go straight into the node and run ‘yum update’ and reboot, then it gets the latest 4.1.x image and the engine detects it as such.<br>
<br>
You mean you do that after the above (removing 4.0 repos, adding 4.1)?<br>
<br>
What packages did it update?<br>
<br>
Please check also time-wise nearby log files for this host in<br>
/var/log/ovirt-engine/host-<wbr>deploy and share them.<br>
'ovirt-host-mgmt*' is the result of checking for updates from the admin web ui.<br>
<br>
> But of course that’s not the ideal method. I used the manual method for the remaining hosts.<br>
><br>
> I don’t know if this is related, but since the upgrade I’ve also noticed an unfamiliar error when I log in directly to the engine host. (It’s a standalone Centos7 VM running on a separate KVM host.) Here is is:<br>
><br>
> nodectl must be run as root!<br>
> nodectl must be run as root!<br>
> This comes up when *any* user logs into the box. When I switch to root I get this:<br>
> /bin/python3: Error while finding spec for 'nodectl.__main__' (<class 'ImportError'>: No module named 'nodectl')<br>
> /bin/python3: Error while finding spec for 'nodectl.__main__' (<class 'ImportError'>: No module named 'nodectl')<br>
> So it looks like it’s been invoked from here:<br>
> ls -llh /etc/profile.d/nodectl*<br>
> -rwxr-xr-x. 1 root root 13 Apr 6 06:46 /etc/profile.d/nodectl-motd.sh<br>
> -rwxr-xr-x. 1 root root 24 Apr 6 06:46 /etc/profile.d/nodectl-run-<wbr>banner.sh<br>
> According to ‘yum whatprovides’ this appears to have been installed by package “ovirt-node-ng-nodectl-4.1.0-<wbr>0.20170406.0.el7.noarch”.<br>
><br>
> Anyone else getting this? I can try fixing the python error by adding the module, but I thought I’d report this first. Any suggestions as to next steps?<br>
<br>
Adding Yuval for the node-specific issues.<br>
<br>
Best,<br>
<br>
><br>
> Thanks<br>
> Daniel<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> On 4/25/17, 2:01 AM, "Yedidyah Bar David" <<a href="mailto:didi@redhat.com" target="_blank">didi@redhat.com</a>> wrote:<br>
><br>
> On Tue, Apr 25, 2017 at 1:19 AM, Beckman, Daniel<br>
> <<a href="mailto:Daniel.Beckman@ingramcontent.com" target="_blank">Daniel.Beckman@<wbr>ingramcontent.com</a>> wrote:<br>
> > So I successfully upgraded my engine from 4.06 to 4.1.1 with no major<br>
> > issues.<br>
> ><br>
> ><br>
> ><br>
> > A nice thing I noticed was that my custom CA certificate for https on the<br>
> > admin and user portals wasn’t clobbered by setup.<br>
> ><br>
> ><br>
> ><br>
> > I did have to restore my custom settings for ISO uploader, log collector,<br>
> > and websocket proxy:<br>
> ><br>
> > cp<br>
> > /etc/ovirt-engine/isouploader.<wbr>conf.d/10-engine-setup.conf.<<wbr>latest_timestamp><br>
> > /etc/ovirt-engine/isouploader.<wbr>conf.d/10-engine-setup.conf<br>
> ><br>
> > cp<br>
> > /etc/ovirt-engine/ovirt-<wbr>websocket-proxy.conf.d/10-<wbr>setup.conf.<latest_timestamp><br>
> > /etc/ovirt-engine/ovirt-<wbr>websocket-proxy.conf.d/10-<wbr>setup.conf<br>
> ><br>
> > cp<br>
> > /etc/ovirt-engine/<wbr>logcollector.conf.d/10-engine-<wbr>setup.conf.<latest_timestamp><br>
> > /etc/ovirt-engine/<wbr>logcollector.conf.d/10-engine-<wbr>setup.conf<br>
><br>
> The utilities read these files sorted by name, last wins. So you<br>
> can add '99-my.conf' to each and have it override whatever engine-setup does.<br>
><br>
> ><br>
> ><br>
> ><br>
> > Now I’m moving on to updating the oVirt node hosts, which are currently at<br>
> > oVirt Node 4.0.6.1. (I’m assuming I should do that before attempting to<br>
> > upgrade the cluster and data center compatibility level to 4.1.)<br>
> ><br>
> ><br>
> ><br>
> > When I right-click on a host and go to Installation / Check for Upgrade, the<br>
> > results are ‘no updates found.’ When I log into that host directly, I notice<br>
> > it’s still got the oVirt 4.0 repo, not 4.1. Is there an extra step I’m<br>
> > missing? The documentation I’ve found<br>
> > (<a href="http://www.ovirt.org/documentation/upgrade-guide/chap-Updates_between_Minor_Releases/" target="_blank">http://www.ovirt.org/<wbr>documentation/upgrade-guide/<wbr>chap-Updates_between_Minor_<wbr>Releases/</a>)<br>
> > doesn’t mention this.<br>
><br>
> You are right. It's mentioned for the engine in the release notes [1]<br>
> but not for the hosts. Please file a github issue or send a pull request :-)<br>
><br>
> [1] <a href="https://www.ovirt.org/release/4.1.0/" target="_blank">https://www.ovirt.org/release/<wbr>4.1.0/</a><br>
><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > **<br>
> ><br>
> > If I can offer some unsolicited feedback: I feel like this list is populated<br>
> > with a lot of questions that could be averted with a little care and feeding<br>
> > of the documentation. It’s unfortunate because that makes for a rocky<br>
> > introduction to oVirt, and it makes it look like a neglected project, which<br>
> > I know is not the case.<br>
><br>
> Patches are welcome :-)<br>
><br>
> ><br>
> ><br>
> ><br>
> > On a related note, I know this has been discussed before but…<br>
> ><br>
> > The centralized control in Github for the documentation does not really<br>
> > encourage user contributions. What’s wrong with a wiki? If we’re really<br>
> > concerned about bad or malicious edits being posted, keep the official in<br>
> > git and add a separate wiki that is clearly marked as user-contributed.<br>
><br>
> That was indeed discussed in the past, I am not aware of any conclusions.<br>
> Perhaps start a separate thread about this? Adding Duck.<br>
><br>
> Please also note that you can have a look at RHV documentation [2].<br>
> Almost all of it applies to oVirt as well (and oVirt's to RHV).<br>
><br>
> [2] <a href="https://access.redhat.com/documentation/en/red-hat-virtualization/" target="_blank">
https://access.redhat.com/<wbr>documentation/en/red-hat-<wbr>virtualization/</a><br>
><br>
> Best,<br>
><br>
> ><br>
> > **<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > Thanks,<br>
> ><br>
> > Daniel<br>
> ><br>
> ><br>
> > ______________________________<wbr>_________________<br>
> > Users mailing list<br>
> > <a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
> > <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">
http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
> ><br>
><br>
><br>
><br>
> --<br>
> Didi<br>
><br>
><br>
><br>
><br>
><br>
><br>
<br>
<br>
<br>
--<br>
Didi<br>
<br>
<br>
<u></u><u></u></p>
</blockquote>
</div>
</div>
</div></div></div>
</div>
</blockquote></div><br></div>