----- Original Message ----- > From: "Dan Kenigsberg" <dan...@redhat.com> > To: ee...@redhat.com > Cc: vdsm-patches@lists.fedorahosted.org, asegu...@redhat.com > Sent: Monday, November 18, 2013 12:14:52 AM > Subject: Re: [oVirt Jenkins] vdsm_create_rpms - Build # 812 - Failure! > > On Sun, Nov 17, 2013 at 03:53:38PM +0000, Jenkins ci oVirt Server wrote: > > Project: http://jenkins.ovirt.org/job/vdsm_create_rpms/ > > Build: http://jenkins.ovirt.org/job/vdsm_create_rpms/812/ > > Build Number: 812 > > Build Status: Failure > > Triggered By: Started by an SCM change > > > > ------------------------------------- > > Changes Since Last Success: > > ------------------------------------- > > Changes for Build #812 > > [Antoni S. Puimedon] Added missing python modules to the configure.ac > > checks > > http://jenkins.ovirt.org/job/vdsm_create_rpms/812/label=fedora18/console > has > > checking python module: pyinotify... no > configure: error: failed to find required module pyinotify > > even though we explictly have > > Requires: python-inotify > > in our spec. How could this happen? Is python-inotify installed on the > amazon-f18 slave? >
it happens since this job creates vdsm rpm and doesn't installs it. i sent patch for puppet to ensure python-inotify will be installed on all slaves. _______________________________________________ vdsm-patches mailing list vdsm-patches@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-patches
