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 year, 3 months
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.*
2 years, 11 months
jenkins failures on corrupted rpmdb within mock chroot
by Sandro Bonazzola
Hi,
I started getting
Running transaction check
Error: transaction check vs depsolve:
/bin/sh is needed by ovirt-openvswitch-2.15-2.el8.noarch
bash is needed by ovirt-openvswitch-2.15-2.el8.noarch
systemd is needed by ovirt-openvswitch-2.15-2.el8.noarch
To diagnose the problem, try running: 'rpm -Va --nofiles --nodigest'.
You probably have corrupted RPMDB, running 'rpm --rebuilddb' might fix
the issue.
In a few occasions already. Did anyone else hit this?
--
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.*
3 years
VDSM build failure: unsupported pickle protocol: 5
by Sandro Bonazzola
hi,
I'm trying to enable copr builds for vdsm (
https://gerrit.ovirt.org/c/vdsm/+/117368 )
And it's currently failing to rebuild src.rpm (generated on Fedora 34) for
el8 with the following error:
(
https://download.copr.fedorainfracloud.org/results/ovirt/ovirt-master-sna...
)
make[2]: Entering directory '/builddir/build/BUILD/vdsm-4.50.0.1/lib/vdsm'
Making all in api
make[3]: Entering directory '/builddir/build/BUILD/vdsm-4.50.0.1/lib/vdsm/api'
Generate vdsm-api.html
chmod u+w .
PYTHONPATH=./../../:./../../vdsm \
./schema_to_html.py vdsm-api ./vdsm-api.html
Traceback (most recent call last):
File "./schema_to_html.py", line 250, in <module>
main()
File "./schema_to_html.py", line 245, in main
api_schema = vdsmapi.Schema((schema_type,), strict_mode=False)
File "/builddir/build/BUILD/vdsm-4.50.0.1/lib/vdsm/api/vdsmapi.py",
line 145, in __init__
loaded_schema = pickle.loads(f.read())
ValueError: unsupported pickle protocol: 5
make[3]: *** [Makefile:697: vdsm-api.html] Error 1
make[3]: Leaving directory '/builddir/build/BUILD/vdsm-4.50.0.1/lib/vdsm/api'
make[2]: *** [Makefile:644: all-recursive] Error 1
make[2]: Leaving directory '/builddir/build/BUILD/vdsm-4.50.0.1/lib/vdsm'
make[1]: *** [Makefile:466: all-recursive] Error 1
make[1]: Leaving directory '/builddir/build/BUILD/vdsm-4.50.0.1/lib'
make: *** [Makefile:539: all-recursive] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.nDfLzv (%build)
Sounds like the make dist process ran on Fedora 34 brings a source
file used at build time on el8 in a cpickle format which is not
backward compatible.
Seems to be a bug, the cpickle shouldn't be included in the tar.gz, it
should be generated at build time.
Comments?
--
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.*
3 years
Re: Java Xmx limit building ovirt-engine package
by Sandro Bonazzola
+Martin Perina <mperina(a)redhat.com> , +Artur Socha <asocha(a)redhat.com> ?
Il giorno mar 26 ott 2021 alle ore 17:01 Marcos Sungaila <
marcos.sungaila(a)oracle.com> ha scritto:
> Hello,
>
>
>
> I’m facing a weird behave when rebuilding the ovirt-engine rpm package.
>
> When I run a rpmbuild -ba ovirt-engine.spec, it fails with the following
> error:
>
>
>
> [ERROR] Out of memory; to increase the amount of memory
>
> Also, it indicates the option -Xmx8192M in the pom.xml file.
>
> The weird part is that building the application in the command line works
> fine but not in the rpmbuild, neither using a mock build system.
>
> I checked this page https://github.com/oVirt/ovirt-engine from GitHub and
> tested those variables with no success.
>
>
>
> Can anyone point me where I can find how to use those variables when
> building the package or have experience building this package/application
> to explain it?
>
>
>
> Thank you in advance for any help.
>
>
>
> Regards,
>
> Marcos
>
>
> _______________________________________________
> Devel mailing list -- devel(a)ovirt.org
> To unsubscribe send an email to devel-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/DNRP3JCD6VE...
>
--
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.*
3 years
