The proposed way is:
- use CORS filter for enginesso.war (https://gerrit.ovirt.org/68062)
- at host installation, add the host to CORSAllowedOrigins
- on engine host: # engine-config -s 'CORSAllowedOrigins=[host IPs]'
So if Cockpit's plugin accesses the oVirt REST API, CORS will work.'
On
- Original Message -
From: "Dan Kenigsberg"
To: "Ramesh Nachimuthu"
Cc: "Sahina Bose" , "devel" , "Yaniv Bronheim"
, "Francesco
Romani" , "Nir Soffer"
On Sun, Dec 11, 2016 at 7:07 PM, Nadav Goldin wrote:
> I think what happened is:
> 1. The two patches https://gerrit.ovirt.org/#/c/67976 and
> https://gerrit.ovirt.org/#/c/67878/(the version bump) were merged
> approximately at the same time.
> 2. The build_artifacts job for
On 11 December 2016 at 16:01, Eyal Edri wrote:
>
>
> AFAIK all of these builds were triggered on merged patches.
We need to see which code its cloning - I suspect it is still trying
to clone the patch instead of the master branch, this may indeed be a
bug in how we configure
On Sun, Dec 11, 2016 at 4:00 PM, Barak Korren wrote:
> On 11 December 2016 at 11:18, Eyal Edri wrote:
> > Adding infra as well.
> >
> > I see a very strange thing happening on the build artifacts jobs:
> >
> > On [1] we see a successful build of 1.2.10
On Sun, Dec 11, 2016 at 3:13 PM, Yaniv Kaul wrote:
>
>
> On Sun, Dec 11, 2016 at 3:10 PM, Shlomo Ben David
> wrote:
>
>> Hi,
>>
>> The [1] job fails with the following errors:
>>
>> *12:34:20 [31mError while running thread
>> 12:34:20 Traceback (most
On Sun, Dec 11, 2016 at 3:10 PM, Shlomo Ben David
wrote:
> Hi,
>
> The [1] job fails with the following errors:
>
> *12:34:20 [31mError while running thread
> 12:34:20 Traceback (most recent call last):
> 12:34:20 File "/usr/lib/python2.7/site-packages/lago/utils.py",
Hi,
The [1] job fails with the following errors:
*12:34:20 [31mError while running thread
12:34:20 Traceback (most recent call last):
12:34:20 File "/usr/lib/python2.7/site-packages/lago/utils.py", line
55, in _ret_via_queue
12:34:20 queue.put({'return': func()})
12:34:20 File
On Sun, Dec 11, 2016 at 2:49 PM, Gil Shinar wrote:
> If I understand the issue correctly, the failures are for fc23 and not for
> el7.
> build artifacts 23, the one that bumped the version, failed for fc23 [1]
> because of test failures.
>
I don't think it has to do with the
If I understand the issue correctly, the failures are for fc23 and not for
el7.
build artifacts 23, the one that bumped the version, failed for fc23 [1]
because of test failures.
[1]
http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_4.0_build-artifacts-fc23-x86_64/23/console
On Sun, Dec 11, 2016
FYI,
We're seeing a single test 'add hotplug disk' failing recently on OST, the
test only failed once on the jobs [1] and was fixed on its own after one
run, but now I see it also on check-patch [2] jobs.
Looking at the changelog, I can't find immediate suspects, and if this is a
race it might
Adding infra as well.
I see a very strange thing happening on the build artifacts jobs:
On [1] we see a successful build of 1.2.10 built in build-artifacts, but on
the 2 patches merged after it, its back to 1.2.9 [2].
Is it possible that the 2 patches merged after the version bump weren't
Yes, version bump was merged.
11 gru 2016 09:57 "Eyal Edri" napisaĆ(a):
> Was the version bumped pushed to the repo itself in Gerrit?
> I.e - does build-artifacts builds now the new version 1.2.10?
>
> On Fri, Dec 9, 2016 at 9:33 PM, Sandro Bonazzola
>
Was the version bumped pushed to the repo itself in Gerrit?
I.e - does build-artifacts builds now the new version 1.2.10?
On Fri, Dec 9, 2016 at 9:33 PM, Sandro Bonazzola
wrote:
>
>
> Il 09/Dic/2016 18:45, "Piotr Kliczewski" ha scritto:
>
> Here [1] is
14 matches
Mail list logo