Error: Adding new Host to ovirt-engine
by Ahmad Khiet
Hi,
Can't add new host to ovirt engine, because the following error:
2019-06-12 12:23:09,664 p=4134 u=engine | TASK [ovirt-host-deploy-facts :
Set facts] *************************************
2019-06-12 12:23:09,684 p=4134 u=engine | ok: [10.35.1.17] => {
"ansible_facts": {
"ansible_python_interpreter": "/usr/bin/python2",
"host_deploy_vdsm_version": "4.40.0"
},
"changed": false
}
2019-06-12 12:23:09,697 p=4134 u=engine | TASK [ovirt-provider-ovn-driver
: Install ovs] *********************************
2019-06-12 12:23:09,726 p=4134 u=engine | fatal: [10.35.1.17]: FAILED! =>
{}
MSG:
The conditional check 'cluster_switch == "ovs" or (ovn_central is defined
and ovn_central | ipaddr and ovn_engine_cluster_version is
version_compare('4.2', '>='))' failed. The error was: The ipaddr filter
requires python's netaddr be installed on the ansible controller
The error appears to be in
'/home/engine/apps/engine/share/ovirt-engine/playbooks/roles/ovirt-provider-ovn-driver/tasks/configure.yml':
line 3, column 5, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
- block:
- name: Install ovs
^ here
2019-06-12 12:23:09,728 p=4134 u=engine | PLAY RECAP
*********************************************************************
2019-06-12 12:23:09,728 p=4134 u=engine | 10.35.1.17 :
ok=3 changed=0 unreachable=0 failed=1 skipped=0 rescued=0
ignored=0
whats missing!?
Thanks
--
Ahmad Khiet
Red Hat <https://www.redhat.com/>
akhiet(a)redhat.com
M: +972-54-6225629
<https://red.ht/sig>
1 month, 2 weeks
oVirt Community - open discussion around repositories and workflows
by Sandro Bonazzola
Dear community members,
We would like to take some next steps in improving usability and general
decision making for our community and are interested in your thoughts and
suggestions.
The first step is a decision regarding our version control and workflows
associated with it. Contributions to new features and general improvements
for oVirt outside of Red Hat have been rare and we would like to hear from
you if we could simplify this process for you. One suggestion we have is
that we could simplify the contribution process and improve the contributor
experience by moving our repositories to GitHub or GitLab.
Currently, our Gerrit (gerrit.ovirt.org) instance is mirrored to GitHub and
we already have several repositories that are exclusively developed there,
including their CI running on GitHub Actions, for example:
* https://github.com/oVirt/go-ovirt-client
* https://github.com/oVirt/512-byte-vm
There are also various related projects that run on GitLab, such as:
* https://gitlab.com/qemu-project
* https://gitlab.com/libvirt
One recent project that moved from Gerrit to GitLab with a very similar
discussion is mediawiki:
https://www.mediawiki.org/wiki/GitLab_consultation/Discussion_summary
Once we hear more of your thoughts around this and if the decision falls on
moving to either GitHub or GitLab, our plan would be to start changing
existing workflows and CI project by project as it makes sense. Both
platforms offer similar features. Two key points that stand out for us are
that:
* GitLab is open source while GitHub isn't
* GitHub is more visible which allows contributors to amplify their
contributions and raise their profile by contributing to various big
projects, including oVirt
We are looking forward to hearing your thoughts,
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
1 year, 10 months
Another CI failure
by Milan Zamazal
Hi,
as demonstrated in
https://jenkins.ovirt.org/job/vdsm_standard-check-patch/31133/, OST
builds can at least start now but still fail, apparently due to the
following:
+ sudo -n usermod -a -G jenkins qemu
usermod: user 'qemu' does not exist
+ log ERROR 'Failed to add user qemu to group jenkins'
+ local level=ERROR
+ shift
+ local 'message=Failed to add user qemu to group jenkins'
+ local prefix
+ [[ 4 -gt 1 ]]
+ prefix='global_setup[lago_setup]'
+ echo 'global_setup[lago_setup] ERROR: Failed to add user qemu to group jenkins'
global_setup[lago_setup] ERROR: Failed to add user qemu to group jenkins
+ return 1
+ failed=true
What can be done about it?
Thanks,
Milan
1 year, 10 months
ovirt-engine dependency on ovirt-engine-extensions-api
by Sandro Bonazzola
Hi,
In ovirt-engine pom.xml there's a requirement for build time
on ovirt-engine-extensions-api = 1.0.0.
This dependency is available on maven central so online build works.
Any clue on why we are not requiring 1.0.1
<https://search.maven.org/artifact/org.ovirt.engine.api/ovirt-engine-exten...>
instead ?
We are packaging ovirt-engine-extensions-api during the development but it
ships 1.0.2.SNAPSHOT so when building in offline mode (needed for building
on CentOS Virt SIG) it fails as the 1.0.0 artifact was never downloaded.
I can rebuild ovirt-engine-extensions-api from 1.0.0 or 1.0.1 which are
available in maven central too as requiring explicitly 1.0.2.SNAPSHOT fails
with:
Failed to execute goal on project common-dependencies: Could not resolve
dependencies for project
org.ovirt.engine.core.manager:common-dependencies:jar:4.5.0-SNAPSHOT: The
following artifacts could not be resolved:
org.ovirt.engine.api:ovirt-engine-extensions-api:jar:1.0.2.SNAPSHOT,
org.ovirt.java-client-kubevirt:java-client-kubevirt:jar:0.5.0,
org.apache.sshd:sshd-common:jar:2.6.0, org.apache.sshd:sshd-core:jar:2.6.0,
net.i2p.crypto:eddsa:jar:0.3.0,
org.ovirt.engine.api:metamodel-server:jar:1.3.7,
org.ovirt.vdsm-jsonrpc-java:vdsm-jsonrpc-java-client:jar:1.6.0,
com.fasterxml.jackson.core:jackson-databind:jar:2.12.1,
org.jboss.resteasy:resteasy-jaxrs:jar:3.9.3.Final,
com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider:jar:2.12.1,
org.apache.httpcomponents:httpclient:jar:4.5.13: Could not find artifact
org.ovirt.engine.api:ovirt-engine-extensions-api:jar:1.0.2.SNAPSHOT ->
[Help 1]
Any recommendations on how to proceed?
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
1 year, 10 months
GitHub Actions-based CI for vdsm
by Marcin Sobczyk
Hi All,
I've been working on adding GitHub Actions-based CI to vdsm today.
Feel free to check out the patches here:
https://gerrit.ovirt.org/q/topic:%22github-actions-ci%22+(status:open%20O...
Some comments:
- the linters work fine already, we can start using them
- RPM building works too in general. I think the RPM versions are not
right yet, so I'll look into this. After the 'rpm' job is done we get a
zipfile with all the built RPMs inside. In the future we may want to run
'createrepo_c' on this dir as well, so we'll have a ready-to-be-used
repository in that zip.
- 'tests' are working too, but we have a couple of failures we'd need to
look at. This job, unlike the others, runs in GitHub's Ubuntu VM inside
which we use a privileged container for running the tests.
- didn't try 'tests-storage' yet
- Not to waist precious free CI minutes and storage, we run linters
first, tests after that, but only under the condition that the linters
didn't fail, and finally we build RPMs, but this time under the
condition that the tests didn't fail.
You can find some of the runs I made in my personal fork here:
https://github.com/tinez/vdsm/actions/workflows/ci.yml
Comments, remarks and reviews are highly appreciated.
Regards, Marcin
1 year, 10 months
