- Users - oVirt List Archives

Host ovritnode1 installation failed. Command returned failure code 1 during SSH session 'root@X.X.X.X'.
by fung jacky 07 Dec '17

07 Dec '17

hi, I encountered a problem. I am getting an error when adding a host to ovirt-engine:Host ovritnode1 installation failed. Command returned failure code 1 during SSH session ' root(a)192.168.1.152'. PS: all user and password is correct. I checked engine log, the information is as follows: 2017-12-06 18:58:52,995-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [617b92e4] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Correlation ID: 617b92e4, Call Stack: null, Custom ID: null, Custom Event ID: -1, Message: Installing Host ovirtnode1. Stage: Environment setup. 2017-12-06 18:58:53,029-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [617b92e4] EVENT_ID: VDS_INSTALL_IN_PROGRESS(509), Correlation ID: 617b92e4, Call Stack: null, Custom ID: null, Custom Event ID: -1, Message: Installing Host ovirtnode1. Stage: Environment packages setup. 2017-12-06 18:59:22,974-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [617b92e4] EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), Correlation ID: 617b92e4, Call Stack: null, Custom ID: null, Custom Event ID: -1, Message: *Failed to install Host ovirtnode1. Yum Cannot queue package iproute: Cannot retrieve metalink for repository: ovirt-4.1-epel/x86_64. Please verify its path and try again.* 2017-12-06 18:59:22,999-05 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (VdsDeploy) [617b92e4] EVENT_ID: VDS_INSTALL_IN_PROGRESS_ERROR(511), Correlation ID: 617b92e4, Call Stack: null, Custom ID: null, Custom Event ID: -1, Message: *Failed to install Host ovirtnode1. Failed to execute stage 'Environment packages setup': Cannot retrieve metalink for repository: ovirt-4.1-epel/x86_64. Please verify its path and try again.* How to solve this problem, please help analyze, thank you!

1 1

[ANN] oVirt 4.2.0 First Candidate Release is now available for testing
by Sandro Bonazzola 07 Dec '17

07 Dec '17

The oVirt Project is pleased to announce the availability of the First Candidate Release of oVirt 4.2.0, as of December 5th, 2017 This is pre-release software. This pre-release should not to be used in production. Please take a look at our community page[1] to learn how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This update is the first candidate release of the 4.2.0 version. This release brings more than 280 enhancements and more than one thousand bug fixes, including more than 500 high or urgent severity fixes, on top of oVirt 4.1 series. What's new in oVirt 4.2.0? - The Administration Portal has been completely redesigned using Patternfly, a widely adopted standard in web application design. It now features a cleaner, more intuitive design, for an improved user experience. - There is an all-new VM Portal for non-admin users. - A new High Performance virtual machine type has been added to the New VM dialog box in the Administration Portal. - Open Virtual Network (OVN) adds support for Open vSwitch software defined networking (SDN). - oVirt now supports Nvidia vGPU. - The ovirt-ansible-roles set of packages help users with common administration tasks. - Virt-v2v now supports Debian/Ubuntu based VMs. For more information about these and other features, check out the oVirt 4.2.0 blog post <https://ovirt.org/blog/2017/11/introducing-ovirt-4.2.0-beta/> and stay tuned for further blog post. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later * oVirt Node 4.2 (available for x86_64 only) 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 Node is already available [4] Additional Resources: * Read more about the oVirt 4.2.0 release highlights: http://www.ovirt.org/release/4.2.0/ * 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.2.0/ [4] http://resources.ovirt.org/pub/ovirt-4.2-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>

2 1

how to setup image-io-proxy after initially disabling it
by Gianluca Cecchi 06 Dec '17

06 Dec '17

Hello, I'm on oVirt 4.1.7, the latest in 4.1 right now. Initially in engine-setup when prompted I set Image I/O Proxy to false. Configure Image I/O Proxy : False Now instead I would like to enable it, but if I run engine-setup I can't find a way to do it. I can only confirm the settings in a whole or exit the setup... How can I do? Currently I have these packages already installed on the system ovirt-imageio-proxy-setup-1.0.0-0.201701151456.git89ae3b4.el7.centos.noarch ovirt-imageio-proxy-1.0.0-0.201701151456.git89ae3b4.el7.centos.noarch and [root@ovirt ~]# systemctl status ovirt-imageio-proxy ● ovirt-imageio-proxy.service - oVirt ImageIO Proxy Loaded: loaded (/usr/lib/systemd/system/ovirt-imageio-proxy.service; disabled; vendor preset: disabled) Active: inactive (dead) [root@ovirt ~]# Can I simply and manually enable/start the service through systemctl commands? The same question arises in case I had not / had enabled VMConsole Proxy and/or WebSocket Proxy during install and in a second time I want to enable / diable them. Thanks, Gianluca

