New Lago release - 0.28.0
by Gal Ben Haim
Hi Everyone!
There's a new Lago release with version 0.28.0 ready for you to upgrade!
Key Changes:
1. We are now formatting our code with 'yapf' 0.14.0.
For all our contributors, please update 'yapf' if needed.
2. When running 'lago shell' it's possible to specify only the suffix
of the vm's name and lago will resolve the full name.
3. We removed some unused code from lago-ovirt plugin.
Docs - http://lago.readthedocs.io/en/0.28/
Repo - http://resources.ovirt.org/repos/lago/stable/0.0/rpm/
Here are the changes:
* Thu Nov 24 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.28.0
ee15dfbb: Merge pull request #356 from lago-project/pkg_resources_exception
81152cd7: Fixed exception handling when checking for deps
* Thu Nov 24 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.27.5
ab5aa8a6: Merge pull request #366 from mykaul/skip_freeze
397321e5: Switch to optionall freeze the FS before logs extraction.
5fe33adb: Merge branch 'master' into skip_freeze
* Wed Nov 23 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.27.4
c577b8d7: Merge pull request #365 from mykaul/guess_host_name_in_shell
d90f2b50: For ease of use, connect to a host even if only the suffix is
given.
* Tue Nov 22 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.27.3
cb48ad59: Merge pull request #367 from nvgoldin/update_yapf
d891034b: Bump yapf version 0.7.1 -> 0.14.0
* Sat Nov 12 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.27.2
fa588e4f: Merge pull request #360 from nvgoldin/ovirtlago_cleanup_i
a1bf8dc6: [ost-plugin] cleanup unused commands
* Wed Nov 09 2016 Lago CI bot <dcaroest+cibot(a)redhat.com> - 0.27.1
290c49a3: Merge pull request #361 from nvgoldin/tests_generate_config
587eba28: Add 'generate-config' verb to functional tests list
Gal Ben Haim
gbenhaim(a)redhat.com
RHEV DevOps
7 years, 5 months
yapf and flake8 are running against each other - and my patch is in the middle.
by Yaniv Kaul
Seems like there's a disagreement between yapf and flake on styling.
See
http://jenkins.ovirt.org/job/lago_master_check-patch-el7-x86_64/362/console
and
http://jenkins.ovirt.org/job/lago_master_check-patch-el7-x86_64/361/console
:
*7:24:57* scripts/check_style.sh*07:24:57* yapf 0.7.1*07:25:59* ---
lago/templates.py (original)*07:25:59* +++
lago/templates.py (reformatted)*07:25:59* @@ -260,7 +260,6
@@*07:25:59* finally:*07:25:59*
response.close()*07:25:59* *07:25:59* -*07:25:59* #: Registry for
template providers*07:25:59* _PROVIDERS = {*07:25:59* 'file':
FileSystemTemplateProvider,*07:25:59* Yapf failed, make sure to
run:*07:25:59* yapf --style .style.yapf --in-place --recursive .
vs.
*07:13:48* PYTHONPATH=/home/jenkins/workspace/lago_master_check-patch-el7-x86_64/lago
python /home/jenkins/workspace/lago_master_check-patch-el7-x86_64/lago/tests/venv/bin/flake8*07:13:52*
./lago/templates.py:264:1: E305 expected 2 blank lines after class or
function definition, found 1*07:13:52* make: *** [check-local] Error 1
Come on... I just want my patch in, it has nothing to do with this
supposed breakage.
Y.
7 years, 5 months
Help debugging HC test failures
by Sahina Bose
Hi,
I need some help/pointers to solve the issues I'm running into while
running the gluster HC tests - https://gerrit.ovirt.org/57283
1. Once I run the suite, initialization completes successfully, but further
tests fail. Engine is running as per "hosted-engine --vm-status" on the
first host (lago_basic_suite_hc_host0) and I can ping the engine from the
host running the test
File "/usr/lib/python2.7/site-packages/ovirtlago/virt.py", line 189, in
get_api
return self.get_api_v3()
File "/usr/lib/python2.7/site-packages/ovirtlago/virt.py", line 195, in
get_api_v3
self._api_v3 = self._get_api(api_ver=3)
File "/usr/lib/python2.7/site-packages/ovirtlago/virt.py", line 180, in
_get_api
raise RuntimeError('Failed to connect to the engine')
RuntimeError: Failed to connect to the engine
Which logs should I look at to debug this issue?
2. Cannot access the web url of engine:
I've setup tunnelling: ssh -L
hc-engine.lago.local:8443:hc-engine.lago.local:443
root(a)rhsdev-grafton1.lab.eng.blr.redhat.com
But continue getting the error:
The client is not authorized to request an authorization. It's required to
access the system using FQDN.
3. Once the vms are left running for a while, connectivity is lost between
the vms and cannot connect to some of the VMs via lago shell .
[root@lago_basic_suite_hc_host0 ~]# ping lago_basic_suite_hc_host1
PING lago_basic_suite_hc_host1 (192.168.200.2) 56(84) bytes of data.
>From lago-basic-suite-hc-host0.lago.local (192.168.200.3) icmp_seq=1
Destination Host Unreachable
Looks like issue with network in VM from console of VM
deployment-basic_suite_hc]# virsh console
a2051d60-lago_basic_suite_hc_host1
Connected to domain a2051d60-lago_basic_suite_hc_host1
[root@lago_basic_suite_hc_host1 ~]# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP qlen 1000
link/ether 54:52:c0:a8:c8:02 brd ff:ff:ff:ff:ff:ff
inet6 fe80::5652:c0ff:fea8:c802/64 scope link
valid_lft forever preferred_lft forever
Any pointers are much appreciated.
thanks
sahina
7 years, 5 months
New Lago release - 0.27
by Nadav Goldin
Hey all,
New Lago version is out - v0.27, included in this release: fixes for a
few bugs, improvements to the 'ovirt' verb, packaging fixes and some
new docs. Also, a new verb was added: 'generate-config'[1], this verb
allows to print the current loaded configuration lago is using. It
also introduced a few changes to lago.conf file, so if you are using
/etc/lago.d/lago.conf, please make sure you read[1] before upgrading.
Specifically these parameters were changed in lago.conf:
1. 'default_ssh_user', changed to: 'ssh_user', no change to the default value.
2. 'default_ssh_password, changed to: 'ssh_password', no change to the
default value.
3. 'template_default_repo', changed to: 'template_repo_name'(same as
the existing CLI), no change to value.
4. 'template_*' parameters were moved under the [init] section in lago.conf.
5. lago.conf default location changed to /etc/lago/lago.conf(when
upgrading via yum or dnf, it will be automatically be installed there)
To upgrade using yum/dnf simply run:
yum update lago
If you find any bugs, or have request for new features please feel
free to open an issue in the GitHub page[2]. Also we started working
with GitHub's integrated Kanban board[3].
The updated docs can be found here[4], and the full change log here[5].
Thanks everyone who contributed to this release!
Enjoy,
Nadav.
[1] http://lago.readthedocs.io/en/0.27/Configuration.html
[2] https://github.com/lago-project/lago/issues
[3] https://github.com/lago-project/lago/projects/1
[4] https://lago.readthedocs.org
[5] https://github.com/lago-project/lago/milestone/2?closed=1
7 years, 6 months