- Users - oVirt List Archives

Cannnot change display resolution using spice
by Станислав Ефремов 10 Jun '17

10 Jun '17

This is a multipart message in MIME format. ------=_NextPart_000_01A1_01D2E0FD.73774630 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable I`m using CentOS Linux release 7.3.1611 and oVirt 4.1.2 =20 I`m testing oVirt to use it like vdi solution. I cannot change = resolution everywhere, except Fedora 25 with Gnome3 and GDM.=20 In others distro display resolution setting 1024x768 and might be set to = 800x600. Xrandr shows all available modes but when I set resolution its failed = and I cannot interact with desktop except ctrl-alt-f1.=20 Can it related to vgamem? =20 ------=_NextPart_000_01A1_01D2E0FD.73774630 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" = xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta = http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta = name=3DGenerator content=3D"Microsoft Word 15 (filtered = medium)"><style></style></head><body lang=3DRU = link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1>I`m using CentOS Linux release = 7.3.1611 and oVirt 4.1.2<o:p></o:p><o:p> </o:p>I`m testing oVirt to use it like vdi solution. I cannot = change resolution everywhere, except Fedora 25 with Gnome3 and GDM. = <o:p></o:p>In others = distro display resolution setting 1024x768 and might be set to = 800x600.<o:p></o:p>Xrandr shows all available modes but when I set resolution = its failed and I cannot interact with desktop except ctrl-alt-f1. = <o:p></o:p>Can it = related to vgamem?<o:p></o:p><o:p> </o:p></div></body></html> ------=_NextPart_000_01A1_01D2E0FD.73774630--

2 2

nfs.home.lan already exits with uuid
by Greg Fitzgerald 10 Jun '17

10 Jun '17

Hi, I just replaced my local proxmox server with ovirt for some testing. When I woke up this morning one of my VM's nfs.home.lan was offline. So I tried to power it back on and I received following event message. VM nfs.home.lan is down with error. Exit message: operation failed: domain 'nfs.home.lan' already exists with uuid b6453519-4124-4a47-9fb8-064be743067d. I tried to reboot the physical machine, I also tried destroying the VM (keeping the disk drives) and recreating it and attaching the drive again. Always end up with the same error message. Best Regards, Greg Fitzgerald

1 0

Hosted-Engine --Deploy option in Web
by Langley, Robert 10 Jun '17

10 Jun '17

--_000_MWHPR09MB1421B9141F477FFABB427B6587CE0MWHPR09MB1421namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable There is no Hosted Engine option within the Edit window of my additional ho= st. How do I deploy Hosted-Engine to an existing host, if I've forgotten to= do so when adding it as a new host? And, this host is one of the three sto= rage servers hosting the engine gluster volume. Thanks, Robert Langley --_000_MWHPR09MB1421B9141F477FFABB427B6587CE0MWHPR09MB1421namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Exchange Server">  <style></style> </head> <body> <div>There is no Hosted Engine option within the Edit window of my addition= al host. How do I deploy Hosted-Engine to an existing host, if I’ve f= orgotten to do so when adding it as a new host? And, this host is one of th= e three storage servers hosting the engine gluster volume.</div> <div> </div> <div>Thanks,</div> <div>Robert Langley</div> <div> </div> </body> </html> --_000_MWHPR09MB1421B9141F477FFABB427B6587CE0MWHPR09MB1421namp_--

2 1

Building oVirt engine on Debian
by Leni Kadali Mutungi 09 Jun '17

09 Jun '17

Ran `make clean install-dev` and the process freezes at: [INFO] weaveinfo Join point 'constructor-execution(void com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer.<init>(com.google.gwt.dev.jjs.ast.JProgram))' in Type 'com.google.gwt.dev.jjs.impl.ControlFlowAnalyzer' (ControlFlowAnalyzer.java:905) advised by after advice from 'org.ovirt.engine.ui.gwtaop.DontPrune' (DontPrune.java) My computer freezes at that point and I have to power it off. I tried doing it in the terminal without the Desktop Environment and I get the same result. The component being built is the UI Common Web. Advice on what to do next is appreciated. -- - Warm regards Leni Kadali Mutungi