3 9

Logical network setup with neutron
by Lakshmi Narasimhan Sundararajan 06 Dec '17

06 Dec '17

Hi Team, I am looking at integrating openstack neutron with oVirt. Reading the docs so far, and through my setup experiments, I can see that oVirt and neutron do seem to understand each other. But I need some helpful pointers to help me understand a few items during configuration. 1) During External Provider registration, a) although openstack keystone is currently supporting v3 api endpoints, only configuring v2 works. I see an exception otherwise.I have a feeling only v2 auth is supported with oVirt. b) Interface mappings. This I believe is a way for logical networks to switch/route traffic back to physical networks. This is of the form label:interface. Where label is placed on each Hosts network setting to point to the right physical interface. I did map label "red" when I setup Host networks to a physical Nic. And used "red:br-red, green:br-green" here, wherein my intention is to create a bridge br-red on each Host for this logical network and switch/route packets over the "red" label mapped physical nic on each host. And every vm attached to "red" logical network shall have a vnic placed on "br-red" Is my understanding correct? 2) Now I finally create a logical network using external provider "openstack neutron". Herein "Physical Network" parameter that I totally do not understand. If the registration were to have many interface mappings, is this a way of pinning to the right interface? I cannot choose, red, red:br-red... I can only leave it empty, So what is the IP address of the physical address argument part of logical network creation? "Optionally select the Create on external provider check box. Select the External Provider from the drop-down list and provide the IP address of the Physical Network". What this field means? I would appreciate some clarity and helpful pointers here. Best regards -- DISCLAIMER The information in this e-mail is confidential and may be subject to legal privilege. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you have received this communication in error, please address with the subject heading "Received in error," send to it(a)msystechnologies.com, then delete the e-mail and destroy any copies of it. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. The views, opinions, conclusions and other information expressed in this electronic mail and any attachments are not given or endorsed by the company unless otherwise indicated by an authorized representative independent of this message. MSys cannot guarantee that e-mail communications are secure or error-free, as information could be intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses, though all reasonable precautions have been taken to ensure no viruses are present in this e-mail. As our company cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments we recommend that you subject these to your virus checking procedures prior to use

2 1

Re: [ovirt-users] VDSM multipath.conf - prevent automatic management of local devices
by Ben Bradley 06 Dec '17

06 Dec '17

On 23/11/17 06:46, Maton, Brett wrote: > Might not be quite what you're after but adding > > # RHEV PRIVATE > > To /etc/multipath.conf will stop vdsm from changing the file. > ||| Hi there. Thanks for the reply. Yes I am aware of that and it seems that's what I will have to do. I have no problem with VDSM managing the file, I just wish it didn't automatically load local storage devices into multipathd. I'm still not clear on the purpose of this automatic management though. From what I can tell there is no difference to hosts/clusters made through this automatic management - i.e. you still have to add storage domains manually in oVirt. Could anyone give any info on the purpose of this auto-management of local storage devices into multipathd in VDSM? Then I will be able to make an informed decision as to the benefit of letting it continue. Thanks, Ben > > On 22 November 2017 at 22:42, Ben Bradley <listsbb(a)virtx.net > <mailto:listsbb@virtx.net>> wrote: > > Hi All > > I have been running ovirt in a lab environment on CentOS 7 for > several months but have only just got around to really testing things. > I understand that VDSM manages multipath.conf and I understand that > I can make changes to that file and set it to private to prevent > VDSM making further changes. > > I don't mind VDSM managing the file but is it possible to set to > prevent local devices being automatically added to multipathd? > > Many times I have had to flush local devices from multipath when > they are added/removed or re-partitioned or the system is rebooted. > It doesn't even look like oVirt does anything with these devices > once they are setup in multipathd. > > I'm assuming it's the VDSM additions to multipath that are causing > this. Can anyone else confirm this? > > Is there a way to prevent new or local devices being added > automatically? > > Regards > Ben > _______________________________________________ > Users mailing list > Users(a)ovirt.org <mailto:Users@ovirt.org> > http://lists.ovirt.org/mailman/listinfo/users > <http://lists.ovirt.org/mailman/listinfo/users> > >

2 1

hosted engine and about more than 1000 vms
by 董青龙 06 Dec '17

06 Dec '17

