On Mon, Feb 22, 2016 at 9:06 PM, Yaniv Kaul wrote:
> On Mon, Feb 22, 2016 at 5:25 PM, Yaniv Bronheim
> wrote:
>
>> Hi,
>> I added recently to check-merged phase a job for automatic functional
>> test run. see for example
>>
On Mon, Feb 22, 2016 at 5:25 PM, Yaniv Bronheim wrote:
> Hi,
> I added recently to check-merged phase a job for automatic functional test
> run. see for example
> http://jenkins.ovirt.org/job/vdsm_master_check-merged-fc23-x86_64/52/
>
Excellent!
>
>
- Original Message -
> From: "Mikey Ariel"
> To: us...@ovirt.org, devel@ovirt.org, in...@ovirt.org
> Sent: Thursday, February 18, 2016 1:42:56 PM
> Subject: [ovirt-devel] Coming (Very) Soon - New ovirt.org Website &
> Deprecated Wiki
>
> -BEGIN PGP SIGNED
Hi,
I added recently to check-merged phase a job for automatic functional test
run. see for example
http://jenkins.ovirt.org/job/vdsm_master_check-merged-fc23-x86_64/52/
https://gerrit.ovirt.org/#/c/48268/58/automation/check-merged.sh -
generally, it installs lago in the jenkins machine, set up
All stable branch maintainers, please make sure to merge all relevant open
bugs until Tuesday morning 11:00 AM TLV time.
https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3.6.3%20target_release%3A---%20status%3Amodified%2Cpost
Every package build (i.e oVirt product) -
Fyi oVirt developers,
An oVirt build is planned for this Tuesday 11:00 AM TLV time (10:00 AM CET).
Taking into consideration the time it takes for Jenkins to run a full CI
everything need to be backported by monday 11PM.
Please make sure to mark as verified and CR +2 so it will be ready for
On Mon, Feb 22, 2016 at 1:31 PM, Martin Sivak wrote:
> Here is a solution that should play nice with Network Manager:
>
> +1 for a steady stable solution like this
+Eldad I'm sure this may come in handy for you
> /etc/NetworkManager/dnsmasq.d/10-vdsmfake.conf
>
>
Here is a solution that should play nice with Network Manager:
/etc/NetworkManager/dnsmasq.d/10-vdsmfake.conf
address=/vdsm.simulator/127.0.0.1
/etc/NetworkManager/conf.d/20-dnsmasq.conf
[main]
dns=dnsmasq
$ yum install dnsmasq
$ systemctl disable dnsmasq
$ systemctl restart NetworkManager
> On 20 Feb 2016, at 17:46, Paul Dyer wrote:
>
> It seems like I am hitting this issue from release 3.6.0:
>
> If cluster is updated to compatibility version 3.6 while hosts that have not
> been upgraded, i.e with emulated machine flags that do not match cluster
>