2 18

Re: [ovirt-users] unsuccessful hosted engine install
by Sandro Bonazzola 09 Jun '17

09 Jun '17

On Wed, May 31, 2017 at 4:45 AM, Brendan Hartzell <mrrex4(a)gmail.com> wrote: > Can you please elaborate about the failure you see here and how are you > trying to manually partition the host? > > Sure, I will start from the beginning. > - Using: ovirt-node-ng-installer-ovirt-4.1-2017052604 <(201)%20705-2604> > .iso > - During installation I setup one of the two interfaces and check the box > to automatically use the connection. > - I'm currently providing a host name of node-1.test.net until I have a > successful process. > - I configure date and time for my timezone and to use an internal NTP > server. > - On Installation Destination, I pick my 128GB USB3.0 SanDisk flash drive, > check the box that I would like to make additional space, and click done. > In the reclaim disk space window, I click delete all, and then reclaim > space. I go back into the Installation Destination, select that I will > configure partitioning, and click done. The Manual Partitioning window > opens, I use the option to automatically create mount points. > In this screen, please change partitioning scheme from LVM to LVM Thin Provisioning: it should solve your following error. > At this point, /boot is 1024MB, /var is 15GB, / is 88.11 GB, and swap is > 11.57GB. I then change / to 23.11 GB, update settings, change /var to > 80GB, update settings again, and click done. I accept the changes and > begin installation. > > I tried these changes based on this article: http://www.ovirt.org/ > documentation/self-hosted/chap-Deploying_Self-Hosted_Engine/ > > The article does say that you can specify a different directory than > /var/tmp, but I don't recall seeing that option. > If the setup detects not enough space in /var/tmp for extracting the appliance it will ask about a different directory. > > After some time, I get the following error: > There was an error running the kickstart script at line 7. This is a > fatal error and installation will be aborted. The details of this error > are: > > [INFO] Trying to create a manageable base from '/' > [ERROR] LVM Thin Provisioning partitioning scheme is required. For > autoinstall via Kickstart with LVM Thin Provisioning check options > --thinpool and --grow. Please consult documentation for details. > ^^ this one should be solved by the LVM Thin Provisioning scheme mentioned above.. > > Traceback (most recent call last): > File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main > "__main__", fname, loader, pkg_name) > File "/usr/lib64/python2.7runpy.py", line 72, in _run_code exec code in > run_globals > File "/usr/lib/python2.7/site-packages/imgbased/__main__.py", line 51, in > <module> CliApplication() > File "/usr/lib/python2.7/site-packages/imgbased/__init__.py", line 82, in > CliApplication() > File "/usr/lib/python2.7/site-packages/imgbased/hooks.py", line 120, in > emit cb(self.context, *args) > File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", line > 169, in post_argparse layout.initialize(args.source, args.init_nvr) > File "/usr/lib/python2.7/site-packages/imgbased/plugins/core.py", line > 216, in initialize self.app.imgbase.init_layout_from(source, init_nvr) > File "/usr/lib/python2.7/site-packages/imgbased/imgbase.py", line 271, in > init_layout_from self.init_tags_on(existing_lv) > File "/usr/lib/python2.7/site-packages/imgbased/imgbase.py", line 243, in > init_tags_on pool = lv.thinpool() > File "/usr/lib/python2.7/site-packages/imgbased/lvm.py", line 250, in > thinpool raise MissingLvmThinPool() imgbased.lvm.MissingLvmThinPool > > At this point, the only option is to exit the installer. > > **************************** > > Being this a new install, please use 4.1. oVirt 4.0 is not supported > anymore. > > Not a problem. > > **************************** > > Can you please provide hosted engine setup logs or better a full sos > report? (sosreport -a) > > Again, the process I'm following: > - Using: ovirt-node-ng-installer-ovirt-4.1-2017052604 <(201)%20705-2604> > .iso > - During installation I setup one of the two interfaces and check the box > to automatically use the connection. > - I'm currently providing a host name of node-1.test.net until I have a > successful process. > - I configure date and time for my timezone and to use an internal NTP > server. > - On Installation Destination, I pick my 128GB USB3.0 SanDisk flash drive, > check the box that I would like to make additional space, and click done. > In the reclaim disk space window, I click delete all, and then reclaim > space. > - Begin Installation and set a root password. > - Perform a yum update - no packages marked for update (as expected) > - Use vi to update /etc/hosts with a reference for node-1.test.net and > engine.test.net > - First attempt at hosted-engine from web-UI > - Setup downloads and installs ovirt-engine-appliance-4.1-20170523.1.el7. > centos.noarch.rpm > *Failed to execute stage 'Environment setup': Failed to reconfigure > libvirt for VDSM > *Hosted Engine deployment failed > - Attached SOS report > The checksum is: aa56097edc0b63c49caaf1a1fde021bc > > At this point, I would run ovirt-hosted-engine-cleanup and I would get > further along in the install process. However, because this is a fresh > install, I'm going to leave things here for now so you can review the SOS. > Thanks for the SOS report! Hosted Engine setup fails on: 2017-05-30 19:24:39 DEBUG otopi.plugins.gr_he_setup.system.vdsmenv plugin.execute:921 execute-output: ('/bin/vdsm-tool', 'configure', '--force') stdout: Checking configuration status... Current revision of multipath.conf detected, preserving lvm is configured for vdsm libvirt is already configured for vdsm SUCCESS: ssl configured to true. No conflicts Running configure... Reconfiguration of libvirt is done. 2017-05-30 19:24:39 DEBUG otopi.plugins.gr_he_setup.system.vdsmenv plugin.execute:926 execute-output: ('/bin/vdsm-tool', 'configure', '--force') stderr: Error: ServiceOperationError: _systemctlStart failed Job for libvirtd.service failed because the control process exited with error code. See "systemctl status libvirtd.service" and "journalctl -xe" for details. At the same time journalctl shows: May 30 19:24:39 node-1.test.net libvirtd[20954]: libvirt version: 2.0.0, package: 10.el7_3.5 (CentOS BuildSystem <http://bugs.centos.org>, 2017-03-03-02:09:45, c1bm.rdu2.centos.org) May 30 19:24:39 node-1.test.net libvirtd[20954]: hostname: node-1.test.net May 30 19:24:39 node-1.test.net libvirtd[20954]: The server certificate /etc/pki/vdsm/certs/vdsmcert.pem is not yet active May 30 19:24:39 node-1.test.net systemd[1]: libvirtd.service: main process exited, code=exited, status=6/NOTCONFIGURED May 30 19:24:39 node-1.test.net systemd[1]: Failed to start Virtualization daemon. May 30 19:24:39 node-1.test.net systemd[1]: Unit libvirtd.service entered failed state. May 30 19:24:39 node-1.test.net systemd[1]: libvirtd.service failed. May 30 19:24:39 node-1.test.net systemd[1]: libvirtd.service holdoff time over, scheduling restart. > > **************************** > > I'd like to understand the issues you faced before suggesting to restart > from scratch. > > Too late... I did two re-installs to get a more accurate account of my > install process for above. > > **************************** > > Thank you for your help! > > Brendan > > On Tue, May 30, 2017 at 12:17 AM, Sandro Bonazzola <sbonazzo(a)redhat.com> > wrote: > >> >> >> On Tue, May 30, 2017 at 6:49 AM, Brendan Hartzell <mrrex4(a)gmail.com> >> wrote: >> >>> oVirt users list, >>> >>> Long story short, I've been spending weeks on this project for my home >>> lab with no success. >>> >>> I would like to successfully install two nodes that host a highly >>> available engine with an iSCSI storage back-end. >>> >>> I have read through most, if not all, of the guides on ovirt.org with >>> no substantial help. >>> >>> Successfully, I have done the following: >>> Install oVirt Engine on a bare metal system, added a node, and started >>> exploring - not desired. >>> Install oVirt Node 4.0.6 on a bare metal system - fails if partitions >>> are not done automatically. >>> Install oVirt Node 4.1.2 on a bare metal system - fails if partitions >>> are not done automatically. >>> >> >> Can you please elaborate about the failure you see here and how are you >> trying to manually partition the host? >> >> >> >> >> >>> >>> My process after installing a Node: >>> Run a yum update - just to be sure, but I am using latest iso images >>> from downloads section. >>> Edit /etc/hosts for local name resolution - the goal is to host DNS as a >>> virtual machine, eventually. >>> On 4.1 if I install ovirt-engine-appliance from yum, it does simplify >>> one step in the hosted engine setup. If I do this on 4.0 it discards the >>> image and uses the default. >>> >> >> Being this a new install, please use 4.1. oVirt 4.0 is not supported >> anymore. >> >> >> >>> On 4.1 the hosted engine setup fails immediately unless I run the hosted >>> engine cleanup from the shell. >>> >> >> Can you please provide hosted engine setup logs or better a full sos >> report? (sosreport -a) >> >> >> >> >>> If I do this, I can typically get to the point of installing. >>> >>> When I do get to the installation phase, I get to a point just after >>> extracting the OVA that I get a message on the shell saying something about >>> the watchdog running the whole time and then the node reboots. >>> >>> I found one email thread that sounded like my issue and suggested the >>> following commands: >>> vdsm-tool configure --force >>> systemctl restart libvirtd >>> systemctl restart vdsmd >>> >>> Unfortunately, these commands did not help my situation like the other >>> individual. >>> >>> What log file would everyone like to see first? Given that I still >>> consider myself relatively new to Linux, please identify the path for the >>> log file requested. >>> >> >> See above >> >> >>> >>> Also, because I plan on performing a clean install for this thread using >>> my process from above (I'm not expecting my outcome to be any different), >>> are there any tips and tricks that might result in a success? >>> >> >> I'd like to understand the issues you faced before suggesting to restart >> from scratch. >> Adding some people who may help as well. >> >> >> >>> >>> Thank you for any and all help, >>> Brendan >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >>> >> >> >> -- >> >> SANDRO BONAZZOLA >> >> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D >> >> Red Hat EMEA <https://www.redhat.com/> >> <https://red.ht/sig> >> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >> > > -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

