[ovirt-users] Re: oVirt 4.3 -> 4.4 Upgrade Path Questions

[shadow emy]

Just a head up 4.4.1 was released today, which fix a big number of  upgrade bugs
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/NDGETPMEYF6JBZH35BXOH2YRS36JOCQX/

[ovirt-users] [ANN] oVirt 4.4.1 is now generally available

[Lev Veyde]

oVirt 4.4.1 is now generally available

The oVirt project is excited to announce the general availability of oVirt
4.4.1 , as of July 8th, 2020.

This release unleashes an altogether more powerful and flexible open source
virtualization solution that encompasses hundreds of individual changes and
a wide range of enhancements across the engine, storage, network, user
interface, and analytics, as compared to oVirt 4.3.
Important notes before you install / upgrade

Please note that oVirt 4.4 only supports clusters and data centers with
compatibility version 4.2 and above. If clusters or data centers are
running with an older compatibility version, you need to upgrade them to at
least 4.2 (4.3 is recommended).

Please note that in RHEL 8 / CentOS 8 several devices that worked on EL7
are no longer supported.

For example, the megaraid_sas driver is removed. If you use Enterprise
Linux 8 hosts you can try to provide the necessary drivers for the
deprecated hardware using the DUD method (See the users’ mailing list
thread on this at
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NDSVUZSESOXEFJNPHOXUH4HOOWRIRSB4/
)
Documentation

   -

   If you want to try oVirt as quickly as possible, follow the instructions
   on the Download  page.
   -

   For complete installation, administration, and usage instructions, see
   the oVirt Documentation .
   -

   For upgrading from a previous version, see the oVirt Upgrade Guide
   .
   -

   For a general overview of oVirt, see About oVirt
   .

What’s new in oVirt 4.4.1 Release?

This update is the first in a series of stabilization updates to the 4.4
series.

This release introduces a new monitoring solution that provides a user
interface to oVirt DWH collected data using Grafana. This allows admins to
track inventory, monitor performance and capacity trends, and easily
identify and troubleshoot resources issues. Grafana is installed and
configured during engine-setup and includes pre-built dashboards that are
based on the data collected by the ovirt_engine_history PostgreSQL Data
Warehouse database (BZ#1777877
).

In oVirt 4.4.1 the maximum memory size for 64-bit x86_64 and ppc64/ppc64le
VMs is now 6TB. For x86_64 this limit is applied also to VMs in 4.2 and 4.3
Cluster Levels.

You can now use CentOS Stream as an alternative to CentOS Linux on
non-production systems.

This release is available now on x86_64 architecture for:

   -

   Red Hat Enterprise Linux 8.2
   -

   CentOS Linux (or similar) 8.2
   -

   CentOS Stream (tech preview)


This release supports Hypervisor Hosts on x86_64 and ppc64le architectures
for:

   -

   Red Hat Enterprise Linux 8.2
   -

   CentOS Linux (or similar) 8.2
   -

   CentOS Stream (tech preview)
   -

   oVirt Node 4.4 based on CentOS Linux 8.2 (available for x86_64 only)


oVirt Node and Appliance have been updated, including:

   -

   oVirt 4.4.1: http://www.ovirt.org/release/4.4.1/
   -

   CentOS Linux 8.2.2004:
   https://lists.centos.org/pipermail/centos-announce/2020-June/035756.html
   -

   CentOS Virt SIG updates including Advanced Virtualization 8.2 (qemu-kvm
   4.2 , libvirt 6.0.0
   )
   -

   Wildfly 19.1.0:
   https://wildfly.org/news/2020/05/04/WildFly-1910-Released/
   -

   Ansible 2.9.10:
   
https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst#v2-9-10
   -

   Glusterfs 7.6: https://docs.gluster.org/en/latest/release-notes/7.6/



See the release notes [1] for installation instructions and a list of new
features and bugs fixed.

Notes:

   -

   oVirt Appliance is already available for CentOS Linux 8
   -

   oVirt Node NG is already available for CentOS Linux 8


Additional resources:

   -

   Read more about the oVirt 4.4.1 release highlights:
   http://www.ovirt.org/release/4.4.1/
   -

   Get more oVirt project updates on Twitter: https://twitter.com/ovirt
   -

   Check out the latest project news on the oVirt blog:
   http://www.ovirt.org/blog/


[1] http://www.ovirt.org/release/4.4.1/

[2] http://resources.ovirt.org/pub/ovirt-4.4/iso/