------=_Part_27087_1224232802.1512092523799 Content-Type: text/plain; charset=GBK Content-Transfer-Encoding: base64 SGksIGFsbAogICAgICAgIFdlIHdhbnQgdG8gZGVwbG95IGFuIGVudmlyb25tZW50IG9mIGhvc3Rl ZCBlbmdpbmUgd2hpY2ggd2lsbCBtYW5hZ2UgbW9yZSB0aGFuIDEwMDAgdm1zLiBIb3cgbWFueSB2 Y3B1cyBhbmQgbWVtb3J5IHNob3VsZCB3ZSBnaXZlIHRvIGhvc3RlZCBlbmdpbmU/IEFuZCBhcmUg dGhlcmUgYW55IG90aGVyIHRoaW5ncyBzaG91bGQgd2UgcGF5IGF0dGVudGlvbiB0bz8gSG9wZSBz b21lb25lIGNhbiBoZWxwLiBUaGFua3Mh ------=_Part_27087_1224232802.1512092523799 Content-Type: text/html; charset=GBK Content-Transfer-Encoding: base64 PGRpdiBzdHlsZT0ibGluZS1oZWlnaHQ6MS43O2NvbG9yOiMwMDAwMDA7Zm9udC1zaXplOjE0cHg7 Zm9udC1mYW1pbHk6QXJpYWwiPjxkaXY+SGksIGFsbDwvZGl2PjxkaXY+Jm5ic3A7ICZuYnNwOyAm bmJzcDsgJm5ic3A7IFdlIHdhbnQgdG8gZGVwbG95IGFuIGVudmlyb25tZW50IG9mIGhvc3RlZCBl bmdpbmUgd2hpY2ggd2lsbCBtYW5hZ2UgbW9yZSB0aGFuIDEwMDAgdm1zLiBIb3cgbWFueSB2Y3B1 cyBhbmQgbWVtb3J5IHNob3VsZCB3ZSBnaXZlIHRvIGhvc3RlZCBlbmdpbmU/IEFuZCBhcmUgdGhl cmUgYW55IG90aGVyIHRoaW5ncyBzaG91bGQgd2UgcGF5IGF0dGVudGlvbiB0bz8gSG9wZSBzb21l b25lIGNhbiBoZWxwLiBUaGFua3MhPC9kaXY+PC9kaXY+PGJyPjxicj48c3BhbiB0aXRsZT0ibmV0 ZWFzZWZvb3RlciI+PHA+Jm5ic3A7PC9wPjwvc3Bhbj4= ------=_Part_27087_1224232802.1512092523799--

2 1

Fedora support (was: [ANN] oVirt 4.2.0 Second Beta Release is now available for testing)
by Yedidyah Bar David 06 Dec '17

06 Dec '17

On Wed, Nov 29, 2017 at 7:29 PM, Blaster <Blaster(a)556nato.com> wrote: > Is Fedora not supported anymore? > > I've read the release notes for the 4.2r2 beta and 4.1.7, they mention > specific versions of RHEL and CentOS, but only mention Fedora by name, with > no specific version information. We currently have too many problems with fedora to call it even 'Technical Preview', as was done in the past. You can still use the nightly snapshots, and most things work, more-or-less, with some issues having known workarounds. See e.g.: https://bugzilla.redhat.com/showdependencytree.cgi?id=1460625&hide_resolved… And also: http://lists.ovirt.org/pipermail/devel/2017-August/030990.html (not sure that one is still relevant for Fedora 27, didn't check recently). > > On 11/15/2017 9:17 AM, Sandro Bonazzola wrote > > > This release is available now on x86_64 architecture for: > > * Red Hat Enterprise Linux 7.4 or later > > * CentOS Linux (or similar) 7.4 or later > > > This release supports Hypervisor Hosts on x86_64 and ppc64le architectures > for: > > * Red Hat Enterprise Linux 7.4 or later > > * CentOS Linux (or similar) 7.4 or later > > * oVirt Node 4.2 (available for x86_64 only) > > tp://lists.ovirt.org/mailman/listinfo/users > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > -- Didi

2 2

Failed deply of ovirt-engine using ovirt-node-ng-installer-ovirt-4.2-pre-2017120512.iso
by Roberto Nunin 06 Dec '17

06 Dec '17