4 13

Seamless SAN HA failovers with oVirt?
by Matthew Trent 08 Jun '17

08 Jun '17

I'm using two TrueNAS HA SANs (FreeBSD-based ZFS) to provide storage via NFS to 7 oVirt boxes and about 25 VMs. For SAN system upgrades I've always scheduled a maintenance window, shut down all the oVirt stuff, upgraded the SANs, and spun everything back up. It's pretty disruptive, but I assumed that was the thing to do. However, in talking with the TrueNAS vendor they said the majority of their customers are using VMWare and they almost always do TrueNAS updates in production. They just upgrade one head of the TrueNAS HA pair then failover to the other head and upgrade it too. There's a 30-ish second pause in I/O while the disk arrays are taken over by the other HA head, but VMWare just tolerates it and continues without skipping a beat. They say this is standard procedure in the SAN world and virtualization systems should tolerate 30-60 seconds of I/O pause for HA failovers seamlessly. It sounds great to me, but I wanted to pick this lists' brain -- is anyone doing this with oVirt? Are you able to failover your HA SAN with 30-60 seconds of no I/O without oVirt freaking out? If not, are there any tunables relating to this? I see the default NFS mount options look fairly tolerant (proto=tcp,timeo=600,retrans=6), but are there VDSM or sanlock or some other oVirt timeouts that will kick in and start putting storage domains into error states, fencing hosts or something before that? I've never timed anything, but I want to say my past experience is that ovirt hosted engine started showing errors almost immediately when we've had SAN issues in the past. Thanks! -- Matthew Trent Network Engineer Lewis County IT Services

