- Devel - oVirt List Archives

planned Jenkins restart
by Evgheni Dereveanchin 15 Aug '16

15 Aug '16

Hi everyone, I wanted to inform you that I'll restart Jenkins within the next couple of hours to apply a plugin update: https://ovirt-jira.atlassian.net/browse/OVIRT-679 I'll inform you once the process is finished. Regards, Evgheni Dereveanchin

1 1

ovirt-engine stable branch maintainer needed
by Eyal Edri 14 Aug '16

14 Aug '16

Hi, If you have rights for ovirt-engine 4.0 please merge [1] as it fixes the latest regression caused on engine-setup. The fix was merged already for master and verified it works there. [1] https://gerrit.ovirt.org/#/c/62317/ -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

3 2

oVirt Bot and oVirt Meetings
by Sandro Bonazzola 14 Aug '16

14 Aug '16

Hi, is the oVirt Bot meant to be down? The oVIrt website still mention it: http://www.ovirt.org/community/about/meetings/ http://www.ovirt.org/develop/infra/ovirtbot/ http://www.ovirt.org/develop/infra/running-ovirtbot/ http://www.ovirt.org/develop/infra/infrastructure-team-meetings/ Are listed meetings still valid? I don't think so. http://www.ovirt.org/community/about/meetings/ -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1

ovirt-shell in 4.0.1
by Paul Dyer 12 Aug '16

12 Aug '16

Hi, Is ovirt-engine-cil still funtional in ovirt 4.0.1? I have been able to use it to list VMs, but not for actions that require a name/id parameter. Here is what happens when I try to start a VM: $ ovirt-shell -f list-down-vms.txt ============================================ >>> connected to oVirt manager 4.0.1.0 <<< ============================================ [oVirt shell ( connected )]# list vms --kwargs "status-state=down" |grep name |sed s/'name *:'// rh6-dev12c-vm177 rh6-dev12c-vm178 rh6-dev12c-vm179 rh6-dev12c-vm180 rh6-dev12c-vm181 rh6-dev12c-vm182 rh6-dev12c-vm183 rh6-dev12c-vm184 rh6-dev12c-vm185 rh6-dev12c-vm186 rh6-dev12c-vm187 rh6-dev12c-vm188 rh6-dev12c-vm189 ========================================= >>> disconnected from oVirt manager <<< ========================================= $ ovirt-shell =========================================== >>> connected to oVirt manager 4.0.1.0 <<< =========================================== ++++++++++++++++++++++++++++++++++++++++++++ Welcome to oVirt shell ++++++++++++++++++++++++++++++++++++++++++++ [oVirt shell (connected)]# action vm rh6-dev12c-vm189 start ========================= ERROR ================= vm rh6-dev12c-vm189 does not exist. ================================================= [oVirt shell (connected)]# $ rpm -q --provides ovirt-engine-cli ovirt-engine-cli = 3.6.8.0-1.el7.centos Thanks, Paul -- Paul Dyer, Mercury Consulting Group, RHCE 504-302-8750

1 1

Which GlusterFS for oVirt 4.1?
by Sandro Bonazzola 11 Aug '16

11 Aug '16

Hi, currently we're building and composing master (will become 4.1) assuming GlusterFS 3.7 will be used. I see that 3.8 is available in Fedora 24 and on CentOS Storage SIG. Is it time to move to 3.8 for 4.1? Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 3

system tests failing
by Evgheni Dereveanchin 11 Aug '16

11 Aug '16

Hi everyone, We have the test-repo_ovirt_experimental_master job failing since build 717: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/717/ System tests are also starting to fail: http://jenkins.ovirt.org/job/ovirt_master_system-tests/380/ Here's the list of patches which appeared in build 717: https://gerrit.ovirt.org/#/c/61384/ - Sandro Bonazzola - packaging: spec: drop default defattr https://gerrit.ovirt.org/#/c/62026/ - Yaniv Bronhaim - Using %{_libdir} macro instead of /usr/lib https://gerrit.ovirt.org/#/c/62028/ - Yaniv Bronhaim - Require python2-devel specifically to avoid python3 pkg https://gerrit.ovirt.org/#/c/62049/ - Fabian Deutsch - Revert "imgbase: Drop journal support" https://gerrit.ovirt.org/#/c/62050/ - Fabian Deutsch - cli: Add journal logging The error is related to secondary storage domain addition, it sounds like a known bug but now it seems to be triggered every time. I'm not sure how we can identify the source of the regression since these tests run on repos of already built RPMs, so the complete set has to be re-built with a specific patch and tested to find out the offending one. Regards, Evgheni Dereveanchin

