- Users - oVirt List Archives

[Users] Node setup on Fedora 19
by Jakub Bittner 24 Jul '13

24 Jul '13

Hello, I am trying to setup fedora 19 server as ovirt node, but it still failing with network. Here is the log: 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND 2013-07-24 12:54:55 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.bridge bridge._rhel_getInterfaceConfigParameters:406 Readig interface parameters of em1 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND 2013-07-24 12:54:55 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.bridge plugin.executeRaw:347 execute: ('/bin/nmcli', 'dev', 'list', 'iface', u'em1'), executable='None', cwd='None', env=None 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND 2013-07-24 12:54:55 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.bridge plugin.executeRaw:364 execute-result: ('/bin/nmcli', 'dev', 'list', 'iface', u'em1'), rc=0 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND 2013-07-24 12:54:55 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.bridge plugin.execute:412 execute-output: ('/bin/nmcli', 'dev', 'list', 'iface', u'em1') stdout: 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND GENERAL.DEVICE: em1 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND GENERAL.TYPE: 802-3-ethernet 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND GENERAL.VENDOR: Broadcom Corporation 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND GENERAL.PRODUCT: -- 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND GENERAL.DRIVER: bnx2 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND GENERAL.DRIVER-VERSION: 2.2.3 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND GENERAL.FIRMWARE-VERSION: 6.2.12 bc 5.2.3 NCSI 2.0.11 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND GENERAL.HWADDR: E8:9A:8F:13:AF:51 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND GENERAL.STATE: 100 (connected) 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND GENERAL.REASON: 0 (No reason given) 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND GENERAL.UDI: /sys/devices/pci0000:00/0000:00:09.0/0000:07:00.0/net/em1 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND GENERAL.IP-IFACE: em1 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND GENERAL.NM-MANAGED: yes 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND GENERAL.AUTOCONNECT: yes 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND GENERAL.FIRMWARE-MISSING: no 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND GENERAL.CONNECTION: /org/freedesktop/NetworkManager/ActiveConnection/0 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND CAPABILITIES.CARRIER-DETECT: yes 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND CAPABILITIES.SPEED: 1000 Mb/s 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND CONNECTIONS.AVAILABLE-CONNECTION-PATHS: /org/freedesktop/NetworkManager/Settings/{7} 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND CONNECTIONS.AVAILABLE-CONNECTIONS[1]: 4fa38552-a2e6-41f7-abf9-5257f5e80847 | eno1 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND WIRED-PROPERTIES.CARRIER: on 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND IP4.ADDRESS[1]: ip = 192.168.3.212/24, gw = 192.168.3.1 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND IP4.DNS[1]: 192.168.3.214 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND 2013-07-24 12:54:55 DEBUG otopi.plugins.ovirt_host_deploy.vdsm.bridge plugin.execute:417 execute-output: ('/bin/nmcli', 'dev', 'list', 'iface', u'em1') stderr: 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND 2013-07-24 12:54:55 DEBUG otopi.context context._executeMethod:130 method exception 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND Traceback (most recent call last): 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND File "/tmp/ovirt-lKUu6m5wHT/pythonlib/otopi/context.py", line 120, in _executeMethod 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND method['method']() 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND File "/tmp/ovirt-lKUu6m5wHT/otopi-plugins/ovirt-host-deploy/vdsm/bridge.py", line 751, in _misc 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND parameters = self._rhel_getInterfaceConfigParameters(name=interface) 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND File "/tmp/ovirt-lKUu6m5wHT/otopi-plugins/ovirt-host-deploy/vdsm/bridge.py", line 465, in _rhel_getInterfaceConfigParameters 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND ''.ljust(prefix, '1') + 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND TypeError: an integer is required 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND 2013-07-24 12:54:55 ERROR otopi.context context._executeMethod:139 Failed to execute stage 'Misc configuration': an integer is required 2013-07-24 12:54:55 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:215 DIALOG:SEND 2013-07-24 12:54:55 DEBUG otopi.transaction transaction.abort:131 aborting 'Yum Transaction'

