Please use package versions when building rpms
by Dafna Ron
Hi All,
As some of you may have noticed, we have been having failures for some of
the tests in master in the past 24 hours with the following yum error:
https://pastebin.com/vqJCLgrP
After some debugging we found that the issue is caused because the package
which is failing had two different commits and no version set which caused
two different packages with exactly the same name to be created.
To solve this issue we would need the package to be re-build with a new
version set.
Here are the details on the package and how it failed.
As you can see below we had two different commits creating two different
packages by the same name:
https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-image-
template_standard-on-ghpush/30/
which was triggered by push: 00f5ffd4-a06e-11e8-8fc7-fa3846728ab0
https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-image-
template_standard-on-ghpush/31/
which was triggered by push: 3dfc5996-a09b-11e8-856c-ec86908871c4
checking the packages that exist in the 4.2 and master tested repos I can
see that we have the same exact name for two different packages:
4.2:
ovirt-ansible-image-template-1.1.7-1.el7.noarch.rpm:
Header SHA1 digest: OK (0033d83c3d8b6b0506767de3a4e44ffd64b2605c)
MD5 digest: OK (2b6e87e53a51175aeac61662561c0e20)
master:
ovirt-ansible-image-template-1.1.7-1.el7.noarch.rpm:
Header SHA1 digest: OK (597577a11775a7fc21207f3e76fe4df8a5030912)
MD5 digest: OK (74bafadf2afae5f7797a90c982ad2767)
This would cause yum to fail because we cannot have the same package name
with different checksums.
If anyone needs help in setting up versioning please contact myself or
anyone from the CI team and we would be happy to assist.
Thanks,
Dafna
6 years, 4 months
how do I setup LDAP for dev server?
by Greg Sheremeta
Hi,
I'm trying to tie my 389ds server to my dev engine built from source. I
followed the instructions [
https://www.ovirt.org/documentation/admin-guide/chap-Users_and_Roles/] for
configuring LDAP (which assume an RPM installation, I think), and then
copied the /etc config files to ~greg/ovirt-engine/etc/ovirt-engine
ERROR [org.ovirt.engine.core.sso.utils.SsoExtensionsManager] (ServerService
Thread Pool -- 44) [] Could not load extension based on configuration file
'/home/greg/ovirt-engine/etc/ovirt-engine/extensions.d/lan-authn.properties'.
Please check the configuration file is valid. Exception message is: Error
loading extension 'lan-authn': The module
'org.ovirt.engine-extensions.aaa.ldap' cannot be loaded:
org.ovirt.engine-extensions.aaa.ldap
ERROR [org.ovirt.engine.core.sso.utils.SsoExtensionsManager] (ServerService
Thread Pool -- 44) [] Could not load extension based on configuration file
'/home/greg/ovirt-engine/etc/ovirt-engine/extensions.d/lan.properties'.
Please check the configuration file is valid. Exception message is: Error
loading extension 'lan': The module 'org.ovirt.engine-extensions.aaa.ldap'
cannot be loaded: org.ovirt.engine-extensions.aaa.ldap
What am I missing? Are there developer instructions for this somewhere?
Best wishes,
Greg
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
<https://www.redhat.com/>
gshereme(a)redhat.com IRC: gshereme
<https://red.ht/sig>
6 years, 4 months
[ OST Failure Report ] [ oVirt 4.2 (imgbased) ] [ 09-08-2018 ] [ 004_basic_sanity.check_snapshot_with_memory ]
by Dafna Ron
Hi,
We have a failure in 4.2 which I think may be related to the patch itself.
Jira opened with additional info:
https://ovirt-jira.atlassian.net/browse/OVIRT-2418
*Link and headline of suspected patches: *
*We failed patch https://gerrit.ovirt.org/#/c/93545/
<https://gerrit.ovirt.org/#/c/93545/> - core: remove lvs after a failed
upgrade on ovirt-4.2Link to Job:*
* https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2819/
<https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2819/>Link to
all logs:*
* https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2819/artifact...
<https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2819/>(Relevant)
error snippet from the log: <error>*
Error Message
Fault reason is "Operation Failed". Fault detail is "[Cannot run VM.
Low disk space on Storage Domain iscsi.]". HTTP response code is 409.
Stacktrace
Traceback (most recent call last):
File "/usr/lib64/python2.7/unittest/case.py", line 369, in run
testMethod()
File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line
142, in wrapped_test
test()
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line
60, in wrapper
return func(get_test_prefix(), *args, **kwargs)
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line
79, in wrapper
prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs
File "/home/jenkins/workspace/ovirt-4.2_change-queue-tester/ovirt-system-tests/basic-suite-4.2/test-scenarios/004_basic_sanity.py",
line 589, in check_snapshot_with_memory
vm_service.start()
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/services.py",
line 30074, in start
return self._internal_action(action, 'start', None, headers, query, wait)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
299, in _internal_action
return future.wait() if wait else future
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
55, in wait
return self._code(response)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
296, in callback
self._check_fault(response)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
134, in _check_fault
self._raise_error(response, body.fault)
File "/usr/lib64/python2.7/site-packages/ovirtsdk4/service.py", line
118, in _raise_error
raise error
Error: Fault reason is "Operation Failed". Fault detail is "[Cannot
run VM. Low disk space on Storage Domain iscsi.]". HTTP response code
is 409.
*</error>*
6 years, 4 months