8 13

Host install common error
by FERNANDO FREDIANI 08 Jun '17

08 Jun '17

This is a multi-part message in MIME format. --------------B17F4A1A13CE833AC9902298 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello folks. One of the most (if not the more) annoying problems of oVirt is the known message "... installation failed. Command returned failure code 1 during SSH session ..." which happens quiet often in several situations. Scrubbing installation logs it seems that most stuff goes well, but then it stops in a message saying: "ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Setup validation': Cannot locate vdsm package, possible cause is incorrect channels" - followed by another message: "DEBUG otopi.context context.dumpEnvironment:770 ENV BASE/exceptionInfo=list:'[(<type 'exceptions.RuntimeError'>, RuntimeError('Cannot locate vdsm package, possible cause is incorrect channels',), <traceback object at 0x3131ef0>)]'" I am not sure why would it complain about the repositories as this is a Minimal CentOS 7 Install and the oVirt repository is added by oVirt-Engine itself so I assumed it added the most appropriate to its own version. I even tried to copy over the same repositories used on the Hosts that are installed and working fine but that message shows up again on the Install retries. Does anyone have any other hints where to look ? For reference my engine version running is: 4.1.1.6-1.el7.centos. Fernando --------------B17F4A1A13CE833AC9902298 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> Hello folks. One of the most (if not the more) annoying problems of oVirt is the known message "... installation failed. Command returned failure code 1 during SSH session ..." which happens quiet often in several situations. Scrubbing installation logs it seems that most stuff goes well, but then it stops in a message saying: "ERROR otopi.context context._executeMethod:151 Failed to execute stage 'Setup validation': Cannot locate vdsm package, possible cause is incorrect channels" - followed by another message: "DEBUG otopi.context context.dumpEnvironment:770 ENV BASE/exceptionInfo=list:'[(<type 'exceptions.RuntimeError'>, RuntimeError('Cannot locate vdsm package, possible cause is incorrect channels',), <traceback object at 0x3131ef0>)]'" I am not sure why would it complain about the repositories as this is a Minimal CentOS 7 Install and the oVirt repository is added by oVirt-Engine itself so I assumed it added the most appropriate to its own version. I even tried to copy over the same repositories used on the Hosts that are installed and working fine but that message shows up again on the Install retries. Does anyone have any other hints where to look ? For reference my engine version running is: 4.1.1.6-1.el7.centos. Fernando </body> </html> --------------B17F4A1A13CE833AC9902298--