3 6

[Users] [ANN] oVirt 3.3 Test Day - Tomorrow Wed - Jul 24th
by Moran Goldboim 24 Jul '13

24 Jul '13

This is a multi-part message in MIME format. --------------060503070604080704040108 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit oVirt 3.3 release is just around the corner, and we would like to invite you all to take a taste of the new release [1]. http://www.ovirt.org/OVirt_3.3_TestDay Tomorrow morning (when all repos are packages are ready - finger crossed) you are invited to: -checkout Test Day page [2] -choose a distro (el6/fc19) -install oVirt [3] -check out the version -report what you find Developers and Users will be available in the channel/ on list to support in case there is trouble Thanks [1] http://www.ovirt.org/OVirt_3.3_release-management [2] http://www.ovirt.org/OVirt_3.3_TestDay [3]http://www.ovirt.org/Download --------------060503070604080704040108 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> oVirt 3.3 release is just around the corner, and we would like to invite you all to take a taste of the new release [1]. <a href="http://www.ovirt.org/OVirt_3.3_TestDay">http://www.ovirt.org/OVirt_3.3_TestDay</a> Tomorrow morning (when all repos are packages are ready - finger crossed) you are invited to: -checkout Test Day page [2] -choose a distro (el6/fc19) -install oVirt [3] -check out the version -report what you find Developers and Users will be available in the channel/ on list to support in case there is trouble  Thanks [1] <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <a href="http://www.ovirt.org/OVirt_3.3_release-management">http://www.ovirt.org/OVirt_3.3_release-management</a> [2] <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <a href="http://www.ovirt.org/OVirt_3.3_TestDay">http://www.ovirt.org/OVirt_3.3_TestDay</a> [3]<a class="moz-txt-link-freetext" href="http://www.ovirt.org/Download">http://www.ovirt.org/Download</a> </body> </html> --------------060503070604080704040108--

1 1

[Users] Nagios monitoring plugin check_rhev3 1.2.1 released
by René Koch (ovido) 24 Jul '13

24 Jul '13

I'm happy to announce version 1.2.1 of check_rhev3. check_rhev3 is a monitoring plugin for Icinga/Nagios and it's forks, which is used to monitor datacenters, clusters, hosts, vms, vm pools and storage domains of Red Hat Enterprise Virtualization (RHEV) and oVirt virtualization environments. Download this plugin from: https://github.com/ovido/check_rhev3/releases/check_rhev3-1.2.1 For further information on how to install this plugin visit: https://github.com/ovido/check_rhev3/wiki/Installation-Documentation A detailed usage documentation can be found here: https://github.com/ovido/check_rhev3/wiki/Usage-Documentation Changelog: * Bug fixed: * Fixed search regex for hosts and networks If you have any questions or ideas, please drop me an email: r.koch(a)ovido.at. Thank you for using check_rhev3. -- Best regards René Koch Senior Solution Architect ============================================ ovido gmbh - "Das Linux Systemhaus" Brünner Straße 163, A-1210 Wien Phone: +43 720 / 530 670 Mobile: +43 660 / 512 21 31 E-Mail: r.koch(a)ovido.at ============================================

4 7

[Users] [ANN] oVirt 3.3 Test Day - Tomorrow Wed - Jul 24th
by Moran Goldboim 24 Jul '13

24 Jul '13

