ovirt tests failing on missing libxml2-python
by Eyal Edri
2016-06-24 17:28:17,843 DEBUG [org.ovirt.otopi.dialog.MachineDialogParser]
(VdsDeploy) [796140d9] Got: ***L:ERROR Failed to execute stage 'Package
installation': [u'libxml2-python-2.9.1-6.el7_2.3.x86_64 requires libxml2 =
2.9.1-6.el7_2.3']
2016-06-24 17:28:17,844 DEBUG [org.ovirt.otopi.dialog.MachineDialogParser]
(VdsDeploy) [796140d9] nextEvent: Log ERROR Failed to execute stage
'Package installation': [u'libxml2-python-2.9.1-6.el7_2.3.x86_64 requires
libxml2 = 2.9.1-6.el7_2.3']
2016-06-24 17:28:17,860 ERROR
This is failing 3.6,4.0 and master tests, anyone knows on a recent
dependency change in vdsm or other host level pkg?
--
Eyal Edri
Associate Manager
RHEV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
8 years, 12 months
Latest ovirt-system-tests doesn't perform reposync?
by Yaniv Kaul
I'm still running on Lago 0.18 (can't upgrade due to F24 bug deps with
repoman), and when I switched to the latest ovirt-system-tests, something's
not sync'ing the repos correctly:
Good run (from the old ovirt-system-tests):
2016-06-22 14:52:53,770::log_utils.py::__exit__::593::ovirtlago::INFO::
* Running reposync: ESC[32mSuccessESC[0m (in 0:00:06)
2016-06-22 14:52:53,770::log_utils.py::__exit__::593::ovirtlago::INFO:: #
Syncing remote repos locally (this might take some time):
ESC[32mSuccessESC[0m (in 0:00:06)
2016-06-22
14:52:53,771::log_utils.py::__enter__::586::ovirtlago.merge_repos::INFO::
# [Thread-1] Processing directory
/var/lib/lago/reposync/ovirt-master-snapshot-el7: ESC[0mESC[0m
2016-06-22
14:52:53,771::log_utils.py::__enter__::586::lago.utils::DEBUG::start task
Run command: "find" "/var/lib/lago/reposync/ovirt-master-snapshot-el7"
"-type" "f" "-size" "+0" "-name" "*.rpm"
2016-06-22
14:52:53,775::utils.py::_run_command::178::lago.utils::DEBUG::command exit
with 0
...
Bad run (from the latest ovirt-system-tests):
2016-06-22 15:17:19,728::log_utils.py::__exit__::593::ovirtlago::INFO::
* Running reposync: ESC[32mSuccessESC[0m (in 0:00:09)
2016-06-22 15:17:19,728::log_utils.py::__exit__::593::ovirtlago::INFO:: #
Syncing remote repos locally (this might take some time):
ESC[32mSuccessESC[0m (in 0:00:09)
2016-06-22 15:17:19,728::log_utils.py::__enter__::586::lago.virt::INFO:: #
Save prefix: ESC[0mESC[0m
Any ideas?
TIA,
Y.
9 years
[17-06-2016] New lago release - 0.22.0
by Gal Ben Haim
Hi everyone!
There's a new lago release with version 0.22.0 ready for you to upgrade!
Docs - http://lago.readthedocs.io/en/0.22/Env_Setup.html
Repo - http://resources.ovirt.org/repos/lago/stable/0.0/rpm/
Here are the changes:
* Thu Jun 16 2016 gbenhaim <galbh2(a)gmail.com> - 0.22.1
20cc8d58: Fixed a bug where script manager stuck on an infinite loop.
* Thu Jun 16 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.22.0
ed677d6b: Merge pull request #280 from
lago-project/hide_import_error_when_using_old_versions_of_stevedore
be794dc1: Hide import error when using old versions of stevedore.
Enjoy!
Gal Ben Haim
gbenhaim(a)redhat.com
RHEV DevOps
9 years
Lago Ansible Inventory Script
by Eric Helms
Howdy,
Since I didn't find anything searching around, I decided to start
implementing a dynamic inventory script for Lago for my local environment
while trying to keep it as generic as possible. If you'd be interested I'd
like to share it and get feedback but I am not sure where is the best place
for me to place it or offer it to Lago via a PR.
Eric
9 years
[09-06-2016] New lago release - 0.21.0
by Gal Ben Haim
Hi everyone!
There's a new lago release with version 0.21.0 ready for you to upgrade!
Here are the changes:
* Thu Jun 02 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.21.0
f28ea953: Merge pull request #272 from
lago-project/show_plugin_import_exception_only_in_debug_level
6336d527: Added a callback function to handle import exception
Enjoy!
Gal Ben Haim
gbenhaim(a)redhat.com
RHEV DevOps
9 years
[Request for feedback] Adding [Docker] container support to Lago
by Jan Lieskovsky
Hello folks,
since there's motivation Lago to support containers too
(https://github.com/lago-project/lago/issues/149) investigated
the possible ways how this could be implemented.
Created a WIP PR:
[1] https://github.com/lago-project/lago/pull/276
but would appreciate a wider feedback from the list prior continuing on that one.
Basically I see three possibilities how [Docker] container support for
Lago could be implemented:
Approach 1)
- Allow Lago container yaml / json init file in "docker-compose.yml" format
- Use available "docker-compose" rpm to perform the underlying actions (IOW
lago commands would be just wrappers around docker-compose use. E.g.
lago start == docker-compose up
lago stop == docker-compose down)
As a part of this I have added "prefix-provider" support to lago (first commit
of [1]). The intention is to define new docker-prefix for lago, which would
wrap use of docker-compose,
Advantage: Should be easy to implement
Disadvantage: Dependency on external docker-compose RPM, which at the moment
in F22 doesn't support v2 of docker-compose YAML files yet
Approach 2)
- allow "docker-compose.yml" as init json/yaml file for lago container configuration,
- instead of using "docker-compose" create own docker lago vm provider / plugin (using
python-docker-py implementation to access docker service),
As part of this I have implemented support for local docker container based provider
into Lago (commit 2 of [1]).
Advantage: No dependency on external docker-compose RPM
Disadvantate: * The need to write own docker-compose.yml file parser (AFAIK
python-dockerfile-parse doesn't support parsing them [yet)
* Basically we would duplicate the effort the docker-compose tool
is doing right now
Approach 3)
- don't allow docker-compose.yml as Lago container json/yml file,
- use rather format instead
Advantage: No need for docker-compose.yml parser. We can define custom format,
easily to be parsable.
Disadvantage: Divergence from commonly used docker-compose.yml files (UX would
differ as users would need to get accustomed to different format of
configuration file)
The question is obvious -- can you hopefully provide comments / opinion, which
approach of the above do you like best and why? If having yet another one from
the above ones, please share.
Thank you for your opinions in advance.
Regards, Jan
--
Jan iankko Lieskovsky
P.S.: Having agreed on an approach how this should be implemented will help us
with adding vagrant support to lago too.
9 years
[02-06-2016] New lago release - 0.20.0
by David Caro
Hi everyone! There's a new lago release with version 0.20.0 ready for you to upgrade!
One important change is the ability to use repoman for building the local repo,
It also means that repoman is now required when installing python-lago-ovirt,
repoman can be found in the following repo:
http://resources.ovirt.org/repos/ci-tools/
Here are the other changes:
745e6087: Added possibility to specify ssh-user and ssh-pass on initfile
99e99b75: Detect (and report) any empty domain name possibly
c7966a35: Using repoman to merge the reposync downloaded repos
7894c1d4: Added --custom-source option to reposetup
5c5199e9: Allow copying dirs in the vm
For the full changelog, you can go to the docs page:
http://lago.readthedocs.io/en/0.20/
Enjoy!
--
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605
Email: dcaro(a)redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605
9 years, 1 month
