[Ovirt] [CQ weekly status] [23-11-2018]
by Dafna Ron
Hi,
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 ovirt-4.2 - YELLOW (#1)
e
CQ ovirt-Master - RED (#1)
- *Project failing* - ovirt-engine
- *First job reported*:
https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11267
- *root cause*: https://gerrit.ovirt.org/#/c/95169/ ansible: Remove
duplication of vnc_tls option
- *Revert for change*: https://gerrit.ovirt.org/95666
- Tomasz Baranski is working on testing and fixing the change.
There is a long queue of changes waiting to be tested and the revert patch
is in queue.
Once revert is tested the jobs for ovirt-engine, unless any other
regressions were introduced, project should start to pass.
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)
6 years
vdsm-client: Adding a new verb to vdsm
by Kaustav Majumder
Hi all,
I was working on adding a new verb to vdsm-gluster [1]. But right now the
only way i see to test this is by using vdsm-client.I have patched a host
running vdsm with my code, but the vdsm-client is not showing the required
verb. Is there anything else needed to be done?
Eg-vdsm-client --gluster-enabled GlusterVolume globalOptionsList
[1] https://gerrit.ovirt.org/#/c/95636/
Thanks,
Kaustav
6 years
[ OST Failure Report ] [ oVirt Master (ovirt-engone) ] [ 21-11-2018 ] [ check_update_host ]
by Dafna Ron
Hi,
We have a failure in ovirt-master in basic suite for test
check_update_host.
Link and headline of suspected patches:
ansible: Remove duplication of vnc_tls option -
https://gerrit.ovirt.org/#/c/95169/
Link to Job:
https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11267
Link to all logs:
https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11267/arti...
(Relevant) error snippet from the log:
<error>
[dron@dron post-002_bootstrap.py]$ egrep
89d99b74-fa6c-4d1d-a261-fb7ca7fcada2
lago-basic-suite-master-engine/_var_log/ovirt-engine/engine.log
2018-11-21 13:41:34,209-05 DEBUG
[org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
(default task-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] method: get,
params: [ad768a3b-d44b-4fd4-b57a-9029fca470a0], timeElapsed: 9ms
2018-11-21 13:41:34,224-05 INFO
[org.ovirt.engine.core.bll.hostdeploy.HostUpgradeCheckCommand] (default
task-1) [89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Running command:
HostUpgradeCheckCommand internal: false. Entities affected : ID:
ad768a3b-d44b-4fd4-b57a-9029fca470a0 Type: VDSAction group
EDIT_HOST_CONFIGURATION with role type ADMIN
2018-11-21 13:41:34,259-05 DEBUG
[org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] method: get, params:
[ad768a3b-d44b-4fd4-b57a-9029fca470a0], timeElapsed: 13ms
2018-11-21 13:41:34,273-05 INFO
[org.ovirt.engine.core.bll.hostdeploy.HostUpgradeCheckInternalCommand]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Running command:
HostUpgradeCheckInternalCommand internal: true. Entities affected : ID:
ad768a3b-d44b-4fd4-b57a-9029fca470a0 Type: VDS
2018-11-21 13:41:34,277-05 DEBUG
[org.ovirt.engine.core.common.di.interceptor.DebugLoggingInterceptor]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] method: get, params:
[ad768a3b-d44b-4fd4-b57a-9029fca470a0], timeElapsed: 4ms
2018-11-21 13:41:34,281-05 DEBUG
[org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Inventory hosts:
[lago-basic-suite-master-host-0]
2018-11-21 13:41:34,282-05 INFO
[org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Executing Ansible command:
ANSIBLE_STDOUT_CALLBACK=hostupgradeplugin [/usr/bin/ansible-playbook,
--ssh-common-args=-F /var/lib/ovirt-engine/.ssh/config, --check,
--private-key=/etc/pki/ovirt-engine/keys/engine_id_rsa,
--inventory=/tmp/ansible-inventory2326258642232337463,
/usr/share/ovirt-engine/playbooks/ovirt-host-upgrade.yml] [Logfile: null]
2018-11-21 13:41:37,610-05 INFO
[org.ovirt.engine.core.common.utils.ansible.AnsibleExecutor]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Ansible playbook command has exited
with value: 2
2018-11-21 13:41:37,611-05 ERROR
[org.ovirt.engine.core.bll.host.HostUpgradeManager]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Failed to run check-update of host
'lago-basic-suite-master-host-0'.
2018-11-21 13:41:37,611-05 ERROR
[org.ovirt.engine.core.bll.hostdeploy.HostUpdatesChecker]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] Failed to check if updates are
available for host 'lago-basic-suite-master-host-0' with error message
'Failed to run check-update of host 'lago-basic-suite-master-host-0'.'
2018-11-21 13:41:37,616-05 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-commandCoordinator-Thread-1)
[89d99b74-fa6c-4d1d-a261-fb7ca7fcada2] EVENT_ID:
HOST_AVAILABLE_UPDATES_FAILED(839), Failed to check for available updates
on host lago-basic-suite-master-host-0 with message 'Failed to run
check-update of host 'lago-basic-suite-master-host-0'.'.
[dron@dron post-002_bootstrap.py]$
</error>
6 years
Fwd: [ovirt-users] FOSDEM‘19 Virtualization & IaaS Devroom CfP
by Piotr Kliczewski
A friendly reminder that Cfp is due by 1st of December.
Please submit your proposal using:
https://penta.fosdem.org/submission/FOSDEM19
---------- Forwarded message ---------
From: Piotr Kliczewski <pkliczew(a)redhat.com>
Date: Tue, Oct 16, 2018 at 9:32 AM
Subject: [ovirt-users] FOSDEM‘19 Virtualization & IaaS Devroom CfP
To: users <users(a)ovirt.org>
Cc: Doron Fediuck <doron(a)redhat.com>
We are excited to announce that the
call for proposals is now open for the Virtualization & IaaS devroom at the
upcoming FOSDEM 2019, to be hosted on February 2nd 2019.
This year will mark FOSDEM’s 19th anniversary as one of the longest-running
free and open source software developer events, attracting thousands of
developers and users from all over the world. FOSDEM will be held once
again in Brussels, Belgium, on February 2nd & 3rd, 2019.
This devroom is a collaborative effort, and is organized by dedicated folks
from projects such as OpenStack, Xen Project, oVirt, QEMU, KVM, and
Foreman. We would like to invite all those who are involved in these fields
to submit your proposals by December 1st, 2018.
About the Devroom
The Virtualization & IaaS devroom will feature session topics such as open
source hypervisors and virtual machine managers such as Xen Project, KVM,
bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as
KubeVirt,
Apache CloudStack, OpenStack, oVirt, QEMU and OpenNebula.
This devroom will host presentations that focus on topics of shared
interest, such as KVM; libvirt; shared storage; virtualized networking;
cloud security; clustering and high availability; interfacing with multiple
hypervisors; hyperconverged deployments; and scaling across hundreds or
thousands of servers.
Presentations in this devroom will be aimed at developers working on these
platforms who are looking to collaborate and improve shared infrastructure
or solve common problems. We seek topics that encourage dialog between
projects and continued work post-FOSDEM.
Important Dates
Submission deadline: 1 December 2019
Acceptance notifications: 14 December 2019
Final schedule announcement: 21 December 2019
Devroom: 2nd February 2019
Submit Your Proposal
All submissions must be made via the Pentabarf event planning site[1]. If
you have not used Pentabarf before, you will need to create an account. If
you submitted proposals for FOSDEM in previous years, you can use your
existing account.
After creating the account, select Create Event to start the submission
process. Make sure to select Virtualization and IaaS devroom from the Track
list. Please fill out all the required fields, and provide a meaningful
abstract and description of your proposed session.
Submission Guidelines
We expect more proposals than we can possibly accept, so it is vitally
important that you submit your proposal on or before the deadline. Late
submissions are unlikely to be considered.
All presentation slots are 30 minutes, with 20 minutes planned for
presentations, and 10 minutes for Q&A.
All presentations will be recorded and made available under Creative
Commons licenses. In the Submission notes field, please indicate that you
agree that your presentation will be licensed under the CC-By-SA-4.0 or
CC-By-4.0 license and that you agree to have your presentation recorded.
For example:
"If my presentation is accepted for FOSDEM, I hereby agree to license all
recordings, slides, and other associated materials under the Creative
Commons Attribution Share-Alike 4.0 International License. Sincerely,
<NAME>."
In the Submission notes field, please also confirm that if your talk is
accepted, you will be able to attend FOSDEM and deliver your presentation.
We will not consider proposals from prospective speakers who are unsure
whether they will be able to secure funds for travel and lodging to attend
FOSDEM. (Sadly, we are not able to offer travel funding for prospective
speakers.)
Speaker Mentoring Program
As a part of the rising efforts to grow our communities and encourage a
diverse and inclusive conference ecosystem, we're happy to announce that
we'll be offering mentoring for new speakers. Our mentors can help you with
tasks such as reviewing your abstract, reviewing your presentation outline
or slides, or practicing your talk with you.
You may apply to the mentoring program as a newcomer speaker if you:
Never presented before or
Presented only lightning talks or
Presented full-length talks at small meetups (<50 ppl)
Submission Guidelines
Mentored presentations will have 25-minute slots, where 20 minutes will
include the presentation and 5 minutes will be reserved for questions.
The number of newcomer session slots is limited, so we will probably not be
able to accept all applications.
You must submit your talk and abstract to apply for the mentoring program,
our mentors are volunteering their time and will happily provide feedback
but won't write your presentation for you!
If you are experiencing problems with Pentabarf, the proposal submission
interface, or have other questions, you can email our devroom mailing
list[2] and we will try to help you.
How to Apply
In addition to agreeing to video recording and confirming that you can
attend FOSDEM in case your session is accepted, please write "speaker
mentoring program application" in the "Submission notes" field, and list
any prior speaking experience or other relevant information for your
application.
Call for Mentors
Interested in mentoring newcomer speakers? We'd love to have your help!
Please email iaas-virt-devroom at lists.fosdem.org with a short speaker
biography and any specific fields of expertise (for example, KVM,
OpenStack, storage, etc.) so that we can match you with a newcomer speaker
from a similar field. Estimated time investment can be as low as a 5-10
hours in total, usually distributed weekly or bi-weekly.
Never mentored a newcomer speaker but interested to try? As the mentoring
program coordinator, email Brian Proffitt[3] and he will be happy to answer
your questions!
Code of Conduct
Following the release of the updated code of conduct for FOSDEM, we'd like
to remind all speakers and attendees that all of the presentations and
discussions in our devroom are held under the guidelines set in the CoC and
we expect attendees, speakers, and volunteers to follow the CoC at all
times.
If you submit a proposal and it is accepted, you will be required to
confirm that you accept the FOSDEM CoC. If you have any questions about the
CoC or wish to have one of the devroom organizers review your presentation
slides or any other content for CoC compliance, please email us and we will
do our best to assist you.
Call for Volunteers
We are also looking for volunteers to help run the devroom. We need
assistance watching time for the speakers, and helping with video for the
devroom. Please contact Brian Proffitt, for more information.
Questions?
If you have any questions about this devroom, please send your questions to
our devroom mailing list. You can also subscribe to the list to receive
updates about important dates, session announcements, and to connect with
other attendees.
See you all at FOSDEM!
[1] <https://penta.fosdem.org/submission/FOSDEM17>
https://penta.fosdem.org/submission/FOSDEM19
[2] iaas-virt-devroom at lists.fosdem.org
<https://lists.fosdem.org/listinfo/fosdem>
[3] bkp at redhat.com <https://lists.fosdem.org/listinfo/fosdem>
6 years
[ACTION REQUIRED] Compose for oVirt 4.3.0 beta (alpha?)
by Sandro Bonazzola
Hi,
I started preparing repository for beta (or alpha if beta release criteria
are not satisfied)
Please add the builds you want included in the release configuration files.
I already started filling the configuration files, if your package is
already there, please check if the versions and the shipped builds are
correct and fix if not.
Reference gerrit project is:
https://gerrit.ovirt.org/#/admin/projects/releng-tools
for release notes automatic generation: milestones/ovirt-4.3.0.conf
for adding builds to the repository: releases/ovirt-4.3.0_beta1.conf
documentation: releases/README-prepare-patches
Thanks,
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://red.ht/sig>
6 years
Fwd: Error Message in basic-suite-master: segmentation fault during host-deply
by Galit Rosenthal
Hi,
I have a problem with basic-suite-master with host deploy
Who can help solve this issue?
Thanks,
Galit
check patch [3] is failing on :
Basic suite master fails when using packages from new repository used, it
might be related to the new 7.6 packages[1]:
Error Message:
2018-11-21 08:20:52,005-05 ERROR
[org.ovirt.engine.core.uutils.ssh.SSHDialog]
(EE-ManagedThreadFactory-engine-Thread-2) [b85560f] SSH error running
command root@lago-basic-suite-master-host-1:'umask 0077;
MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t ovirt-XXXXXXXXXX)"; trap
"chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm -fr \"${MYTMP}\" >
/dev/null 2>&1" 0; tar --warning=no-timestamp -C "${MYTMP}" -x &&
"${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine
DIALOG/customization=bool:True': RuntimeException: Unexpected error during
execution: bash: line 1: 1374 Segmentation fault
"${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine
DIALOG/customization=bool:True
Host Deploy fails on segmentation fault [2]:
[1] http://mirror.centos.org/centos/7/cr/x86_64/
[2]
https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/233...
[3] gerrit: https://gerrit.ovirt.org/#/c/95570/
--
GALIT ROSENTHAL
SOFTWARE ENGINEER
Red Hat
<https://www.redhat.com/>
galit(a)gmail.com T: 972-9-7692230
<https://red.ht/sig>
6 years
screenshots for all UI patches / UXD reviewer update
by Greg Sheremeta
Hi all,
Just as a refresher and for anyone new -- please be sure to add screenshots
of your admin portal patches to your gerrit commit in the form of an
imgur.com link in the commit message.
Additionally, Laura Wright is now handling most of our UI look and feel
review duties. She is quickly becoming an oVirt UI expert :) so please
continue to add her on your UI patches so she can +1 the designs. It's
especially important to have her review English strings, too. So if you
were previously adding Liz Blanchard (Liz is still around but focusing on
kubevirt), you can now add Laura instead. Generally, maintainers should
avoid merging patches that touch the UI until Laura has +1'd.
Please let me know if you have any questions!
Best wishes,
Greg
--
GREG SHEREMETA
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
<https://www.redhat.com/>
gshereme(a)redhat.com IRC: gshereme
<https://red.ht/sig>
6 years