5 7

oVirt 4.1: plan to update patternfly?
by Sandro Bonazzola 10 Aug '16

10 Aug '16

Hi, we're currently using patternfly 1.3.0, I see 3.8.1 is out here https://github.com/patternfly/patternfly/releases Are there plan to update to it? -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

3 3

[ANN] oVirt 4.0.2 Fourth Release Candidate is now available
by Sandro Bonazzola 10 Aug '16

10 Aug '16

The oVirt Project is pleased to announce the availability of the Fourth Release Candidate of oVirt 4.0.2 for testing, as of August 10th, 2016. This release is available now for: * Fedora 23 (tech preview) * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.2 or later * CentOS Linux (or similar) 7.2 or later * Fedora 23 (tech preview) * oVirt Next Generation Node 4.0 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 fourth release candidate of the second in a series of stabilization updates to the 4.0 series. 4.0.2 brings 24 enhancements and more than 200 bugfixes, including 107 high or urgent severity fixes, on top of oVirt 4.0 series See the release notes [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO is available. [4] * A new oVirt Next Generation Node will be available soon [4]. * A new oVirt Engine Appliance is already available. * Mirrors[5] might need up to one day to synchronize. Additional Resources: * Read more about the oVirt 4.0.2 release highlights: http://www.ovirt.org/release/4.0.2/ * 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.0.2/ [4] http://resources.ovirt.org/pub/ovirt-4.0-pre/iso/ [5] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

OVS-based cluster adding vdsm report 'RTNETLINK answers: File exists' error in supervdsm.log in release 4.0.2
by lifuqiong 10 Aug '16

10 Aug '16

Hi, I want to test ovs in vdsm of release 4.0.2. And according Petr's helpful advice, created an ovs-based cluster and install vdsm to ovirt engine. But report a 'RTNETLINK answers: File exists' error as bellows. It seems that vdsm want to add a default gw through ' ip -4 route add default via 192.168.0.1' ; but of course this gateway already exists, why the vdsm will still add the default gateway? Error log: --------------------------------------------------------------------------------------------------------------------------------------------------------- MainProcess|jsonrpc.Executor/4::DEBUG::2016-08-02 22:35:03,203::commands::68::root::(execCmd) /usr/bin/taskset --cpu-list 0-3 /sbin/ip link set dev ovirtmgmt up (cwd None) MainProcess|jsonrpc.Executor/4::DEBUG::2016-08-02 22:35:03,205::commands::86::root::(execCmd) SUCCESS: <err> = ''; <rc> = 0 MainProcess|jsonrpc.Executor/4::DEBUG::2016-08-02 22:35:03,205::commands::68::root::(execCmd) /usr/bin/taskset --cpu-list 0-3 /sbin/ip link set dev p3p1 up (cwd None) MainProcess|jsonrpc.Executor/4::DEBUG::2016-08-02 22:35:03,207::commands::86::root::(execCmd) SUCCESS: <err> = ''; <rc> = 0 MainProcess|jsonrpc.Executor/4::DEBUG::2016-08-02 22:35:03,207::commands::68::root::(execCmd) /usr/bin/taskset --cpu-list 0-3 /sbin/ip addr flush dev ovirtmgmt scope global (cwd None) MainProcess|jsonrpc.Executor/4::DEBUG::2016-08-02 22:35:03,209::commands::86::root::(execCmd) SUCCESS: <err> = ''; <rc> = 0 MainProcess|jsonrpc.Executor/4::DEBUG::2016-08-02 22:35:03,209::commands::68::root::(execCmd) /usr/bin/taskset --cpu-list 0-3 /sbin/ip -4 addr add dev ovirtmgmt 192.168.0.117/255.255.255.0 (cwd None) MainProcess|jsonrpc.Executor/4::DEBUG::2016-08-02 22:35:03,211::commands::86::root::(execCmd) SUCCESS: <err> = ''; <rc> = 0 MainProcess|jsonrpc.Executor/4::DEBUG::2016-08-02 22:35:03,211::commands::68::root::(execCmd) /usr/bin/taskset --cpu-list 0-3 /sbin/ip -4 route add default via 192.168.0.1 (cwd None) MainProcess|jsonrpc.Executor/4::DEBUG::2016-08-02 22:35:03,213::commands::86::root::(execCmd) FAILED: <err> = 'RTNETLINK answers: File exists\n'; <rc> = 2 MainProcess|jsonrpc.Executor/4::DEBUG::2016-08-02 22:35:03,213::api::246::root::(setupNetworks) Setting up network according to configuration: networks:{u'ovirtmgmt': {'remove': True}}, bondings:{}, options:{'connectivityCheck': 0, 'inRollback': True} MainProcess|jsonrpc.Executor/4::DEBUG::2016-08-02 22:35:03,213::api::267::root::(_setup_networks) Validating configuration MainProcess|jsonrpc.Executor/4::DEBUG::2016-08-02 22:35:03,216::routes::75::root::(get_gateway) The gateway 192.168.0.1 is duplicated for the device p3p1 MainProcess|jsonrpc.Executor/4::ERROR::2016-08-02 22:35:03,310::supervdsmServer::96::SuperVdsm.ServerCallback::(wrapper) Error in setupNetworks Traceback (most recent call last): File "/usr/share/vdsm/supervdsmServer", line 94, in wrapper res = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/network/api.py", line 248, in setupNetworks _setup_networks(networks, bondings, options) File "/usr/lib/python2.7/site-packages/vdsm/network/api.py", line 275, in _setup_networks netswitch.setup(networks, bondings, options, in_rollback) File "/usr/lib64/python2.7/contextlib.py", line 35, in __exit__ self.gen.throw(type, value, traceback) File "/usr/lib/python2.7/site-packages/vdsm/network/api.py", line 199, in _rollback six.reraise(excType, value, tb) File "/usr/lib/python2.7/site-packages/vdsm/network/api.py", line 182, in _rollback yield File "/usr/lib/python2.7/site-packages/vdsm/network/api.py", line 275, in _setup_networks netswitch.setup(networks, bondings, options, in_rollback) File "/usr/lib/python2.7/site-packages/vdsm/network/netswitch.py", line 119, in setup _setup_ovs(ovs_nets, ovs_bonds, options, in_rollback) File "/usr/lib/python2.7/site-packages/vdsm/network/netswitch.py", line 165, in _setup_ovs connectivity.check(options) File "/usr/lib/python2.7/site-packages/vdsm/network/netconfpersistence.py", line 243, in __exit__ raise ne.RollbackIncomplete(config_diff, ex_type, ex_value) IPRoute2Error: ['RTNETLINK answers: File exists'] ip addr show -------------------------------------------------------------------------------------------------------------------------------------------------------------------- 　　 [root@server117 ~]# ip addr show 　　1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 　　 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 　　 inet 127.0.0.1/8 scope host lo 　　 valid_lft forever preferred_lft forever 　　 inet6 ::1/128 scope host 　　 valid_lft forever preferred_lft forever 　　2: p3p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master ovirtmgmt state UP qlen 1000 　　 link/ether 64:00:6a:23:b8:c0 brd ff:ff:ff:ff:ff:ff 　　3: em1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP qlen 1000 　　 link/ether a0:36:9f:09:36:c0 brd ff:ff:ff:ff:ff:ff 　　 inet6 fe80::a236:9fff:fe09:36c0/64 scope link 　　 valid_lft forever preferred_lft forever 　　4: em2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 　　 link/ether a0:36:9f:09:36:c1 brd ff:ff:ff:ff:ff:ff 　　5: wlp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 　　 link/ether 60:6d:c7:29:d7:55 brd ff:ff:ff:ff:ff:ff 　　6: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN 　　 link/ether 42:ab:a1:1b:24:94 brd ff:ff:ff:ff:ff:ff 　　7: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 　　 link/ether a0:36:9f:09:36:c0 brd ff:ff:ff:ff:ff:ff 　　 inet6 fe80::a236:9fff:fe09:36c0/64 scope link 　　 valid_lft forever preferred_lft forever 　　8: ovirtmgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP 　　 link/ether 64:00:6a:23:b8:c0 brd ff:ff:ff:ff:ff:ff 　　 inet 192.168.0.117/24 brd 192.168.0.255 scope global ovirtmgmt 　　 valid_lft forever preferred_lft forever 　　9: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN 　　 link/ether 4e:ce:20:14:aa:24 brd ff:ff:ff:ff:ff:ff 　　　　　　 How to solve it? Thank you. Mark Hope hear from you asap.

2 1

Re: [ovirt-devel] [ovirt-users] How to add ovs-based VM in version 4.0.2? Thank you
by lifuqiong 10 Aug '16

10 Aug '16

Hi petr, I followed your instruction last mail, re-install an Centos 7.2 1503(ip:192.168.0.117), and executing 'yum install http://plain.resources.ovirt.org/pub/ovirt-4.0-pre/rpm/el7/noarch/ovirt-rel…' On the new system. Creating an cluster using ovs-based network, and install vdsm(192.168.0.117); deploy log shows that meeting an error as follows: But I cann't find out the code which implements the function of setupNetworks, Just find the setupNetwork() function was defined in API.py, what does this function do actually, where is the code ? and how to fix this error? jsonrpc.Executor/4::ERROR::2016-08-02 22:35:03,321::__init__::549::jsonrpc.JsonRpcServer::(_handle_request) Internal server error Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 544, in _handle_request res = method(**params) File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 195, in _dynamicMethod result = fn(*methodArgs) File "/usr/share/vdsm/API.py", line 1465, in setupNetworks supervdsm.getProxy().setupNetworks(networks, bondings, options) File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in __call__ return callMethod() File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in <lambda> **kwargs) File "<string>", line 2, in setupNetworks File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod raise convert_to_error(kind, result) IPRoute2Error: ['RTNETLINK answers: File exists'] Hope get your help asp. Thank you Mark -----邮件原件----- 发件人: Petr Horacek [mailto:phoracek@redhat.com] 发送时间: 2016年8月3日 1:50 收件人: lifuqiong 抄送: Meni Yakove; Dan Kenigsberg; Michael Burman; devel 主题: Re: 答复: [ovirt-users] [ovirt-devel] How to add ovs-based VM in version 4.0.2? Thank you If everything goes well, it will be in master this week. I don't know when it will be part of 4.0. I installed master VDSM patched with https://gerrit.ovirt.org/#/q/topic:ovs_acquire on my host (Fedora 23 with disabled NetworkManager) and it worked OK. You can try to build it on your own [1]. If you hit any problem, feel free to ask. We'd like to go that way, but nothing specific yet. [1] http://www.ovirt.org/develop/developer-guide/vdsm/developers/ 2016-08-02 14:15 GMT+02:00 lifuqiong <lifuqiong(a)cncloudsec.com>: > Hi Petr, > Thank you > When the patch will merge to master? And when will the vdsm will release a version with this patch? > Btw, do you have a plan to support ovs with dpdk or vhost-user port? If so, what's the pipeline? > > Thank you > > -----邮件原件----- > 发件人: Petr Horacek [mailto:phoracek@redhat.com] > 发送时间: 2016年8月2日 19:53 > 收件人: lifuqiong > 抄送: Meni Yakove; Dan Kenigsberg; Michael Burman; devel > 主题: Re: [ovirt-users] [ovirt-devel] How to add ovs-based VM in version > 4.0.2? Thank you > > Clean == host that has just NICs, like right after system installation (no networks created by VDSM, bridges, bonds, vlans). Anyway, VDSM OVS is not able to acquire external NICs yet (the patch is under review and will be merged to master soon [1]). > > I would recommend you to wait for VDSM with mentioned patch merged. If you cannot wait, you can try to setup ovirtmgmt network manually via console (turn down NIC, setup OVS network on top of it). Not sure if this would help you. > > [1] https://gerrit.ovirt.org/#/c/60404/29 > > 2016-08-02 13:30 GMT+02:00 lifuqiong <lifuqiong(a)cncloudsec.com>: >> Hi Petr, >> Thank you for your advice. But what does "Clean hosts" mean, >> as I know now, When you add a clean Host to ovirt engine, the vdsm or ovirt node will create a Network named ovirtmgmt, which is an Linux bridge network, How do I clean the network? Just delete the linux bridge and reset the linux bridge binding's physical Nic? >> >> Hope to get your help as sonn as possible. >> Thank you. >> Mark >> >> -----邮件原件----- >> 发件人: Petr Horacek [mailto:phoracek@redhat.com] >> 发送时间: 2016年8月2日 18:29 >> 收件人: lifuqiong >> 抄送: Meni Yakove; Dan Kenigsberg; Michael Burman; users >> 主题: Re: [ovirt-users] [ovirt-devel] How to add ovs-based VM in >> version 4.0.2? Thank you >> >> If the host was a part of legacy cluster you must do manual cleanup of all networks. Currently VDSM cannot change Linux bridges into OVS ones (this will be implemented soon). Make sure that you are adding clean hosts (with NIC interface/s only) to OVS cluster. >> >> Regards, >> Petr >> >> 2016-08-02 10:01 GMT+02:00 Michael Burman <mburman(a)redhat.com>: >>> Hi , >>> >>> Did you synced network/s after you moved the host to the ovs type cluster? >>> It seems like you didn't..) >>> Go to 'Hosts' main tab' and choose the host, go to 'Network >>> Interfaces' sub tab and press the 'Sync All Networks' , now the >>> networks should be synced to host as ovs switch type. >>> Run the vm and check the xml. >>> It should look something like this: >>> >>> <source bridge='vdsmbr_nRL3asDq'/> >>> <virtualport type='openvswitch'> >>> >>> thanks >>> >>> >>> On Tue, Aug 2, 2016 at 9:37 AM, Meni Yakove <myakove(a)redhat.com> wrote: >>>> >>>> >>>> >>>> On Tue, Aug 2, 2016 at 7:12 AM, lifuqiong >>>> <lifuqiong(a)cncloudsec.com> >>>> wrote: >>>>> >>>>> I create a cluster which already enabled ovs network as you >>>>> mentioned , but when I create vm in this cluster, I can only >>>>> using ovirtmgmt/ovirtmgmt vNIC profile, which is still a Linux bridge. >>>>> >>>>> I found no way to add a OVS vNIC profile, I have to chose >>>>> ovirtmgmt/ovirtmgmt vNIC to setup a VM. After VM is started, the >>>>> vm is still using Linux bridge to communicate with outside, not the ovs. >>>>> >>>>> >>>>> >>>>> Need I to create a ovs bridge or vport and bind it to physical NIC >>>>> in vdsm manually? >>>>> >>>>> >>>>> >>>>> Hope your reply as soon as possible. >>>>> >>>>> Thank you >>>>> >>>>> Mark >>>>> >>>>> >>>>> >>>>> 发件人: users-bounces(a)ovirt.org [mailto:users-bounces@ovirt.org] 代表 >>>>> Meni Yakove >>>>> 发送时间: 2016年8月1日 16:42 >>>>> 收件人: Dan Kenigsberg >>>>> 主题: Re: [ovirt-users] [ovirt-devel] How to add ovs-based VM in >>>>> version 4.0.2? Thank you >>>>> >>>>> >>>>> >>>>> On Mon, Aug 1, 2016 at 11:07 AM, Dan Kenigsberg >>>>> <danken(a)redhat.com> >>>>> wrote: >>>>> >>>>> On Mon, Aug 01, 2016 at 02:02:52PM +0800, lifuqiong wrote: >>>>> > Hi, I upgrade my ovirt to version 4.0.2.2, how to using ovs in >>>>> > this version? >>>>> > Is there any instruction? Thank you >>>>> >>>>> Please note and note well: OVS is not production-grade yet. It is >>>>> only a preliminary tech preview, under active development. >>>>> >>>>> However, we'd be very happy to get your help in testing it (and >>>>> possibly fixing it, too). >>>>> >>>>> When defining a new cluster, you should see a check box, letting >>>>> you select OVS for that cluster. >>>>> >>>>> >>>>> >>>>> To be precise, this is not a check box. In the Edit Cluster >>>>> dialog, look at the "switch >>>>> >>>>> type" option, and change "LEGACY" to "OVS". >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> After being checked, each VM network that is defined in your >>>>> cluster would be implemented with OVS instead of Linux bridge. >>>>> >>>>> As aluded before, there are plenty of known definciencies (e.g., >>>>> no persistence of ip config on VM network, no live migration, not >>>>> all bond modes, etc etc). But do not hesitate to raise other >>>>> issues with the devel mailing list. >>>>> >>>>> Happy testing! >>>>> >>>>> Dan. >>>>> _______________________________________________ >>>>> Devel mailing list >>>>> Devel(a)ovirt.org >>>>> http://lists.ovirt.org/mailman/listinfo/devel >>>>> >>>>> >>>> >>>> >>> >>> >>> >>> -- >>> Michael Burman >>> RedHat Israel, RHEV-M QE Network Team >>> >>> Mobile: 054-5355725 >>> IRC: mburman >> >

3 3