I'm having trouble to deploy one three host hyperconverged lab using iso-image named above. My test environment is based on HPE BL680cG7 blade servers. These servers has 6 physical 10GB network interfaces (flexNIC), each one with four profiles (ethernet,FCoE,iSCSI,etc). I choose one of these six phys interfaces (enp5s0f0) and assigned it a static IPv4 address, for each node. After node reboot, interface ONBOOT param is still set to no. Changed via iLO interface to yes and restarted network. Fine. After gluster setup, with gdeploy script under Cockpit interface, avoiding errors coming from : /usr/share/gdepply/scripts/blacklist_all_disks.sh, start hosted-engine deploy. With the new version, I'm having an error never seen before: The Engine VM (10.114.60.117) and this host (10.114.60.134/24) will not be in the same IP subnet. Static routing configuration are not supported on automatic VM configuration. Failed to execute stage 'Environment customization': The Engine VM (10.114.60.117) and this host (10.114.60.134/24) will not be in the same IP subnet. Static routing configuration are not supported on automatic VM configuration. Hosted Engine deployment failed. There's no input field for HE subnet mask. Anyway in our class-c ovirt management network these ARE in the same subnet. How to recover from this ? I cannot add /24 CIDR in HE Static IP address field, it isn't allowed. Moreover, VM FQDN is asked two times during the deploy process. It's correct ? Some additional, general questions: NetworkManager: must be disabled deploying HCI solution ? In my attempt, wasn't disabled. There's some document to follow to perform a correct deploy ? Is this one still "valid" ? : https://ovirt.org/blog/2017/04/up-and-running-with-ovirt-4.1-and-gluster-st… Attached hosted-engine-setup log. TIA -- Roberto 110-006-970

2 1

New post on oVirt blog: LVM Configuration the Easy Way
by John Marks 05 Dec '17

05 Dec '17

Hello! Just a quick heads up that there is a new post on the oVirt blog: LVM Configuration the Easy Way <https://ovirt.org/blog/2017/12/lvm-configuration-the-easy-way/> In a nutshell: oVirt now features a simple way to prevent a host from scanning and then activating logical volumes that are not required directly by the host, by means of an LVM filter. Read the post <https://ovirt.org/blog/2017/12/lvm-configuration-the-easy-way/>. See you on the oVirt blog! Best, John -- John Marks Technical Writer, oVirt redhat Israel Cell: +972 52 8644 491 -- John Marks Technical Writer, oVirt redhat Israel Cell: +972 52 8644 491

1 0

Re: [ovirt-users] (no subject)
by Fred Rolland 05 Dec '17

05 Dec '17

(Please reply to the users list) Hi, This is from your log: 2017-12-03 16:03:20,731+08 WARN [org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor] (EE-ManagedThreadFactory-engine-Thread-1) [6e2b20a8] Playbook '/usr/share/ovirt-engine/../ovirt-ansible-roles/playbooks/ovirt-host-deploy.yml' does not exist, please ensure that ovirt-ansible-roles package is properly installed. 2017-12-03 16:03:20,733+08 ERROR [org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand] (EE-ManagedThreadFactory-engine-Thread-1) [6e2b20a8] Host installation failed for host 'cb723bbf-066b-4430-9aa1-25883434f800', 'node3': Failed to execute Ansible host-deploy role. Please check logs for more details: null You need to install the ovirt-ansible-roles package. Regards, Freddy On Mon, Dec 4, 2017 at 2:19 PM, ※秋天的童话 <2289826784(a)qq.com> wrote: > > > > ------------------ 原始邮件 ------------------ > *发件人:* "Fred Rolland";<frolland(a)redhat.com>; > *发送时间:* 2017年12月4日(星期一) 凌晨1:33 > *收件人:* "※秋天的童话"<2289826784(a)qq.com>;"users"<users(a)ovirt.org>; > *主题:* Re: [ovirt-users] (no subject) > > (Please always reply to the list) > > The log for the engine is located here: /var/log/ovirt-engine/engine.log > Other relevant logs can be found as described in [1] > > [1]https://www.ovirt.org/documentation/admin-guide/ > chap-Log_Files/#ovirt-engine-log-files > > On Sun, Dec 3, 2017 at 2:53 PM, ※秋天的童话 <2289826784(a)qq.com> wrote: > >> how to search the log about the Ovirt >> >> ---Original--- >> *From:* "Fred Rolland"<frolland(a)redhat.com> >> *Date:* 2017/12/3 20:50:31 >> *To:* "※秋天的童话"<2289826784(a)qq.com>; >> *Cc:* "users"<users(a)ovirt.org>; >> *Subject:* Re: [ovirt-users] (no subject) >> >> Hi, >> >> Can you attach logs? >> >> Thanks, >> Freddy >> >> On Sun, Dec 3, 2017 at 10:27 AM, ※秋天的童话 <2289826784(a)qq.com> wrote: >> >>> I have a problem about ovirt 4.2 version >>> >>> _______________________________________________ >>> Users mailing list >>> Users(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/users >>> >>> >> >

1 0