New network test failure on jenkins
by Nir Soffer
Hi all,
There is a new networking test failure in the ci:
16:18:11 ======================================================================
16:18:11 ERROR: test_dump_bonding_name2numeric
(toolBondingTests.TestToolBonding)
16:18:11 ----------------------------------------------------------------------
16:18:11 Traceback (most recent call last):
16:18:11 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/testValidation.py",
line 97, in wrapper
16:18:11 return f(*args, **kwargs)
16:18:11 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/modprobe.py",
line 58, in wrapper
16:18:11 return f(*args, **kwargs)
16:18:11 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/tests/toolBondingTests.py",
line 37, in test_dump_bonding_name2numeric
16:18:11 opt_map = _get_bonding_options_name2numeric()
16:18:11 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/tool/dump_bonding_opts.py",
line 94, in _get_bonding_options_name2numeric
16:18:11 opts[mode] = bond_opts_name2numeric_filtered(bond_name)
16:18:11 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/netinfo/bonding.py",
line 203, in bond_opts_name2numeric_filtered
16:18:11 in _bond_opts_name2numeric(bond).iteritems()
16:18:11 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/netinfo/bonding.py",
line 238, in _bond_opts_name2numeric
16:18:11 _bond_opts_name2numeric_scan(path)
16:18:11 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/netinfo/bonding.py",
line 247, in _bond_opts_name2numeric_scan
16:18:11 numeric_val)
16:18:11 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc23-x86_64/vdsm/lib/vdsm/netinfo/bonding.py",
line 259, in _bond_opts_name2numeric_getval
16:18:11 opt_write_file.flush()
16:18:11 IOError: [Errno 16] Device or resource busy:
'opt[/sys/class/net/Z7PxqN9gLALvKkE/bonding/lacp_rate],
numeric_val[1]'
See http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/1831/con...
Can someone from networking check this?
Thanks,
Nir
8 years, 3 months
oVirt 3.6.2 RC2 merge / tag / bugzilla reminder
by Simone Tiraboschi
All stable branch maintainers, please make sure to merge all relevant open
bugs until Tuesday morning 11:00 AM TLV time (10:00 CET).
https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3....
Every package build (i.e oVirt product) - please make sure every bug in
MODIFIED has the right Target Release and Target Milestone.
A Target release should state the version of the package you're building
and should include the same version you used for the tag you just used for
this build. (e.g. for ovirt-engine, tag will be: ovirt-engine-3.6.2, and
target release must be: 3.6.2)
8 years, 3 months
Re: [ovirt-devel] [ovirt-users] Nested KVM - vdsm-hook-nestedvt
by Eyal Edri
adding also devel, some developers might be able to help.
e.
On Fri, Jan 1, 2016 at 4:32 PM, Winfried de Heiden <wdh(a)dds.nl> wrote:
> Hi all and happy new year!
>
> I'm running oVirt 3.6 on EL7.
>
> In order to test nested-kvm I installed vdsm-hook-nestedvt on the
> hypervisor and put "fake_kvm_support = true" in /etc/vdsm/vdsm.conf.
>
> However, afterwards the hypervisor host cannot connect to the ovirt
> Manager, on ovirt Manager the engine.log will tell:
>
> 2016-01-01 15:21:42,105 WARN
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (DefaultQuartzScheduler_Worker-76) [71d1638c] Correlation ID: 29daf92c,
> Call Stack: null, Custom Event ID: -1, Message: Host bigvirt moved to
> Non-Operational state as host does not meet the cluster's minimum CPU
> level. Missing CPU features : model_Opteron_G3
>
> After removing the option all works well again, but I'ḿ lacking the nested
> kvm option :( Is nested kvm only supported on a limited cpu's??
>
> Winny
>
> Information from /proc/cpuinfo:
>
> processor : 0
> vendor_id : AuthenticAMD
> cpu family : 16
> model : 10
> model name : AMD Phenom(tm) II X6 1055T Processor
> stepping : 0
> microcode : 0x10000bf
> cpu MHz : 2800.000
> cache size : 512 KB
> physical id : 0
> siblings : 6
> core id : 0
> cpu cores : 6
> apicid : 0
> initial apicid : 0
> fpu : yes
> fpu_exception : yes
> cpuid level : 6
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt
> pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc
> extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm
> extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt
> cpb hw_pstate npt lbrv svm_lock nrip_save pausefilter
> bogomips : 5625.54
> TLB size : 1024 4K pages
> clflush size : 64
> cache_alignment : 64
> address sizes : 48 bits physical, 48 bits virtual
> power management: ts ttp tm stc 100mhzsteps hwpstate cpb
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
>
--
Eyal Edri
Associate Manager
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
8 years, 3 months
Re: [ovirt-devel] [VDSM] Running make check on *your* development machine
by Nir Soffer
On Tue, Dec 29, 2015 at 7:04 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote:
> On Tue, Dec 29, 2015 at 6:29 PM, Nir Soffer <nsoffer(a)redhat.com> wrote:
>>
>> Hi all,
>>
>> Recently we added a new test, breaking make check when run on a
>> development
>> machine as non-privileged user.
>> https://gerrit.ovirt.org/50984
>>
>> This test pass on the CI environment, because the tests are running as
>> root.
>
>
> Should we do something different in CI?
We should, but I want to discuss this in the devel mailing list.
Nir
> Y.
>
>>
>>
>> Please verify that "make check" is successful on your development
>> environment.
>> otherwise, you may break the tests for others using this practice.
>>
>>
>> Best practice for running the tests:
>>
>> 1. Run the tests for the module you change:
>>
>> $ ./run_tests_local.sh rwlock_test.py
>> nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$']
>> rwlock_test.RWLockStressTests
>> test_fairness(1, 2) SKIP:
>> Stress tests are disabled
>> test_fairness(2, 8) SKIP:
>> Stress tests are disabled
>> test_fairness(3, 32) SKIP:
>> Stress tests are disabled
>> test_fairness(4, 128) SKIP:
>> Stress tests are disabled
>> rwlock_test.RWLockTests
>> test_concurrent_readers OK
>> test_demotion_no_waiters OK
>> test_demotion_with_blocked_reader SKIP:
>> Slow tests are disabled
>> test_demotion_with_blocked_writer SKIP:
>> Slow tests are disabled
>> test_exclusive_context_blocks_reader SKIP:
>> Slow tests are disabled
>> test_exclusive_context_blocks_writer SKIP:
>> Slow tests are disabled
>> test_fifo SKIP:
>> Slow tests are disabled
>> test_promotion_forbidden OK
>> test_recursive_read_lock OK
>> test_recursive_write_lock OK
>> test_release_other_thread_read_lock OK
>> test_release_other_thread_write_lock OK
>> test_shared_context_allows_reader OK
>> test_shared_context_blocks_writer SKIP:
>> Slow tests are disabled
>> test_wakeup_all_blocked_readers SKIP:
>> Slow tests are disabled
>> test_wakeup_blocked_reader SKIP:
>> Slow tests are disabled
>> test_wakeup_blocked_writer SKIP:
>> Slow tests are disabled
>>
>> ----------------------------------------------------------------------
>> Ran 21 tests in 0.005s
>>
>> This should be very fast and should run after every change.
>>
>> 2. Check that slow and stress tests pass
>>
>> Some modules have @slowtest and @stresstest, which are skipped by default.
>> When modifying such modules, enable also these tests:
>>
>> $ ./run_tests_local.sh rwlock_test.py --enable-slow-tests
>> --enable-stress-tests
>> nose.config: INFO: Ignoring files matching ['^\\.', '^_', '^setup\\.py$']
>> rwlock_test.RWLockStressTests
>> test_fairness(1, 2) OK
>> test_fairness(2, 8) OK
>> test_fairness(3, 32) OK
>> test_fairness(4, 128) OK
>> rwlock_test.RWLockTests
>> test_concurrent_readers OK
>> test_demotion_no_waiters OK
>> test_demotion_with_blocked_reader SKIP:
>> Known issue in current code
>> test_demotion_with_blocked_writer OK
>> test_exclusive_context_blocks_reader OK
>> test_exclusive_context_blocks_writer OK
>> test_fifo OK
>> test_promotion_forbidden OK
>> test_recursive_read_lock OK
>> test_recursive_write_lock OK
>> test_release_other_thread_read_lock OK
>> test_release_other_thread_write_lock OK
>> test_shared_context_allows_reader OK
>> test_shared_context_blocks_writer OK
>> test_wakeup_all_blocked_readers OK
>> test_wakeup_blocked_reader OK
>> test_wakeup_blocked_writer OK
>>
>> ----------------------------------------------------------------------
>> Ran 21 tests in 14.054s
>>
>> This may take more time.
>>
>> 3. When the module tests pass, run "make check"
>>
>> make check
>>
>> This takes about 90 seconds.
>>
>> To run all tests, including slow and stress tests, use:
>>
>> make check-all
>>
>> This may take couple of minutes, so it is not recommended.
>>
>> Thanks,
>> Nir
>> _______________________________________________
>> Devel mailing list
>> Devel(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/devel
>
>
8 years, 3 months