5 4

User Portal and Multi-Monitor Support
by Bryan Sockel 08 Jun '17

08 Jun '17

Is there a way to enable multi monitor support when launching a RDP Session through the user Portal? Bryan Sockel Systems Administrator Alt-N Technologies | Grapevine, TX Office 817.601.3222 x233 Sent using Alt-N's own MDaemon Messaging Server Get to know the Alt-N family by liking us on Facebook!

1 0

Network interface not working
by Герасимов Александр 08 Jun '17

08 Jun '17

This is a multi-part message in MIME format. --------------DC86F700F56181ECDB9F4F15 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8; format=flowed Hi all. I have to servers with ovirt. And to identical virtual machines. Both servers are identical. But on second virtual server not working one network interface. Ping have a problem. I tried to change network driver, but has no effect. I don't understand that to do ovirt version and package: rpm -qa|grep ovirt ovirt-imageio-proxy-0.4.0-0.201608310602.gita9b573b.el7.centos.noarch ovirt-engine-vmconsole-proxy-helper-4.0.5.5-1.el7.centos.noarch ovirt-engine-restapi-4.0.5.5-1.el7.centos.noarch ovirt-engine-extensions-api-impl-4.0.5.5-1.el7.centos.noarch ovirt-imageio-daemon-0.4.0-1.el7.noarch ovirt-engine-wildfly-10.1.0-1.el7.x86_64 ovirt-vmconsole-1.0.4-1.el7.centos.noarch ovirt-engine-cli-3.6.9.2-1.el7.noarch ovirt-engine-websocket-proxy-4.0.5.5-1.el7.centos.noarch ovirt-engine-dashboard-1.0.5-1.el7.centos.noarch ovirt-host-deploy-1.5.3-1.el7.centos.noarch ovirt-engine-wildfly-overlay-10.0.0-1.el7.noarch ovirt-engine-setup-base-4.0.5.5-1.el7.centos.noarch ovirt-engine-dwh-setup-4.0.5-1.el7.centos.noarch ovirt-engine-setup-plugin-websocket-proxy-4.0.5.5-1.el7.centos.noarch ovirt-engine-setup-4.0.5.5-1.el7.centos.noarch ovirt-engine-dbscripts-4.0.5.5-1.el7.centos.noarch ovirt-engine-userportal-4.0.5.5-1.el7.centos.noarch ovirt-imageio-common-0.4.0-1.el7.noarch python-ovirt-engine-sdk4-4.0.2-1.el7.centos.x86_64 ovirt-vmconsole-host-1.0.4-1.el7.centos.noarch ovirt-engine-dwh-4.0.5-1.el7.centos.noarch ovirt-engine-tools-backup-4.0.5.5-1.el7.centos.noarch ovirt-image-uploader-4.0.1-1.el7.centos.noarch ovirt-engine-setup-plugin-ovirt-engine-4.0.5.5-1.el7.centos.noarch ovirt-engine-tools-4.0.5.5-1.el7.centos.noarch ovirt-engine-4.0.5.5-1.el7.centos.noarch ovirt-release40-4.0.5-2.noarch ovirt-host-deploy-java-1.5.3-1.el7.centos.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.0.5.5-1.el7.centos.noarch ovirt-iso-uploader-4.0.2-1.el7.centos.noarch ovirt-engine-webadmin-portal-4.0.5.5-1.el7.centos.noarch ovirt-setup-lib-1.0.2-1.el7.centos.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7.centos.noarch ovirt-engine-lib-4.0.5.5-1.el7.centos.noarch ovirt-imageio-proxy-setup-0.4.0-0.201608310602.gita9b573b.el7.centos.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.0.5.5-1.el7.centos.noarch ovirt-engine-backend-4.0.5.5-1.el7.centos.noarch ovirt-engine-extension-aaa-jdbc-1.1.1-1.el7.noarch ovirt-vmconsole-proxy-1.0.4-1.el7.centos.noarch -- С уважением, базисный админстратор Гераcимов Александр тел. +7(495)4116886 доб. 5367 --------------DC86F700F56181ECDB9F4F15 Content-Transfer-Encoding: 8bit Content-Type: text/html; charset=utf-8 <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> Hi all. I have to servers with ovirt. And to identical virtual machines. Both servers are identical. But on second virtual server not working one network interface. Ping have a problem. I tried to change network driver, but has no effect. I don't understand that to do ovirt version and package: rpm -qa|grep ovirt ovirt-imageio-proxy-0.4.0-0.201608310602.gita9b573b.el7.centos.noarch ovirt-engine-vmconsole-proxy-helper-4.0.5.5-1.el7.centos.noarch ovirt-engine-restapi-4.0.5.5-1.el7.centos.noarch ovirt-engine-extensions-api-impl-4.0.5.5-1.el7.centos.noarch ovirt-imageio-daemon-0.4.0-1.el7.noarch ovirt-engine-wildfly-10.1.0-1.el7.x86_64 ovirt-vmconsole-1.0.4-1.el7.centos.noarch ovirt-engine-cli-3.6.9.2-1.el7.noarch ovirt-engine-websocket-proxy-4.0.5.5-1.el7.centos.noarch ovirt-engine-dashboard-1.0.5-1.el7.centos.noarch ovirt-host-deploy-1.5.3-1.el7.centos.noarch ovirt-engine-wildfly-overlay-10.0.0-1.el7.noarch ovirt-engine-setup-base-4.0.5.5-1.el7.centos.noarch ovirt-engine-dwh-setup-4.0.5-1.el7.centos.noarch ovirt-engine-setup-plugin-websocket-proxy-4.0.5.5-1.el7.centos.noarch ovirt-engine-setup-4.0.5.5-1.el7.centos.noarch ovirt-engine-dbscripts-4.0.5.5-1.el7.centos.noarch ovirt-engine-userportal-4.0.5.5-1.el7.centos.noarch ovirt-imageio-common-0.4.0-1.el7.noarch python-ovirt-engine-sdk4-4.0.2-1.el7.centos.x86_64 ovirt-vmconsole-host-1.0.4-1.el7.centos.noarch ovirt-engine-dwh-4.0.5-1.el7.centos.noarch ovirt-engine-tools-backup-4.0.5.5-1.el7.centos.noarch ovirt-image-uploader-4.0.1-1.el7.centos.noarch ovirt-engine-setup-plugin-ovirt-engine-4.0.5.5-1.el7.centos.noarch ovirt-engine-tools-4.0.5.5-1.el7.centos.noarch ovirt-engine-4.0.5.5-1.el7.centos.noarch ovirt-release40-4.0.5-2.noarch ovirt-host-deploy-java-1.5.3-1.el7.centos.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.0.5.5-1.el7.centos.noarch ovirt-iso-uploader-4.0.2-1.el7.centos.noarch ovirt-engine-webadmin-portal-4.0.5.5-1.el7.centos.noarch ovirt-setup-lib-1.0.2-1.el7.centos.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7.centos.noarch ovirt-engine-lib-4.0.5.5-1.el7.centos.noarch ovirt-imageio-proxy-setup-0.4.0-0.201608310602.gita9b573b.el7.centos.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.0.5.5-1.el7.centos.noarch ovirt-engine-backend-4.0.5.5-1.el7.centos.noarch ovirt-engine-extension-aaa-jdbc-1.1.1-1.el7.noarch ovirt-vmconsole-proxy-1.0.4-1.el7.centos.noarch <pre class="moz-signature" cols="72">-- С уважением, базисный админстратор Гераcимов Александр тел. +7(495)4116886 доб. 5367</pre> </body> </html> --------------DC86F700F56181ECDB9F4F15--

2 5

[ANN] oVirt 4.1.3 First Release Candidate is now available
by Sandro Bonazzola 08 Jun '17

08 Jun '17

The oVirt Project is pleased to announce the availability of the First Release Candidate of oVirt 4.1.3 for testing, as of June 8th, 2017 This is pre-release software. Please take a look at our community page[1] to know how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This pre-release should not to be used in production. This update is the first release candidate of the third in a series of stabilization updates to the 4.1 series. 4.1.3 brings more than 35 enhancements and more than 170 bugfixes, including more than 100 high or urgent severity fixes, on top of oVirt 4.1 series This release is available now for: * Fedora 24 (tech preview) * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later * oVirt Node 4.1 * Fedora 24 (tech preview) See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available - oVirt Live is already available[4] - oVirt Node is already available[4] We are addressing compose issues for above components which are missing ansible 2.3 and latest fluentd builds from CentOS SIGs. Additional Resources: * Read more about the oVirt 4.1.3 release highlights: http://www.ovirt.org/release/4.1.3/ * 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] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.1.3/ [4] resources.ovirt.org/pub/ovirt-4.1-pre/iso/ -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

1 0