-- 

Lev Veyde

Senior Software Engineer, RHCE | RHCVA | MCITP

Red Hat Israel



l...@redhat.com | lve...@redhat.com

TRIED. TESTED. TRUSTED. 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/FB3WEFVK2XFK7WAWAN75DQBD4BXERU7O/

[ovirt-users] Re: Lots of problems with deploying the hosted-engine (ovirt 4.4 | CentOS 8.2.2004)

[Asaf Rachmani]

Hi Jonas,

Can you please share the full log file located in
/var/log/ovirt-hosted-engine-setup ?
My guess you hit [1], this is the fix for that [2] (not merged yet).
You can install the rpm with the fix from Jenkins CI [3] and then run the
following command:
hosted-engine --deploy --ansible-extra-vars=he_offline_deployment=true

Regarding the "disk-memory-leak", can you please open a bug for that?

Regards,
Asaf

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1849517
[2] https://gerrit.ovirt.org/109730
[3]
https://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_standard-check-patch/184/


On Tue, Jul 7, 2020 at 4:24 PM jonas  wrote:

> Hi!
>
> A short addendum:
> I have now also tried to perform the installation using the oVirt Node
> distribution as a basis, but that also ended with the same problem. So
> it does not seam to be an issue with the underlying CentOS installation,
> but rather with my general setup or parameters.
>
> Regards
> Jonas
>
> On 2020-06-28 16:26, jonas wrote:
> > Hi!
> >
> > I have banged my head against deploying the ovirt 4.4 self-hosted
> > engine on Centos 8.2 for last couple of days.
> >
> > First I was astonished that resources.ovirt.org has no IPv6
> > connectivity, which made my initial plan for a mostly IPv6-only
> > deployment impossible.
> >
> > CentOS was installed from scratch using the ks.cgf Kickstart file
> > below, which also adds the ovirt 4.4 repo and installs
> > cockpit-ovirt-dashboard & ovirt-engine-appliance.
> >
> > When deploying the hosted-engine from cockpit while logged in as a
> > non-root (although privileged) user, the "(3) Prepare VM" step
> > instantly fails with a nondescript error message and without
> > generating any logs. By using the browser dev tools it was determined
> > that this was because the ansible vars file could not be created as
> > the non-root user did not have write permissions in
> > '/var/lib/ovirt-hosted-engine-setup/cockpit/' . Shouldn't cockpit be
> > capable of using sudo when appropriate, or at least give a more
> > descriptive error message?
> >
> > After login into cockpit as root, or when using the command line
> > ovirt-hosted-engine-setup tool, the deployment fails with "Failed to
> > download metadata for repo 'AppStream'".
> > This seems to be because a) the dnsmasq running on the host does not
> > forward dns queries, even though the host itself can resolve dns
> > queries just fine, and b) there also does not seem to be any
> > functioning routing setup to reach anything outside the host.
> > Regarding a) it is strange that dnsmasq is running with a config file
> > '/var/lib/libvirt/dnsmasq/default.conf' containing the 'no-resolv'
> > option. Could the operation of systemd-resolved be interfering with
> > dnsmasq (see ss -tulpen output)? I tried to manually stop
> > systemd-resolved, but got the same behaviour as before.
> >
> > I hope someone could give me a hint how I could get past this problem,
> > as so far my ovirt experience has been a little bit sub-par. :D
> >
> > Also when running ovirt-hosted-engine-cleanup, the extracted engine
> > VMs in /var/tmp/localvm* are not removed, leading to a
> > "disk-memory-leak" with subsequent runs.
> >
> > Best regards
> > Jonas
> >
> > --- ss -tulpen output post deploy-run ---
> > [root@nxtvirt ~]# ss -tulpen  | grep ':53 '
> > udp   UNCONN 0  0 127.0.0.53%lo:53
> > 0.0.0.0:* users:(("systemd-resolve",pid=1379,fd=18)) uid:193
> > ino:32910 sk:6 <->
> > udp   UNCONN 0  0   [fd00:1234:5678:900::1]:53
> > [::]:* users:(("dnsmasq",pid=13525,fd=15)) uid:979 ino:113580
> > sk:d v6only:1 <->
> > udp   UNCONN 0  0  [fe80::5054:ff:fe94:f314]%virbr0:53
> > [::]:* users:(("dnsmasq",pid=13525,fd=12)) uid:979 ino:113575
> > sk:e v6only:1 <->
> > tcp   LISTEN 0  32  [fd00:1234:5678:900::1]:53
> > [::]:* users:(("dnsmasq",pid=13525,fd=16)) uid:979 ino:113581
> > sk:20 v6only:1 <->
> > tcp   LISTEN 0  32 [fe80::5054:ff:fe94:f314]%virbr0:53
> > [::]:* users:(("dnsmasq",pid=13525,fd=13)) uid:979 ino:113576
> > sk:21 v6only:1 <->
> >
> >
> > --- running dnsmasq processes on host ('nxtvirt') post deploy-run ---
> >
> > dnsmasq13525  0.0  0.0  71888  2344 ?S12:31   0:00
> > /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf
> > --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
> > root   13526  0.0  0.0  71860   436 ?S12:31   0:00
> > /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf
> > --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper
> >
> >
> > --- var/lib/libvirt/dnsmasq/default.conf ---
> >
> > ##WARNING:  THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO
> > BE
> > ##OVERWRITTEN AND LOST.  Changes to this configuration should be made
> > using:
> > ##virsh net-edit default
> > ## or other application using the libvirt API.
> > ##
> > ## dnsmasq conf file created 

