[ovirt-devel] Re: Proposing Marcin Sobczyk as VDSM infra maintainer

2019-11-12 Thread Dan Kenigsberg
On Mon, Nov 11, 2019 at 3:36 PM Nir Soffer wrote: > > On Thu, Nov 7, 2019 at 4:13 PM Martin Perina wrote: > > > > Hi, > > > > Marcin has joined infra team more than a year ago and during this time he > > contributed a lot to VDSM packaging, improved automation and ported all > > infra team part

[ovirt-devel] ovirt-engine has been tagged (ovirt-engine-4.3.7.2)

2019-11-12 Thread Tal Nisan
___ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archive

[ovirt-devel] Re: Proposing Marcin Sobczyk as VDSM infra maintainer

2019-11-12 Thread Marcin Sobczyk
On 11/12/19 9:56 AM, Dan Kenigsberg wrote: On Mon, Nov 11, 2019 at 3:36 PM Nir Soffer wrote: On Thu, Nov 7, 2019 at 4:13 PM Martin Perina wrote: Hi, Marcin has joined infra team more than a year ago and during this time he contributed a lot to VDSM packaging, improved automation and porte

[ovirt-devel] Yarn build failing

2019-11-12 Thread Ritesh Chikatwar
Team, Any idea why am i facing this issue when i do *yarn build * for ovirt-engine-ui-extensions 1:1 error Parsing error: 'import' and 'export' may appear only with 'sourceType: module' /home/ritesh/git/ui-extenstion/ovirt-engine-ui-extensions/src/utils/webadmin-dom.js 1:1 error Parsi

[ovirt-devel] Re: [feedback needed] oVirt master test

2019-11-12 Thread Joop van de Wege
Downloaded both the ova and iso and imported it into my test install of ovirt-4.3.7 and had only problems with the ova. What I did was is to unpack the rpm and use the ova archive to import it using the webui but that failed, did a chown 36:36 on it but no luck. At the end I just extracted the di

[ovirt-devel] Re: Yarn build failing

2019-11-12 Thread Benny Zlotnik
did you run `yarn install`? On Tue, Nov 12, 2019 at 12:35 PM Ritesh Chikatwar wrote: > > Team, > > > Any idea why am i facing this issue when i do yarn build for > ovirt-engine-ui-extensions > > > 1:1 error Parsing error: 'import' and 'export' may appear only with > 'sourceType: module' >

[ovirt-devel] Re: Yarn build failing

2019-11-12 Thread Ritesh Chikatwar
Yeah, it is installed successfully. On Tue, Nov 12, 2019 at 6:41 PM Benny Zlotnik wrote: > did you run `yarn install`? > > On Tue, Nov 12, 2019 at 12:35 PM Ritesh Chikatwar > wrote: > > > > Team, > > > > > > Any idea why am i facing this issue when i do yarn build for > ovirt-engine-ui-extensi

[ovirt-devel] vdsm has been tagged (v4.30.37)

2019-11-12 Thread Milan Zamazal
4.3.7 should be 4.*.37, shouldn't it? ___ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/abo

[ovirt-devel] Re: vdsm has been tagged (v4.30.37)

2019-11-12 Thread Dafna Ron
Thanks Milan :) On Tue, Nov 12, 2019 at 2:32 PM Milan Zamazal wrote: > 4.3.7 should be 4.*.37, shouldn't it? > > ___ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/s

[ovirt-devel] Re: Check patch failure in vdsm

2019-11-12 Thread Miguel Duarte de Mora Barroso
On Mon, Nov 11, 2019 at 11:12 AM Eyal Shenitzky wrote: > > Hi, > > I encounter the following error for py36 test in vdsm check patch: > > ... > ... > 14:03:37 File "/usr/local/lib/python3.7/site-packages/pluggy/callers.py", > line 187, in _multicall > 14:03:37 res = hook_impl.function(*args) > 14

[ovirt-devel] Building vdsm with standard-manual-runner fails to clone the repo

2019-11-12 Thread Nir Soffer
Building vdsm using standard-manual-runner fails now with: ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git fetch --tags --progress https://gerrit.ovirt.org/jenkins +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: error: RPC fai

[ovirt-devel] Re: Check patch failure in vdsm

2019-11-12 Thread Nir Soffer
On Tue, Nov 12, 2019 at 5:34 PM Miguel Duarte de Mora Barroso wrote: > > On Mon, Nov 11, 2019 at 11:12 AM Eyal Shenitzky wrote: > > > > Hi, > > > > I encounter the following error for py36 test in vdsm check patch: > > > > ... > > ... > > 14:03:37 File "/usr/local/lib/python3.7/site-packages/plug

[ovirt-devel] Re: Check patch failure in vdsm

2019-11-12 Thread Nir Soffer
On Tue, Nov 12, 2019 at 7:30 PM Nir Soffer wrote: > > On Tue, Nov 12, 2019 at 5:34 PM Miguel Duarte de Mora Barroso > wrote: > > > > On Mon, Nov 11, 2019 at 11:12 AM Eyal Shenitzky wrote: > > > > > > Hi, > > > > > > I encounter the following error for py36 test in vdsm check patch: > > > > > > .

[ovirt-devel] Fedora 31 support

2019-11-12 Thread Nir Soffer
We usually support only the most recent version of Fedora, which is now 31. We can use Fedora 30 for a while, but it is really too old (older than CentOS 8) and there is on point to use it. Instead of helping to discover issues early, we waste time on dealing with old packages that nobody maintain

[ovirt-devel] Re: Yarn build failing

2019-11-12 Thread Scott Dickerson
Hi Ritesh, Just ran this without issue: [sdickers@ghost test]$ rpm -q nodejs nodejs-10.16.3-1.fc30.x86_64 [sdickers@ghost test]$ rpm -q yarn yarn-1.19.1-1.noarch [sdickers@ghost test]$ git clone https://gerrit.ovirt.org/ovirt-engine-ui-extensions Cloning into 'ovirt-engine-ui-extensions'

[ovirt-devel] Re: Yarn build failing

2019-11-12 Thread Ritesh Chikatwar
Scott, I re-installed node and yarn it worked. Thanks for the solution. On Wed, Nov 13, 2019 at 3:11 AM Scott Dickerson wrote: > Hi Ritesh, > > Just ran this without issue: > > > [sdickers@ghost test]$ rpm -q nodejs > nodejs-10.16.3-1.fc30.x86_64 > [sdickers@ghost test]$ rpm -q y

[ovirt-devel] Changing a host name

2019-11-12 Thread Prajith Kesava Prasad
Hey everyone, So im in need of replacing a host, so the process goes like this , there are 3 hosts called A,B,C with (RHHI setup) (ovirt) and i want to replace A, so I order a new physical machine D and now i have to disable the A's hostname(meaning its not accessible by A anymore) and now i chan

[ovirt-devel] Re: Fedora 31 support

2019-11-12 Thread Sandro Bonazzola
Il giorno mar 12 nov 2019 alle ore 22:26 Nir Soffer ha scritto: > We usually support only the most recent version of Fedora, which is now 31. > > We can use Fedora 30 for a while, but it is really too old (older than > CentOS 8) and > there is on point to use it. Instead of helping to discover is