Jenkins is back up. Please resume business as usual...
- Original Message -
From: Barak Korren bkor...@redhat.com
To: infra in...@ovirt.org
Cc: Eyal Edri ee...@redhat.com, devel@ovirt.org
Sent: Monday, June 29, 2015 10:39:16 AM
Subject: Re: fyi - outage in jenkins.ovirt.org
___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
On 9 November 2015 at 10:35, David Caro <dc...@redhat.com> wrote:
> On 11/09, Barak Korren wrote:
>> On 9 November 2015 at 00:27, David Caro <dc...@redhat.com> wrote:
>> > On 11/08, Barak Korren wrote:
>> >> If all jobs are using mock already, maybe we s
On 9 November 2015 at 00:27, David Caro <dc...@redhat.com> wrote:
> On 11/08, Barak Korren wrote:
>> If all jobs are using mock already, maybe we should drop all Fedora
>> slaves to have less frequent upgrade cycles?
>
> Not all the jobs are mocked, and there's some
ilman/listinfo/devel
>
>
>
>
> --
> Eyal Edri
> Supervisor, RHEV CI
> EMEA ENG Virtualization R
> Red Hat Israel
>
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>
> ___
> Infra mailing li
dic jobs.
3. Send a YAML patch to create a new stand-alone job. (That,
experience shows, would result in that job being unmaintained)
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
prove the CI standard so
that a certain artefact file gets posted on the Jenkis results page.
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
ich code is touched when performing some flow manually.
>
Is it possible to have this applied to automatic flows as well? Maybe
running on check_merged.sh for the tests running in Lago?
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailin
ied to add the 'workflow' flag for that at some point (It is used
by most infra projects), but it was not accepted with any enthusiasm
by the devs, you can search back the discussion on 'devel'.
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
you can place any HTML in 'index.html' including result
tables, graphs, etc.
Note that everything above is subject to change, final details will be
determined only when we start having patches that try to implement
this.
--
Barak Korren
bkor...@redhat.com
the makefile dynamically generate the
changelog form the tags)?
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
bug.cgi?id=1291753
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
The oVirt Jenkins server seems to have gone into a particularly long
garbage collection process, so I just restarted it 10 minutes ago to
make it responsive again.
If you had jobs running at that time they will never finish, or finish
with failure, please restart them.
--
Barak Korren
bkor
master_check-patch" job, not this one.
If this job's functionality is indeed already covered by check_patch,
then I vote for it to be removed.
VDSM maintainers, please confirm.
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel maili
> Please remove it - unless you have plans to revert the
> automation/*-based approach.
Since I don't know who wrote it, and what useful bits of code may be
hiding inside, I rather not make any irreversible changes while almost
everyone is on PTO.
--
Barak Korren
bkor...@redhat.com
R
>> I don't know what are the other jobs and what they are doing.
>> Better remove them since nobody care about them anyway.
>
> ack
>
...
>> Nir
>
> Yaniv Bronhaim.
Job disabled for now.
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
rg
> http://lists.ovirt.org/mailman/listinfo/devel
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
ation sequences we were unable to
> provide using the previous implementation.
>
> Regards,
> Alon Bar-Lev.
>
> [1] http://www.ovirt.org/Features/UniformSSOSupport
> ___
> Devel mailing list
> Devel@ovirt.org
> http
the user to enable/disable
> GUI elements in the userportal as required.
>
I would go with solution C which seems to me the most generally useful...
>
> 3) Ability to specify sets of VM templates which can be created as new VMs
> together
>
In conjunction with my proposal for featur
t some point it was thought that oVirt
would be the primary management UI for Gluster. AFAIK Gluster is now
getting its own UI.
As far as using DRBD for backing oVirt VMs, this seems to already be
working. The oVirt CI system (which runs on top of oVirt) had been
using a DRBD-backed NFS storage for years..
a little on how this works? Would this means the
block devices would be configured on the hypervisors themselves? Is
this intended to be some kind of a hyper-converged architecture?
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
>
> I think we can keep the current way we set the version, but replace
> the serial number with a timestamp.
>
This wound lead to a non-reproducible build process, so I'd rather you
won't go there.
--
Barak Korren
bkor...@redhat.com
special treatment.
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
4.0.0: Could not
find artifact org.ovirt.vdsm-jsonrpc-java:vdsm-jsonrpc-java-client:jar:1.2.3
in ovirt-maven-repository
(http://artifactory.ovirt.org/artifactory/ovirt-mirror) -> [Help 1]
07:13:31 [ERROR]
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
D
ill have less hard-coding and
perhaps be more efficient (are we certain we only download what we
need atm?)
The existing solution looks more like premature optimization gone badly IMO.
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing li
ost of that should be a lot faster the 2nd time around, and also
there is some work being done to shrink down the images.
@Yaniv, you did the test on a machine that didn't run Lago before and
was in TLV while using the repo in PHX right?
--
Barak Korren
bkor...@redha
>
> python-cheetah didn't receive updates since 2012 and is not available on
> RHEL 7.2.
>
'python-cheetah' is used internally by Koji (for Mead) so I find the
news that it is not supported on RHEL to be very strange
--
Barak Korren
bkor...@redhat.com
gt; --
>> Eyal Edri
>> Associate Manager
>> RHEV DevOps
>> EMEA ENG Virtualization R
>> Red Hat Israel
>>
>> phone: +972-9-7692018
>> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>>
>> ___
his question is not relevant for you.
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
he following aught to fix that:
https://gerrit.ovirt.org/#/c/54978/
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
> _______
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
--
at (Say I want to upload the the ISOs
to my own ISO domain, where to I find them? how do I know the ones I
found match the oVirt version I have? This is a hassle, VMware has
VM->right-click->deploy guest tools).
So far we had at least one way to get around the hassle, before we
remove
ver Error'. Anyone else facing
> the same issue?
>
>
> Regards,
> Ramesh
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
hat you fetch, no?
> Y.
>
I was referring to the deployment/test code.
AFAIK right now the external repos are disabled before the test starts
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
On 29 June 2016 at 21:45, Yaniv Kaul <yk...@redhat.com> wrote:
> On Mon, Jun 27, 2016 at 9:45 AM, Barak Korren <bkor...@redhat.com> wrote:
>>
>> >
>> >
>> > It means that packages will be fetched EVERY time from outside, which
>> > ma
nfra-docs.readthedocs.io/en/latest/CI/Build_and_test_standards.html
[2]: http://ovirt-system-tests.readthedocs.io/en/latest/
[3]: https://ovirt-jira.atlassian.net/browse/OVIRT-970
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
up my own to do github
> pull request tests, it's not a problem.
If you can organise things in a way that matches the existing
standards, it will make things easier in the future. You can probably
"borrow" some of our code to do that...
I'll be happy to help...
--
Barak Korren
bkor..
> https://travis-ci.org/oVirt/vdsm/jobs/198571422
Take a look at 'Jenkins Blue Ocean", we'll deploy that eventually.
Then again, the existing Jenkins UI is far more flexible then any of
the modern flashy UIs I've seen. I guess this is a KDE v.s. Gnome kind
of thing...
What really needs to happen is th
he current
>status of your build as an image in a fixed URL.
>You can put this URL into other sites (such as GitHub
>README) so that people can see the current
>state of the job (last build) or for a specific build.
>
>
\o/
http://jenkins.ovirt.org/job/
On 23 February 2017 at 16:35, Nir Soffer <nsof...@redhat.com> wrote:
> On Thu, Feb 23, 2017 at 9:37 AM, Barak Korren <bkor...@redhat.com> wrote:
>> Test failed: [ add_secondary_storage_domains ]
>>
>> Note:
>> - This may or may not be related to
>>
//jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tests_manual/64/console
>
> Thanks for reporting this.
>
> Nir
>
>
> On Thu, Feb 23, 2017 at 5:03 PM, Nir Soffer <nsof...@redhat.com> wrote:
>> On Thu, Feb 23, 2017 at 4:51 PM, Yaniv Kaul <yk...@red
12 OST runs straight.
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Next run passed finally:
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5504/
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
be interested to tackle
this.
[1]: http://www.projectatomic.io/blog/2016/09/intro-to-system-containers/
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Devel mailing list
Devel@ovirt.org
http://lists.ov
e
relevat OST suit (most are symlinks to a common file). If we'd
download the entire CentOS repo during OST, the jobs would take much
longer.
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Devel mailing l
o select projects pre-merge. Engine will
most probably be one of the projects this is applied to.
> I haven't merged the patches because I wanted feedback like this, thanks
> Barack.
Thanks for consulting with us.
One nitpick - "Barack" is how the former POTUS spells it, I spe
.
>
>
> Don't think there's a very good solution to this in our current
> architecture.
Yeah, this is what https://gerrit.ovirt.org/#/c/71353/ is aimed at...
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
_
ootstrap.py/lago_basic_suite_master_host0/_var_log_vdsm/vdsm.log
[6]:
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/1077/artifact/exported-artifacts/basic_suite_4.0.sh-fc23/exported-artifacts/test_logs/basic_suite_4.0/post-002_bootstrap.py/lago_basic_suite_4_0_hos
>= 1.3.7
>
You can only use the syntax supported by yum.
Since yum always installs latest by default, a '>=' syntax would not
be useful with it.
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
refore, I think making tests run in %check should not be a high priority.
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
tegration tests
like ovirt-system-tests.
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
est] (MainThread) Could not find mapping
> for lv
> c088020e-91b2-45e6-85fd-eea3fce58764/3267d54d-c0fa-4fe1-b82b-b88dd5f90de3
> 12:33:20 2016-09-28 05:32:03,264 DEBUG
> [storage.StorageDomainManifest] (MainThread) Found freeSlot 4 in VG
> c088020e-91b2-45e6-85fd-eea3fce58764
> 12:33:20 - >> end captured logging <<
> -
> 1
> ___
> Infra mailing list
> in...@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
ought we are doing them on the libvirt level?
Its not oVirt that needs those, its some specific VDSM unit tests.
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
>
> Brian Proffitt
> Principal Community Analyst
> Open Source and Standards
> @TheTechScribe
> 574.383.9BKP
>
> _______
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
g of oVirt v3 for testing is a laptop on a UPS at my home, and
> > v4 is also a different pc attached to a UPS.
> >
> > External Dependencies
> >
> > RHEVM/oVirt REST API - This provider must interact with the API itself
> > to manage virtual machines.
> >
> > Initial Committers
> >
> > Marcus Young ( 3vilpenguin at gmail dot com )
> >
> > --
> > Brian Proffitt
> > Principal Community Analyst
> > Open Source and Standards
> > @TheTechScribe
> > 574.383.9BKP
> >
> > ___
> > Devel mailing list
> > Devel@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
>
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
--
*Barak Korren*
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
was the slow thing until we moved to local disks).
Please investigate further, and open libvirt/oVirt bugs if you think
the slave VMs are somehow inherently slow, as oVirt is not currently
telling us the hyper-visors are overloaded in any way.
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV
>
> Let us now try the more lenient "rebase if needed", please.
Moved.
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/
uot; which is like "Rebase if
Necessary" but always creates a new commit (with headers). Please note
that this is less strict then ff-only and therefore would lead to
merged combinations that do not get tested in CI.
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
x that? Is it waiting
forever for something that will never "show up" because it is outside
the mock env (And could be bind-mounted into it)?
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
com/2016/09/integrating-rhv-openstack-neutron/
>
> Sincerely,
>
> --
> Than H. Maung, CISSP
> tma...@techintsolutions.com
> (571) 295-8462
>
> ___
> Devel mailing list
> Devel@ovirt.org
> http://lists.ovi
rt.org/gitweb?p=ovirt-engine.git;a=blob;f=automation/check-patch.sh;h=4f136d69813c6a017f0befb2f9ea60b6c7e44639;hb=refs/heads/master#l111
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
te...
Anyway, this is not directly related to merge-gating, so a little off-topic IMO.
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
>
> I enjoyed the freedom of cherry-pick, but after 2 broken nightly builds
> in the span of 10 days, I give up. Let's try ff-only.
>
All right, changed.
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
Devel@ov
;click" the submit button on our behalf if tests pass.
I see two options here:
1. Use Code-Review+2 as the indicator to run "heavy" CI and merge.
2. Add an "approve" flag that maintainers can set to +1 (This is
what OpenStack is doing).
What would you prefer?
ient button to do
it). When he does, a new patch set gets pushed, and subsequently
checked by CI.
I recommend we switch all projects to use the "Fast Forward Only" submit type.
Thoughts? Concerns?
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
__
we don't to agree on every little
> detail, the project maintainer can do whatever they want.
Ok, so can we get an agreement between the vdsm maintainers to change
to "ff-only"?
--
Barak Korren
bkor...@redhat.com
RHEV-CI Team
___
Devel mailing list
he standard-CI system to make that
happen, so it'll take a while.
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Devel mailing list
Devel@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/devel
n.net/browse/OVIRT-937
[2]: https://ovirt-jira.atlassian.net/browse/OVIRT-938
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Devel mailing list
Devel@ovirt.org
http://lists.phx.ovirt.org/mailman/listinfo/devel
ystem as a whole works.
As for now, Zuul is the only system I know of that does good
cross-project merge gating. And, for the time being, it does not
support anything other then Gerrit. So I recommend we stay with Gerrit
for now.
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://i
that you can't merge a patch
that needs a rebase, so if patches were rebased, and build_artifacts
runs post-merge, it should be impossible to get it to run on
non-rebased code.
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifirebal
o trust us to not misconfigure the project like that
>> :)
I'm inclined to do so.
I know full well though, that we will get complaints when the system
does what it was told to do as opposed to what the maintainer
wanted...
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
http
y/broken tests or CI infra issues, we need to decide how to deal
> with those, I think.
Hopefully we get to the point where they are rare.
> It was just an idea =) Zuul sounds more like a proper solution.
Just to make things clear - Zuul does not do any magic with Gerrit's
"submit" bu
oVirt CI hardware - I'd still prefer to
have such processes automated on oVirt intra as opposed to done
manually by the maintainer.
Could we change things so the builds are launched from our Jenkins as
opposed to done directly on its slaves?
--
Barak Korren
bkor...@redhat.com
RHC
forward to try it out - and it proved to be
too cumbersome for VDSM maintainers - so switched back to "Merge if
Necessary".
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
ock-confs-dir $JENKINS/mock_configs "fc24.*x86_64"
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
On 5 December 2016 at 10:07, Nir Soffer <nsof...@redhat.com> wrote:
>
> 20 seconds setup sounds great.
>
> Can we try the patches with vdsm builds?
We'll probably merge today, if not, I'll manually cherry-pick this for
the vdsm jobs.
--
Barak Korren
bkor...@redhat.com
RHCE
n again, this is a prioritization question - it not up to me to decide.
[1]: https://ovirt-jira.atlassian.net/browse/OVIRT-734
[2]: https://ovirt-jira.atlassian.net/browse/OVIRT-882
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
button in Gerrit - I still don't think we should have this
(Better to aim for CI to be fast and reliable enough).
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
dsm/wiki
[3]: https://github.com/oVirt/ovirt-system-tests/wiki
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
ow OSAS some editorial
control over what goes on the public site.
I'm guessing that the scenario you are talking about here is a
developer looking to create a preliminary design document for further
discussion. Maybe we need a different tool and process for that?
--
Barak Korren
bkor...@redhat.com
RHC
On 10 January 2017 at 14:33, Ewoud Kohl van Wijngaarden
<ewoud+ov...@kohlvanwijngaarden.nl> wrote:
> On Tue, Jan 10, 2017 at 11:31:50AM +0200, Barak Korren wrote:
>> I suggest we make the platform suffix explicitly required (with a
>> compatibility fall-back, see be
Kubevirt we also use a .travis.yaml which does testing and releasing
> based on tags and branches [1].
>
> Note that for more finetuned controls, they also provide a lot of
> environment variables which you can reference (e.g. branch, tag, ...)
>
Lets not run this into an off-topic 'travi
antee that an oVirt release
can take builds from at most one branch.
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
(-.*)?-.4.0' or (-4.0) to accommodate existing
conventions like the engine`s.
Thoughts? Ideas?
( Jira ticket tracking this work:)
( https://ovirt-jira.atlassian.net/browse/OVIRT-1013 )
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com
is.yml (or
> automation dir in our case) are ignored.
Travis never concerns itself with full system composition and
integration testing, so this is not a useful analogy at all.
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
_
know, you
can use 'muck_runner.sh' to run the CI scripts in almost exactly the
same way Jenkins does it). This is why we tend to not provide any more
contextual information then you would have while running the script on
your laptop.
Having said that, its quite easy for us to provide every
/004_basic_sanity/vm_run/
Further logs can be seen in Jenkins:
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/13/artifact/exported-artifacts/basic_suite_4.1.sh-el7/exported-artifacts/test_logs/basic-suite-4.1/post-004_basic_sanity.py/
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps
_master/4275/artifact/exported-artifacts/basic_suite_master.sh-el7/exported-artifacts/test_logs/basic-suite-master/post-004_basic_sanity.py/lago-basic-suite-master-engine/_var_log_ovirt-engine/engine.log
Please have a look.
Thanks,
Barak.
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-Dev
On 18 December 2016 at 17:26, Nir Soffer <nsof...@redhat.com> wrote:
> On Sun, Dec 18, 2016 at 4:17 PM, Barak Korren <bkor...@redhat.com> wrote:
> We a lot of these errors in the rest of the log. This meas something
> is wrong with this vg.
>
> Needs deeper investiga
ves every time we reach out to you. Give us the benefit of
the doubt of believing we were diligent enough to eliminate such
issues before approaching you.
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
בתאריך 23 בדצמ׳ 2016 12:46 PM, "Dan Kenigsberg" כתב:
On Thu, Dec 22, 2016 at 5:45 PM, Yaniv Bronheim wrote:
> On Thu, Dec 22, 2016 at 5:39 PM, Leon Goldberg
wrote:
>
>> Doesn't seem related; the patch does nothing but move pieces
on
> ls -l /var/log/ovirt-imageio-daemon/
total 0
HTH,
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
apper
return f(*a, **kw)
File "/usr/lib/python2.7/site-packages/vdsm/network/sourceroutethread.py",
line 90, in _subscribeToInotifyLoop
for filePath in sorted(os.listdir(SOURCE_ROUTES_FOLDER)):
OSError: [Errno 20] Not a directory: '/var/run/vdsm/sourceRoutes'
--
Barak Korr
r::275::SuperVdsm.Server::(main) Making
sure I'm root - SuperVdsm
... Repeat ...
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
not how a Jenkins timeout looks like.
The whole job took 53m and 20s. The timeout is set to 360m [2]...
[1]: https://ovirt-jira.atlassian.net/browse/OVIRT-938
[2]:
https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/projects/defaults.yaml;h=c0946d70b196
-in, which is something I'm not eager to
try... (An I think neither is anyone else from the infra team...)
But go ahead and create a Jira ticket, why not...
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
On 7 December 2016 at 14:15, Nir Soffer <nsof...@redhat.com> wrote:
> On Mon, Dec 5, 2016 at 10:11 AM, Barak Korren <bkor...@redhat.com> wrote:
>> On 5 December 2016 at 10:07, Nir Soffer <nsof...@redhat.com> wrote:
>>>
>>> 20 seconds setup sounds gr
On 7 December 2016 at 14:15, Nir Soffer <nsof...@redhat.com> wrote:
>
> Last week it was 19-20 mintues, great improvement!
>
there are a couple of other things we might try soon, that will,
perhaps, help us shave off another 2-3 minutes...
--
Barak Korren
bkor...@redhat.com
בתאריך 17 במרץ 2017 02:32 PM, "Piotr Kliczewski" <
piotr.kliczew...@gmail.com> כתב:
The change was merged 2 weeks ago. How can we make sure not to waste
people time next time to analyze the issue?
"Merged" is hardly "released".
As long as a fix does not make it to a release, users can still
.ovirt.org/mailman/listinfo/devel
--
Barak Korren
bkor...@redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
1 - 100 of 365 matches
Mail list logo