On 23 August 2017 at 08:58, Yedidyah Bar David wrote:
> Hi all,
>
> Is it possible to make the "Build History" box in jenkins show
> some more information? E.g. Who/What triggered each build?
Yes. With Groovy code, from inside the job.
> This is especially useful for *manual* jobs, that are supp
On Wed, Aug 23, 2017 at 8:58 AM, Yedidyah Bar David wrote:
> Hi all,
>
> Is it possible to make the "Build History" box in jenkins show
> some more information? E.g. Who/What triggered each build?
> This is especially useful for *manual* jobs, that are supposed
> to be triggered manually by users.
Hi all,
Is it possible to make the "Build History" box in jenkins show
some more information? E.g. Who/What triggered each build?
This is especially useful for *manual* jobs, that are supposed
to be triggered manually by users. Later, it's a bit hard to find
your builds.
Thanks,
--
Didi
Hi all,
I've made a Go sdk for oVirt-engine v4.0+ implemented. The Go sdk generator
locates (mainly Java) in imjoey/ovirt-engine-sdk-go of github, while for the
Go sdk itself is in imjoey/go-ovirt.
With the help of some dear oVirt sdk maintainers, the project has achieved
nearly 90 percent now. I
Hi,
we have just merged patches [1], which adds the ability to use firewalld
instead of iptables on oVirt hosts.
The type of firewall can be defined per cluster, there is new combo box
'Firewall Type' in 'Cluster Detail' dialog. By default all new clusters
will be created with firewalld enabled,
Hi all,
It was broken by 7914051a (merged yesterday) and fixed by 7e27a47
(merged today).
If you run 'engine-setup' with a broken version, it will exit silently
with rc=1. If this happens, please pull from master.
Sorry for the mess.
Best,
--
Didi
__
In this case turning off the callback prefix check should be helpful
Create a new conf file /etc/ovirt-engine/engine.conf.d/99-sso.conf and add
the line below to the file. This will turn off the additional security
check for the callback prefix.
SSO_CALLBACK_PREFIX_CHECK=false
Ravi
On Tue, Aug
Adding Ravi
On Mon, Aug 21, 2017 at 10:53 AM, Roy Golan wrote:
>
> When using OST you get an engine on isolated network, that in order to
> make available you must tunnel. When tunnelling you end up with a URI with
> a uncommon port or hostname that will result an error while authenticating:
>
>
This seems to be my fault, https://gerrit.ovirt.org/80908 should fix it.
On Tue, Aug 22, 2017 at 1:14 PM, Nir Soffer wrote:
>
>
> On יום ג׳, 22 באוג׳ 2017, 12:57 Yedidyah Bar David wrote:
>>
>> On Tue, Aug 22, 2017 at 12:52 PM, Anton Marchukov
>> wrote:
>> > Hello All.
>> >
>> > Any news on thi
+ Yaniv B.
On Tue, Aug 22, 2017 at 12:14 PM, Nir Soffer wrote:
>
>
> On יום ג׳, 22 באוג׳ 2017, 12:57 Yedidyah Bar David
> wrote:
>
>> On Tue, Aug 22, 2017 at 12:52 PM, Anton Marchukov
>> wrote:
>> > Hello All.
>> >
>> > Any news on this? I see the latest failures for vdsm is the same [1]
>> a
On יום ג׳, 22 באוג׳ 2017, 12:57 Yedidyah Bar David wrote:
> On Tue, Aug 22, 2017 at 12:52 PM, Anton Marchukov
> wrote:
> > Hello All.
> >
> > Any news on this? I see the latest failures for vdsm is the same [1] and
> > the job is still not working for it.
> >
> > [1]
> >
> http://jenkins.ovirt.
On Tue, Aug 22, 2017 at 12:52 PM, Anton Marchukov wrote:
> Hello All.
>
> Any news on this? I see the latest failures for vdsm is the same [1] and
> the job is still not working for it.
>
> [1]
> http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1901/artifact/exported-artifacts/basic-
Hello All.
Any news on this? I see the latest failures for vdsm is the same [1] and
the job is still not working for it.
[1]
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1901/artifact/exported-artifacts/basic-suit-master-el7/test_logs/basic-suite-master/post-002_bootstrap.py/lag
On Tue, Aug 22, 2017 at 9:10 AM, Barak Korren wrote:
> On 21 August 2017 at 23:24, Valentina Makarova
> wrote:
> >
> > Hello!
> >
> > OST failed in ./run_suilte.sh upgrade-from-release-suite-master
> > (it is likely to appear after updating in some remote repo) with error:
> >
> > Trying other m
The problem is not with the 'tested' repo, but with the official
ldap-1.3.2-1ovirt-4.1 repo.
We have ovirt-engine-extension-aaa-ldap-*1.3.2-1* but
ovirt-engine-extension-aaa-ldap-setup-*1.3.3-1*.
upgrade-from-release-suite-master, will first try to initialize and install
engine 4.1 and then upgrade
On 21 August 2017 at 23:24, Valentina Makarova wrote:
>
> Hello!
>
> OST failed in ./run_suilte.sh upgrade-from-release-suite-master
> (it is likely to appear after updating in some remote repo) with error:
>
> Trying other mirror.
> Error: Package:
> ovirt-engine-extension-aaa-ldap-setup-1.3.3-1.
On 22 August 2017 at 09:58, Michal Skrivanek
wrote:
> This seems unrelated to both changes mentioned below
> Please take a look at why does it identify those patches
> At least one issue seems to be
> http://lists.ovirt.org/pipermail/devel/2017-August/031057.html
It identified them because a tes
Hi Valentina,
Our team is working to fix this issue. I'll update here asap.
Thanks,
On Mon, Aug 21, 2017 at 11:26 PM Valentina Makarova
wrote:
>
> Hello!
>
> OST failed in ./run_suilte.sh upgrade-from-release-suite-master
> (it is likely to appear after updating in some remote repo) with error
18 matches
Mail list logo