[ovirt-users] Re: rhv 4.3.9 - snapshots fail

[Pavel Bar]

Good day Markus,
Unfortunately there is no easy workaround. The only option is to fix the
database and image metadata *manually*.
The bug is on our list, but the fix is not straightforward either, so it
might take a few months until it's fixed.

Sincerely,

Pavel


On Tue, Jul 7, 2020 at 4:20 PM Markus Schaufler <
markus.schauf...@digit-all.at> wrote:

> Hi,
>
> I think we ran into this bug
> https://bugzilla.redhat.com/show_bug.cgi?id=1802277 and
> https://access.redhat.com/solutions/5174961 as we have exactly that
> problems and log-entries.
>
> As there are now several VMs that cannot create (or delete) snapshots
> accordingly we cannot do backups on that VMs.
> Are there any suggestions or workarounds in order that we can still backup
> them up?
>
> Thanks very much,
> Markus
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/5JLR4FOTLMZ2FHXJMT7EIHKFJWJ3MMIZ/
>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JSBVN2JUC2KVSA43HKW7I4RKUU2L2JOJ/

[ovirt-users] Re: oVirt 4.3 -> 4.4 Upgrade Path Questions

[Gobinda Das]

Hi,
 Before upgrade make sure your setup upgraded to latest
ovirt-4.3.Recommending to keep the workloads on the Virtual Machines as
minimal as possible. If you have highly write intensive workloads, then it
will take much longer time sync back data which will lead to the longer
upgrade window.
You should have an additional disk(all hosts) for the new voirt 4.4 hosted
engine deployment.

On Tue, Jul 7, 2020 at 6:56 PM Andrei Verovski  wrote:

> Hi !
>
> I have 2-node oVirt 4.3 installation, with engine running as KVM guest on
> SuSE file server (not hosted engine).
> Nodes are manually installed on CentOS 7.x (further referred as old node
> #1 and #2).
>
> I’m going to add 1 additional node, and migrate system to CentOS 8.2 /
> oVirt 4.4.
>
> Is this correct roadmap, or something can be done in a better way? Here is
> my plan.
>
> 1) Upgrade oVirt Hosted Engine running under KVM / SuSE file server to
> CentOS 8.2 / oVirt 4.4.
> Or its better to install from scratch new CentOS 8.2/oVirt 4.4 and migrate
> database?
>
> 2) Install CentOS 8.2 and oVirt node 4.4 on new server (let’s name it node
> #3).
> 3) Migrate virtual machines from old node #1 to the new (#3).
> 4) Upgrade CentOS on old node #1 to v8.2, and oVirt from web interface.
> Will that work, or upgrade CentOS 7 -> 8 will render this process
> unmanageable due to removal of many components?
> 5) Migrate back virtual machines from node #3 to newly upgraded node #1.
> 6) Repeat step 4 and 5 for old node #2.
>
>
> I have set of custom shell and python scripts running on engine and nodes,
> so manual installation was a way to go.
>
> Thanks in advance for any suggestion(s)
>
> with best regards
> Andrei
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/B6TKPHULJE37CF2O44FJJVJ3KOXR5IZI/
>


-- 


Thanks,
Gobinda
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/W6LPORAWQZBXO6YVUYU5HPX5KQCFKR3Q/