Short update - rpms for ovirt-engine, are not up in the repo yet - and being copied ATM. we'll send a short update when it's there - should be in beta repo [1] [1] http://resources.ovirt.org/releases/beta/rpm/ -------- Original Message -------- Subject: Fwd: [Users] [ANN] oVirt 3.3 Test Day - Tomorrow Wed - Jul 24th Date: Tue, 23 Jul 2013 15:23:35 +0300 From: Moran Goldboim <mgoldboi(a)redhat.com> To: engine-devel <engine-devel(a)ovirt.org>, vdsm-devel(a)ovirt.org Feature owners, please make sure: -your feature is updated on release table page [1]. -you have test page for your feature [2]. -your team regression testing section is organized and up to date [3]. Thanks. [1] http://www.ovirt.org/OVirt_3.3_release-management#Features_Status_Table [2] http://www.ovirt.org/OVirt_3.3_TestDay#oVirt_3.3_New_Features_-_Test_Status… [3] http://www.ovirt.org/OVirt_3.3_TestDay#Regression_testing -------- Original Message -------- Subject: [Users] [ANN] oVirt 3.3 Test Day - Tomorrow Wed - Jul 24th Date: Tue, 23 Jul 2013 15:00:23 +0300 From: Moran Goldboim <mgoldboi(a)redhat.com> CC: users(a)ovirt.org <users(a)ovirt.org> oVirt 3.3 release is just around the corner, and we would like to invite you all to take a taste of the new release [1]. http://www.ovirt.org/OVirt_3.3_TestDay Tomorrow morning (when all repos are packages are ready - finger crossed) you are invited to: -checkout Test Day page [2] -choose a distro (el6/fc19) -install oVirt [3] -check out the version -report what you find Developers and Users will be available in the channel/ on list to support in case there is trouble Thanks [1] http://www.ovirt.org/OVirt_3.3_release-management [2] http://www.ovirt.org/OVirt_3.3_TestDay [3]http://www.ovirt.org/Download

1 1

Re: [Users] VLANs and oVirt 3.1
by jplorier＠gmail.com 23 Jul '13

23 Jul '13

Hi, maybe you have pvid of the bond in the 494 vlan (in the switch) and so the traffic you get is untagged. When you manually mark the network to be tagged, you'll discard the untagged packets Regards Juan Pablo Lorier

1 0

[Users] VLANs and oVirt 3.1
by Jason Keltz 23 Jul '13

23 Jul '13

In my test setup for oVirt 3.1, I have 3 switches -- two basic ones with no VLAN support for mgmt, and storage, and a building switch with VLAN support. The network operations team has configured a trunk with 2 dual 1 Gb links on the building switch. If I configure the two network interfaces in oVirt with binding mode 4, and assign a logical network to the link without specifying a VLAN, it works fine. I'm told the default untagged VLAN is 494 (which is what I want). On the other hand, if I simply hard-code VLAN 494 in the logical network setup, it doesn't work - I get no network traffic. I'm told that the switch is setup correctly, and the problem is on my side. How can I debug? Thanks, Jason.

2 2

[Users] VLANs and oVirt 3.1
by Jason Keltz 23 Jul '13

23 Jul '13

I'm experimenting with VLANs in my oVirt test setup with 3.1. My ovirtmgmt, and storage network are each on a basic switch with no VLANs. On the other hand, my public network has several VLANs available to me. The network operations team created a trunk for me with 2 x 1 GbT ports, aggregated with LACP, and passed it on with all VLANs. In oVirt, if I bind the two network interfaces, and, and assign one IP to the bind (mode 4) without specifying a VLAN, everything works fine (untagged VLANS are assigned ID 494 which is what I want). On the other hand, if I specify VLAN 494 in the logical network setup (or any of the other VLANs), it fails. I don't see any traffic. Network operations says that all VLANs are passed on the trunk. How can I debug? Jason.

1 0

[Users] New UI plugin: UI-VDSM-Hooks
by Daniel Erez 23 Jul '13

23 Jul '13

Hi, I've created a new UI plugin that allows invocation of VDSM commands directly from the WebAdmin (using CGI scripts and vdsClient). You can read all about it in my blog: http://derezvir.blogspot.co.il/ Thanks, Daniel

6 9

[Users] [ANN] ovirt nigthly rpms for fedora19 available for download
by Eyal Edri 23 Jul '13

23 Jul '13

Fyi, fedora19 rpm for ovirt projects are now available on http://resources.ovirt.org/releases/nightly/rpm/Fedora/19. Eyal.

1 0

[Users] Node installation dialog
by Jakub Bittner 23 Jul '13

23 Jul '13

Hello, I have problems with installing ovirt node (2.6.1). I think, it fails during grub install. The only ERROR in ovirt.log is "Root partition not found". I booted to live-cd and running from it fine, but I want to try to run installation, but I dont know which command to run to install. Do anybody know? Thank you, Jakub Bittner

2 8