yum x dnf on el8 host installation?
by Milan Zamazal
Hi, when I experiment with installing a RHEL 8 host from Engine (master
branch running on RHEL 7), I get the following error in host deploy:
2019-06-25 12:59:48,701+0200 DEBUG otopi.plugins.otopi.network.firewalld firewalld._get_firewalld_cmd_version:116 firewalld version: 0.6.3
2019-06-25 12:59:48,701+0200 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%EventEnd STAGE customization METHOD otopi.plugins.otopi.network.firewalld.Plugin._customization (None)
2019-06-25 12:59:48,701+0200 DEBUG otopi.context context.dumpEnvironment:731 ENVIRONMENT DUMP - BEGIN
2019-06-25 12:59:48,702+0200 DEBUG otopi.context context.dumpEnvironment:741 ENV NETWORK/firewalldAvailable=bool:'True'
2019-06-25 12:59:48,702+0200 DEBUG otopi.context context.dumpEnvironment:745 ENVIRONMENT DUMP - END
2019-06-25 12:59:48,702+0200 DEBUG otopi.context context._executeMethod:127 Stage customization METHOD otopi.plugins.otopi.core.config.Plugin._customize1
2019-06-25 12:59:48,702+0200 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%EventStart STAGE customization METHOD otopi.plugins.otopi.core.config.Plugin._customize1 (None)
2019-06-25 12:59:48,703+0200 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%EventEnd STAGE customization METHOD otopi.plugins.otopi.core.config.Plugin._customize1 (None)
2019-06-25 12:59:48,703+0200 DEBUG otopi.context context._executeMethod:127 Stage customization METHOD otopi.plugins.ovirt_host_deploy.kdump.packages.Plugin._customization
2019-06-25 12:59:48,703+0200 DEBUG otopi.plugins.otopi.dialog.machine dialog.__logString:204 DIALOG:SEND **%EventStart STAGE customization METHOD otopi.plugins.ovirt_host_deploy.kdump.packages.Plugin._customization (None)
2019-06-25 12:59:48,704+0200 DEBUG otopi.context context._executeMethod:145 method exception
Traceback (most recent call last):
File "/tmp/ovirt-AX5hJa1Fcr/pythonlib/otopi/context.py", line 132, in _executeMethod
method['method']()
File "/tmp/ovirt-AX5hJa1Fcr/otopi-plugins/ovirt-host-deploy/kdump/packages.py", line 216, in _customization
self._kexec_tools_version_supported()
File "/tmp/ovirt-AX5hJa1Fcr/otopi-plugins/ovirt-host-deploy/kdump/packages.py", line 143, in _kexec_tools_version_supported
from rpmUtils.miscutils import compareEVR
ModuleNotFoundError: No module named 'rpmUtils'
2019-06-25 12:59:48,705+0200 ERROR otopi.context context._executeMethod:154 Failed to execute stage 'Environment customization': No module named 'rpmUtils'
It's apparently because `rpmUtils' module from `yum' package is no
longer present on RHEL 8 (in `yum' or another very easily guessable
package). I'm not sure how el7 x el8 host installation is supposed to
work and whether I can do anything at the moment to proceed a bit
further.
I suppose similar yum x dnf issues will need some attention; not only in
host deploy but everywhere where yum or rpm manipulation is used.
Thanks,
Milan
3 years, 1 month
Re: [CentOS-devel] The future of the community build services
by Sandro Bonazzola
Hi,
Il giorno lun 24 giu 2019 alle ore 17:21 Thomas Oulevey <
thomas.oulevey(a)cern.ch> ha scritto:
> Hi Folks,
>
> It's time to have a look to the SIGs and the community needs for the
> next version of the community build service(cbs). We would like to
> request feedback and know if the different communities plan on using
> modular builds, and what would be their timeline to be able to produce
> C8 artifacts (rpms, imagefactory builds, etc...).
>
From oVirt perspective we are not planning to build modules but we need to
see how advanced virtualization module will look like within CentOS 8.
We plan to consume some modules but not building one also for building in
cbs (we'll need at least javapackages-tools module in cbs build root)
>
> As you know Koji is now used to build CentOS 8 [1], and is based on
> the mbbox [2] distribution.
>
> It makes sense for cbs.centos.org to follow this trend and be based on
> the same templates.
>
> At the same time we needed to evaluate how and where we can deploy the
> new Openshift based templates, and associated builders for different
> arches.
>
> It's understood that the transition between both systems should be
> smooth and do not impact your C6/C7 builds and release cycle. We will
> plan accordingly.
>
> Please let us know, if you have comments and/or new ideas.
>
> --
> Thomas Oulevey
>
>
> [1]: https://blog.centos.org/2019/06/centos-8-status-17-june-2019/
> [2]: https://github.com/puiterwijk/mbbox
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel(a)centos.org
> https://lists.centos.org/mailman/listinfo/centos-devel
>
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>
3 years, 1 month
Fwd: [CentOS-devel] The future of the community build services
by Sandro Bonazzola
FYI
---------- Forwarded message ---------
Da: Thomas Oulevey <thomas.oulevey(a)cern.ch>
Date: lun 24 giu 2019 alle ore 17:21
Subject: [CentOS-devel] The future of the community build services
To: <centos-devel(a)centos.org>
Hi Folks,
It's time to have a look to the SIGs and the community needs for the
next version of the community build service(cbs). We would like to
request feedback and know if the different communities plan on using
modular builds, and what would be their timeline to be able to produce
C8 artifacts (rpms, imagefactory builds, etc...).
As you know Koji is now used to build CentOS 8 [1], and is based on
the mbbox [2] distribution.
It makes sense for cbs.centos.org to follow this trend and be based on
the same templates.
At the same time we needed to evaluate how and where we can deploy the
new Openshift based templates, and associated builders for different arches.
It's understood that the transition between both systems should be
smooth and do not impact your C6/C7 builds and release cycle. We will
plan accordingly.
Please let us know, if you have comments and/or new ideas.
--
Thomas Oulevey
[1]: https://blog.centos.org/2019/06/centos-8-status-17-june-2019/
[2]: https://github.com/puiterwijk/mbbox
_______________________________________________
CentOS-devel mailing list
CentOS-devel(a)centos.org
https://lists.centos.org/mailman/listinfo/centos-devel
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>
3 years, 1 month
Weakness of repos in OST
by Dominik Holler
Hi,
from my point of view, we are not testing the repos in OST,
because we manage the packages manually.
The clean way would be installing something like
https://resources.ovirt.org/pub/yum-repo/ovirt-release43-pre.rpm
But this would download each package multiple times each run.
Maybe a way to test the repos would be an OST which bypasses
lago's repo management.
What is your view on this?
Dominik
3 years, 1 month
[Ovirt] [CQ weekly status] [21-06-2019]
by Dafna Ron
This mail is to provide the current status of CQ and allow people to review
status before and after the weekend.
Please refer to below colour map for further information on the meaning of
the colours.
*CQ-4.2*: GREEN (#1)
Last failure was on 18-06 for project v2v-conversion-host due to failed
build-artifacts
which is already fixed by next merged patches.
*CQ-4.3*: RED (#1)
1. We have a failure on ovirt-engine-metrics due to a dependency to a new
ansible package that has not been synced yet to centos repo.
I am adding virt-sig-common repo until this is synced next week:
https://gerrit.ovirt.org/#/c/101023/
*CQ-Master:* RED (#1)
1. same failure on ovirt-engine-metrics as 4.3
2. ovirt-hosted-engine-setup is failing due to package dependency change
from python-libguestfs to python2-libguestfs. mail sent to Ido to check the
issue.
Current running jobs for 4.2 [1], 4.3 [2] and master [3] can be found
here:
[1]
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-...
[2]
https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.3_change...
[3]
http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chan...
Happy week!
Dafna
-------------------------------------------------------------------------------------------------------------------
COLOUR MAP
Green = job has been passing successfully
** green for more than 3 days may suggest we need a review of our test
coverage
1.
1-3 days GREEN (#1)
2.
4-7 days GREEN (#2)
3.
Over 7 days GREEN (#3)
Yellow = intermittent failures for different projects but no lasting or
current regressions
** intermittent would be a healthy project as we expect a number of
failures during the week
** I will not report any of the solved failures or regressions.
1.
Solved job failures YELLOW (#1)
2.
Solved regressions YELLOW (#2)
Red = job has been failing
** Active Failures. The colour will change based on the amount of time the
project/s has been broken. Only active regressions would be reported.
1.
1-3 days RED (#1)
2.
4-7 days RED (#2)
3.
Over 7 days RED (#3)
3 years, 1 month
review request: SDM update_volume API changes
by Germano Veit Michel
Hello,
Could you please review and comment on the following patch series below?
https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic...
These are required by future tools to make fixing image chains safer and
easier.
This has been previously submitted as part of a larger set of patches,
which were not accepted mostly due to a ResourceManager Exception
workaround (force flag). The series above removes that workaround and also
improves the tests.
I'm only submitting the API changes at this time. If you want to have an
idea on what this will be used for, please see now abandoned
https://gerrit.ovirt.org/#/c/94105/ (it will get updated and resubmitted
once and if these API changes are accepted)
Thanks,
Germano
3 years, 1 month
