[VDSM] Build failure because missing ioprocess package in ovirt repos - solved
Hi all, There was a broken build of ioprocess in ovirt repos, causing vdsm all vdsm master builds to fail with this error: ERROR: Command failed. See logs for output. If you have failed builds, please retrigger them in jenkins: http://jenkins.ovirt.org/gerrit_manual_trigger/ Nir
Was the broken build replaced by new one that is working? On Fri, Aug 12, 2016 at 9:10 PM, Nir Soffer <nsoffer@redhat.com> wrote:
Hi all,
There was a broken build of ioprocess in ovirt repos, causing vdsm all vdsm master builds to fail with this error:
ERROR: Command failed. See logs for output.
If you have failed builds, please retrigger them in jenkins: http://jenkins.ovirt.org/gerrit_manual_trigger/
Nir _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
The issue is different: both x86_64 and ppc64le builds python-ioprocess package so a newer python-ioprocess may come from ppc64le build not corresponding to an exact nvr on x86_64. Solution may be to chance the ioprocess build to drop the timestamp or make the ioprocess build a matrix job building from the same src.rpm. Another solution may be relax the nvr requirements in the python-ioprocess package to not require the exact nvr but only the same version. Another solution may be competely separate x86_64 and ppc64le repos. On Sun, Aug 14, 2016 at 8:12 AM, Eyal Edri <eedri@redhat.com> wrote:
Was the broken build replaced by new one that is working?
On Fri, Aug 12, 2016 at 9:10 PM, Nir Soffer <nsoffer@redhat.com> wrote:
Hi all,
There was a broken build of ioprocess in ovirt repos, causing vdsm all vdsm master builds to fail with this error:
ERROR: Command failed. See logs for output.
If you have failed builds, please retrigger them in jenkins: http://jenkins.ovirt.org/gerrit_manual_trigger/
Nir _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel
phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
_______________________________________________ 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
בתאריך 17 באוג׳ 2016 8:54 לפנה״צ, "Sandro Bonazzola" <sbonazzo@redhat.com> כתב:
The issue is different: both x86_64 and ppc64le builds python-ioprocess package so a newer
Solution may be to chance the ioprocess build to drop the timestamp or make the ioprocess build a matrix job building from the same src.rpm. Another solution may be relax the nvr requirements in the
python-ioprocess may come from ppc64le build not corresponding to an exact nvr on x86_64. python-ioprocess package to not require the exact nvr but only the same version.
Another solution may be competely separate x86_64 and ppc64le repos.
I think the issue is the requiring the a version with the timestamp and git commit, it sould only require the same version.
On Sun, Aug 14, 2016 at 8:12 AM, Eyal Edri <eedri@redhat.com> wrote:
Was the broken build replaced by new one that is working?
On Fri, Aug 12, 2016 at 9:10 PM, Nir Soffer <nsoffer@redhat.com> wrote:
Hi all,
There was a broken build of ioprocess in ovirt repos, causing vdsm all vdsm master builds to fail with this error:
ERROR: Command failed. See logs for output.
If you have failed builds, please retrigger them in jenkins: http://jenkins.ovirt.org/gerrit_manual_trigger/
Nir _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel
phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
_______________________________________________ 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
I posted this patch, changing python-ioprocess to require ioprocess-version (instead of version-release). This seem to resolve the issue and is more correct, we don't really need ioprocess from the same build. Please review https://gerrit.ovirt.org/62464 Nir On Wed, Aug 17, 2016 at 12:05 PM, Nir Soffer <nsoffer@redhat.com> wrote:
בתאריך 17 באוג׳ 2016 8:54 לפנה״צ, "Sandro Bonazzola" <sbonazzo@redhat.com> כתב:
The issue is different: both x86_64 and ppc64le builds python-ioprocess package so a newer python-ioprocess may come from ppc64le build not corresponding to an exact nvr on x86_64. Solution may be to chance the ioprocess build to drop the timestamp or make the ioprocess build a matrix job building from the same src.rpm. Another solution may be relax the nvr requirements in the python-ioprocess package to not require the exact nvr but only the same version. Another solution may be competely separate x86_64 and ppc64le repos.
I think the issue is the requiring the a version with the timestamp and git commit, it sould only require the same version.
On Sun, Aug 14, 2016 at 8:12 AM, Eyal Edri <eedri@redhat.com> wrote:
Was the broken build replaced by new one that is working?
On Fri, Aug 12, 2016 at 9:10 PM, Nir Soffer <nsoffer@redhat.com> wrote:
Hi all,
There was a broken build of ioprocess in ovirt repos, causing vdsm all vdsm master builds to fail with this error:
ERROR: Command failed. See logs for output.
If you have failed builds, please retrigger them in jenkins: http://jenkins.ovirt.org/gerrit_manual_trigger/
Nir _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel
phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
_______________________________________________ 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
On Wed, Aug 17, 2016 at 6:21 PM, Nir Soffer <nsoffer@redhat.com> wrote:
I posted this patch, changing python-ioprocess to require ioprocess-version (instead of version-release). This seem to resolve the issue and is more correct, we don't really need ioprocess from the same build.
Please review https://gerrit.ovirt.org/62464
+1
Nir
בתאריך 17 באוג׳ 2016 8:54 לפנה״צ, "Sandro Bonazzola" < sbonazzo@redhat.com> כתב:
The issue is different: both x86_64 and ppc64le builds python-ioprocess package so a newer python-ioprocess may come from ppc64le build not corresponding to an
exact
nvr on x86_64. Solution may be to chance the ioprocess build to drop the timestamp or make the ioprocess build a matrix job building from the same src.rpm. Another solution may be relax the nvr requirements in the
On Wed, Aug 17, 2016 at 12:05 PM, Nir Soffer <nsoffer@redhat.com> wrote: python-ioprocess
package to not require the exact nvr but only the same version. Another solution may be competely separate x86_64 and ppc64le repos.
I think the issue is the requiring the a version with the timestamp and git commit, it sould only require the same version.
On Sun, Aug 14, 2016 at 8:12 AM, Eyal Edri <eedri@redhat.com> wrote:
Was the broken build replaced by new one that is working?
On Fri, Aug 12, 2016 at 9:10 PM, Nir Soffer <nsoffer@redhat.com>
wrote:
Hi all,
There was a broken build of ioprocess in ovirt repos, causing vdsm all vdsm master builds to fail with this error:
ERROR: Command failed. See logs for output.
If you have failed builds, please retrigger them in jenkins: http://jenkins.ovirt.org/gerrit_manual_trigger/
Nir _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel
phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
_______________________________________________ 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
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
Merged, so I sent this to enable the ppc builds again: https://gerrit.ovirt.org/62551 Someone with access to jenkins should verify that this jobs works now. On Thu, Aug 18, 2016 at 10:03 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
On Wed, Aug 17, 2016 at 6:21 PM, Nir Soffer <nsoffer@redhat.com> wrote:
I posted this patch, changing python-ioprocess to require ioprocess-version (instead of version-release). This seem to resolve the issue and is more correct, we don't really need ioprocess from the same build.
Please review https://gerrit.ovirt.org/62464
+1
Nir
On Wed, Aug 17, 2016 at 12:05 PM, Nir Soffer <nsoffer@redhat.com> wrote:
בתאריך 17 באוג׳ 2016 8:54 לפנה״צ, "Sandro Bonazzola" <sbonazzo@redhat.com> כתב:
The issue is different: both x86_64 and ppc64le builds python-ioprocess package so a newer python-ioprocess may come from ppc64le build not corresponding to an exact nvr on x86_64. Solution may be to chance the ioprocess build to drop the timestamp or make the ioprocess build a matrix job building from the same src.rpm. Another solution may be relax the nvr requirements in the python-ioprocess package to not require the exact nvr but only the same version. Another solution may be competely separate x86_64 and ppc64le repos.
I think the issue is the requiring the a version with the timestamp and git commit, it sould only require the same version.
On Sun, Aug 14, 2016 at 8:12 AM, Eyal Edri <eedri@redhat.com> wrote:
Was the broken build replaced by new one that is working?
On Fri, Aug 12, 2016 at 9:10 PM, Nir Soffer <nsoffer@redhat.com> wrote:
Hi all,
There was a broken build of ioprocess in ovirt repos, causing vdsm all vdsm master builds to fail with this error:
ERROR: Command failed. See logs for output.
If you have failed builds, please retrigger them in jenkins: http://jenkins.ovirt.org/gerrit_manual_trigger/
Nir _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel
phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
_______________________________________________ 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
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On Thu, Aug 18, 2016 at 4:16 PM, Nir Soffer <nsoffer@redhat.com> wrote:
Merged, so I sent this to enable the ppc builds again: https://gerrit.ovirt.org/62551
Someone with access to jenkins should verify that this jobs works now.
will check tomorrow morning
On Thu, Aug 18, 2016 at 10:03 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
On Wed, Aug 17, 2016 at 6:21 PM, Nir Soffer <nsoffer@redhat.com> wrote:
I posted this patch, changing python-ioprocess to require ioprocess-version (instead of version-release). This seem to resolve the issue and is more correct, we don't really need ioprocess from the same build.
Please review https://gerrit.ovirt.org/62464
+1
Nir
On Wed, Aug 17, 2016 at 12:05 PM, Nir Soffer <nsoffer@redhat.com>
wrote:
בתאריך 17 באוג׳ 2016 8:54 לפנה״צ, "Sandro Bonazzola" <sbonazzo@redhat.com> כתב:
The issue is different: both x86_64 and ppc64le builds python-ioprocess package so a newer python-ioprocess may come from ppc64le build not corresponding to an exact nvr on x86_64. Solution may be to chance the ioprocess build to drop the timestamp
or
make the ioprocess build a matrix job building from the same src.rpm. Another solution may be relax the nvr requirements in the python-ioprocess package to not require the exact nvr but only the same version. Another solution may be competely separate x86_64 and ppc64le repos.
I think the issue is the requiring the a version with the timestamp and git commit, it sould only require the same version.
On Sun, Aug 14, 2016 at 8:12 AM, Eyal Edri <eedri@redhat.com> wrote:
Was the broken build replaced by new one that is working?
On Fri, Aug 12, 2016 at 9:10 PM, Nir Soffer <nsoffer@redhat.com> wrote: > > Hi all, > > There was a broken build of ioprocess in ovirt repos, causing vdsm > all > vdsm master builds to fail with this error: > > ERROR: Command failed. See logs for output. > > If you have failed builds, please retrigger them in jenkins: > http://jenkins.ovirt.org/gerrit_manual_trigger/ > > Nir > _______________________________________________ > Devel mailing list > Devel@ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > >
-- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel
phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
_______________________________________________ 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
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On Thu, Aug 18, 2016 at 6:03 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
On Thu, Aug 18, 2016 at 4:16 PM, Nir Soffer <nsoffer@redhat.com> wrote:
Merged, so I sent this to enable the ppc builds again: https://gerrit.ovirt.org/62551
Someone with access to jenkins should verify that this jobs works now.
will check tomorrow morning
Looks ok to me
On Thu, Aug 18, 2016 at 10:03 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
On Wed, Aug 17, 2016 at 6:21 PM, Nir Soffer <nsoffer@redhat.com> wrote:
I posted this patch, changing python-ioprocess to require ioprocess-version (instead of version-release). This seem to resolve the issue and is more correct, we don't really need ioprocess from the same build.
Please review https://gerrit.ovirt.org/62464
+1
Nir
On Wed, Aug 17, 2016 at 12:05 PM, Nir Soffer <nsoffer@redhat.com>
wrote:
בתאריך 17 באוג׳ 2016 8:54 לפנה״צ, "Sandro Bonazzola" <sbonazzo@redhat.com> כתב:
The issue is different: both x86_64 and ppc64le builds python-ioprocess package so a newer python-ioprocess may come from ppc64le build not corresponding to an exact nvr on x86_64. Solution may be to chance the ioprocess build to drop the timestamp
or
make the ioprocess build a matrix job building from the same src.rpm. Another solution may be relax the nvr requirements in the python-ioprocess package to not require the exact nvr but only the same version. Another solution may be competely separate x86_64 and ppc64le repos.
I think the issue is the requiring the a version with the timestamp and git commit, it sould only require the same version.
On Sun, Aug 14, 2016 at 8:12 AM, Eyal Edri <eedri@redhat.com>
wrote:
> > Was the broken build replaced by new one that is working? > > On Fri, Aug 12, 2016 at 9:10 PM, Nir Soffer <nsoffer@redhat.com> > wrote: >> >> Hi all, >> >> There was a broken build of ioprocess in ovirt repos, causing vdsm >> all >> vdsm master builds to fail with this error: >> >> ERROR: Command failed. See logs for output. >> >> If you have failed builds, please retrigger them in jenkins: >> http://jenkins.ovirt.org/gerrit_manual_trigger/ >> >> Nir >> _______________________________________________ >> Devel mailing list >> Devel@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel >> >> > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > _______________________________________________ > 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
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community
collaboration. > See how it works at redhat.com
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Nir Soffer" <nsoffer@redhat.com> Cc: "Piotr Kliczewski" <pkliczew@redhat.com>, "devel" <devel@ovirt.org> Sent: Friday, August 19, 2016 10:55:28 AM Subject: Re: [ovirt-devel] [VDSM] Build failure because missing ioprocess package in ovirt repos - solved
On Thu, Aug 18, 2016 at 6:03 PM, Sandro Bonazzola < sbonazzo@redhat.com > wrote:
On Thu, Aug 18, 2016 at 4:16 PM, Nir Soffer < nsoffer@redhat.com > wrote:
Merged, so I sent this to enable the ppc builds again: https://gerrit.ovirt.org/62551
Someone with access to jenkins should verify that this jobs works now.
will check tomorrow morning
Looks ok to me
Hi all, after a chat with Sandro (thanks to him for pointing this out), it looks to me that we have a similar issue for Vdsm. We could use the same fix as ioprocess (https://gerrit.ovirt.org/#/c/62464/), it seems simple and safe - or at least I can't think of any problem atm. Would everyone be OK with this? (please scroll down [quote intentionally kept] for more context)
On Thu, Aug 18, 2016 at 10:03 AM, Sandro Bonazzola < sbonazzo@redhat.com > wrote:
On Wed, Aug 17, 2016 at 6:21 PM, Nir Soffer < nsoffer@redhat.com > wrote:
I posted this patch, changing python-ioprocess to require ioprocess-version (instead of version-release). This seem to resolve the issue and is more correct, we don't really need ioprocess from the same build.
Please review https://gerrit.ovirt.org/62464
+1
Nir
On Wed, Aug 17, 2016 at 12:05 PM, Nir Soffer < nsoffer@redhat.com > wrote:
בתאריך 17 באוג׳ 2016 8:54 לפנה״צ, "Sandro Bonazzola" < sbonazzo@redhat.com > כתב:
The issue is different: both x86_64 and ppc64le builds python-ioprocess package so a newer python-ioprocess may come from ppc64le build not corresponding to an exact nvr on x86_64. Solution may be to chance the ioprocess build to drop the timestamp or make the ioprocess build a matrix job building from the same src.rpm. Another solution may be relax the nvr requirements in the python-ioprocess package to not require the exact nvr but only the same version. Another solution may be competely separate x86_64 and ppc64le repos.
I think the issue is the requiring the a version with the timestamp and git commit, it sould only require the same version.
On Sun, Aug 14, 2016 at 8:12 AM, Eyal Edri < eedri@redhat.com > wrote:
Was the broken build replaced by new one that is working?
On Fri, Aug 12, 2016 at 9:10 PM, Nir Soffer < nsoffer@redhat.com > wrote: > > Hi all, > > There was a broken build of ioprocess in ovirt repos, causing vdsm > all > vdsm master builds to fail with this error: > > ERROR: Command failed. See logs for output. > > If you have failed builds, please retrigger them in jenkins: > http://jenkins.ovirt.org/gerrit_manual_trigger/ > > Nir
-- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani
On Mon, Aug 22, 2016 at 2:25 PM, Francesco Romani <fromani@redhat.com> wrote:
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Nir Soffer" <nsoffer@redhat.com> Cc: "Piotr Kliczewski" <pkliczew@redhat.com>, "devel" <devel@ovirt.org> Sent: Friday, August 19, 2016 10:55:28 AM Subject: Re: [ovirt-devel] [VDSM] Build failure because missing ioprocess package in ovirt repos - solved
On Thu, Aug 18, 2016 at 6:03 PM, Sandro Bonazzola < sbonazzo@redhat.com
wrote:
On Thu, Aug 18, 2016 at 4:16 PM, Nir Soffer < nsoffer@redhat.com > wrote:
Merged, so I sent this to enable the ppc builds again: https://gerrit.ovirt.org/62551
Someone with access to jenkins should verify that this jobs works now.
will check tomorrow morning
Looks ok to me
Hi all,
after a chat with Sandro (thanks to him for pointing this out), it looks to me that we have a similar issue for Vdsm.
We could use the same fix as ioprocess (https://gerrit.ovirt.org/#/c/ 62464/), it seems simple and safe - or at least I can't think of any problem atm.
Would everyone be OK with this?
+1, I saw this issue is already failing Lago tests on experimental so I hope we can see it fixed soon. If it will cause issues in installing vdsm, we'll handle them as they appear.
(please scroll down [quote intentionally kept] for more context)
On Thu, Aug 18, 2016 at 10:03 AM, Sandro Bonazzola < sbonazzo@redhat.com
wrote:
On Wed, Aug 17, 2016 at 6:21 PM, Nir Soffer < nsoffer@redhat.com >
wrote:
I posted this patch, changing python-ioprocess to require ioprocess-version (instead of version-release). This seem to resolve the issue and is more correct, we don't really need ioprocess from the same build.
Please review https://gerrit.ovirt.org/62464
+1
Nir
On Wed, Aug 17, 2016 at 12:05 PM, Nir Soffer < nsoffer@redhat.com >
wrote:
בתאריך 17 באוג׳ 2016 8:54 לפנה״צ, "Sandro Bonazzola" < sbonazzo@redhat.com > כתב:
The issue is different: both x86_64 and ppc64le builds python-ioprocess package so a newer python-ioprocess may come from ppc64le build not corresponding to
an
exact nvr on x86_64. Solution may be to chance the ioprocess build to drop the timestamp or make the ioprocess build a matrix job building from the same src.rpm. Another solution may be relax the nvr requirements in the python-ioprocess package to not require the exact nvr but only the same version. Another solution may be competely separate x86_64 and ppc64le repos.
I think the issue is the requiring the a version with the timestamp and git commit, it sould only require the same version.
On Sun, Aug 14, 2016 at 8:12 AM, Eyal Edri < eedri@redhat.com >
wrote:
> > Was the broken build replaced by new one that is working? > > On Fri, Aug 12, 2016 at 9:10 PM, Nir Soffer < nsoffer@redhat.com
> wrote: >> >> Hi all, >> >> There was a broken build of ioprocess in ovirt repos, causing vdsm >> all >> vdsm master builds to fail with this error: >> >> ERROR: Command failed. See logs for output. >> >> If you have failed builds, please retrigger them in jenkins: >> http://jenkins.ovirt.org/gerrit_manual_trigger/ >> >> Nir
-- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
-- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)
----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "Francesco Romani" <fromani@redhat.com> Cc: "Dan Kenigsberg" <danken@redhat.com>, "Nir Soffer" <nsoffer@redhat.com>, "devel" <devel@ovirt.org> Sent: Monday, August 22, 2016 1:32:09 PM Subject: Re: [ovirt-devel] [VDSM] Build failure because missing ioprocess package in ovirt repos - solved
On Mon, Aug 22, 2016 at 2:25 PM, Francesco Romani <fromani@redhat.com> wrote:
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Nir Soffer" <nsoffer@redhat.com> Cc: "Piotr Kliczewski" <pkliczew@redhat.com>, "devel" <devel@ovirt.org> Sent: Friday, August 19, 2016 10:55:28 AM Subject: Re: [ovirt-devel] [VDSM] Build failure because missing ioprocess package in ovirt repos - solved
On Thu, Aug 18, 2016 at 6:03 PM, Sandro Bonazzola < sbonazzo@redhat.com
wrote:
On Thu, Aug 18, 2016 at 4:16 PM, Nir Soffer < nsoffer@redhat.com > wrote:
Merged, so I sent this to enable the ppc builds again: https://gerrit.ovirt.org/62551
Someone with access to jenkins should verify that this jobs works now.
will check tomorrow morning
Looks ok to me
Hi all,
after a chat with Sandro (thanks to him for pointing this out), it looks to me that we have a similar issue for Vdsm.
We could use the same fix as ioprocess (https://gerrit.ovirt.org/#/c/ 62464/), it seems simple and safe - or at least I can't think of any problem atm.
Would everyone be OK with this?
+1, I saw this issue is already failing Lago tests on experimental so I hope we can see it fixed soon. If it will cause issues in installing vdsm, we'll handle them as they appear.
here it is, please review: https://gerrit.ovirt.org/62672 Thanks and bests, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani
participants (4)
-
Eyal Edri -
Francesco Romani -
Nir Soffer -
Sandro Bonazzola