Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
----- Original Message -----
From: "Timothy Asir Jeyasingh" <tjeyasin@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Dusmant-staff" <dusmant-staff@redhat.com>, devel@ovirt.org Sent: Wednesday, March 25, 2015 9:38:06 AM Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
Please give me one more day time. The fix patch is waiting for review.
I have to say this is highly unorthodox timothy, to knowingly keep CI broken due to missing deps for another full day, rather then reverting the patch that caused this. this blocks several flows, including QA testing for 3.6.0 initial builds and in addition failing CI jobs. Please explain why the patch can't be reverted ASAP and how does justified keeping the CI broken & postponing release to QE. Eyal.
Regards, Tim
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: devel@ovirt.org, "Dan Kenigsberg" <danken@redhat.com>, "Timothy Asir Jeyasingh" <tjeyasin@redhat.com>, "Balamurugan Arumugam" <barumuga@redhat.com> Sent: Wednesday, March 25, 2015 12:42:37 PM Subject: [URGENT][ACTION REQUIRED] please fix VDSM requirements
Hi, we still have repository closure error and CI jobs broken by the blivet requirement introduced with https://gerrit.ovirt.org/35498 on Mar 18.
The merged patch https://gerrit.ovirt.org/38974 requiring it only at runtime is not enough to fix CI and repository issues. Please either revert the blivet requirement at all or try to get https://gerrit.ovirt.org/38942 in as soon as possible. It's one week since last time VDSM has been successfully tested by CI, please address the issue. Thanks,
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Can i just send a fix patch to fix the spec file only which will fix the build related issues. (Just a one line fix) So that the complete fix (38942) can be merged later on. There are few ovirt patches which are using this vdsm function got merged already. Regards, Tim ----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "Timothy Asir Jeyasingh" <tjeyasin@redhat.com> Cc: "Sandro Bonazzola" <sbonazzo@redhat.com>, "Dusmant-staff" <dusmant-staff@redhat.com>, devel@ovirt.org, "Dan Kenigsberg" <danken@redhat.com>, "Gil Klein" <gklein@redhat.com>, "Itamar Heim" <iheim@redhat.com>, "Sahina Bose" <sabose@redhat.com>, "infra" <infra@ovirt.org> Sent: Wednesday, March 25, 2015 3:42:51 PM Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
----- Original Message -----
From: "Timothy Asir Jeyasingh" <tjeyasin@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Dusmant-staff" <dusmant-staff@redhat.com>, devel@ovirt.org Sent: Wednesday, March 25, 2015 9:38:06 AM Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
Please give me one more day time. The fix patch is waiting for review.
I have to say this is highly unorthodox timothy, to knowingly keep CI broken due to missing deps for another full day, rather then reverting the patch that caused this. this blocks several flows, including QA testing for 3.6.0 initial builds and in addition failing CI jobs.
Please explain why the patch can't be reverted ASAP and how does justified keeping the CI broken & postponing release to QE.
Eyal.
Regards, Tim
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: devel@ovirt.org, "Dan Kenigsberg" <danken@redhat.com>, "Timothy Asir Jeyasingh" <tjeyasin@redhat.com>, "Balamurugan Arumugam" <barumuga@redhat.com> Sent: Wednesday, March 25, 2015 12:42:37 PM Subject: [URGENT][ACTION REQUIRED] please fix VDSM requirements
Hi, we still have repository closure error and CI jobs broken by the blivet requirement introduced with https://gerrit.ovirt.org/35498 on Mar 18.
The merged patch https://gerrit.ovirt.org/38974 requiring it only at runtime is not enough to fix CI and repository issues. Please either revert the blivet requirement at all or try to get https://gerrit.ovirt.org/38942 in as soon as possible. It's one week since last time VDSM has been successfully tested by CI, please address the issue. Thanks,
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
----- Original Message -----
From: "Timothy Asir Jeyasingh" <tjeyasin@redhat.com> To: "Eyal Edri" <eedri@redhat.com> Cc: "Sandro Bonazzola" <sbonazzo@redhat.com>, "Dusmant-staff" <dusmant-staff@redhat.com>, devel@ovirt.org, "Dan Kenigsberg" <danken@redhat.com>, "Gil Klein" <gklein@redhat.com>, "Itamar Heim" <iheim@redhat.com>, "Sahina Bose" <sabose@redhat.com>, "infra" <infra@ovirt.org> Sent: Wednesday, March 25, 2015 12:29:25 PM Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
Can i just send a fix patch to fix the spec file only which will fix the build related issues. (Just a one line fix)
So that the complete fix (38942) can be merged later on. There are few ovirt patches which are using this vdsm function got merged already.
Yes. as long as it fixes the repoclosure issue and all required RPMs are available in currently released EL7.
Regards, Tim
----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "Timothy Asir Jeyasingh" <tjeyasin@redhat.com> Cc: "Sandro Bonazzola" <sbonazzo@redhat.com>, "Dusmant-staff" <dusmant-staff@redhat.com>, devel@ovirt.org, "Dan Kenigsberg" <danken@redhat.com>, "Gil Klein" <gklein@redhat.com>, "Itamar Heim" <iheim@redhat.com>, "Sahina Bose" <sabose@redhat.com>, "infra" <infra@ovirt.org> Sent: Wednesday, March 25, 2015 3:42:51 PM Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
----- Original Message -----
From: "Timothy Asir Jeyasingh" <tjeyasin@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Dusmant-staff" <dusmant-staff@redhat.com>, devel@ovirt.org Sent: Wednesday, March 25, 2015 9:38:06 AM Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
Please give me one more day time. The fix patch is waiting for review.
I have to say this is highly unorthodox timothy, to knowingly keep CI broken due to missing deps for another full day, rather then reverting the patch that caused this. this blocks several flows, including QA testing for 3.6.0 initial builds and in addition failing CI jobs.
Please explain why the patch can't be reverted ASAP and how does justified keeping the CI broken & postponing release to QE.
Eyal.
Regards, Tim
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: devel@ovirt.org, "Dan Kenigsberg" <danken@redhat.com>, "Timothy Asir Jeyasingh" <tjeyasin@redhat.com>, "Balamurugan Arumugam" <barumuga@redhat.com> Sent: Wednesday, March 25, 2015 12:42:37 PM Subject: [URGENT][ACTION REQUIRED] please fix VDSM requirements
Hi, we still have repository closure error and CI jobs broken by the blivet requirement introduced with https://gerrit.ovirt.org/35498 on Mar 18.
The merged patch https://gerrit.ovirt.org/38974 requiring it only at runtime is not enough to fix CI and repository issues. Please either revert the blivet requirement at all or try to get https://gerrit.ovirt.org/38942 in as soon as possible. It's one week since last time VDSM has been successfully tested by CI, please address the issue. Thanks,
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Patch sent to upstream: https://gerrit.ovirt.org/#/c/39132/ Regards, Tim ----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "Timothy Asir Jeyasingh" <tjeyasin@redhat.com> Cc: "Sandro Bonazzola" <sbonazzo@redhat.com>, "Dusmant-staff" <dusmant-staff@redhat.com>, devel@ovirt.org, "Dan Kenigsberg" <danken@redhat.com>, "Gil Klein" <gklein@redhat.com>, "Itamar Heim" <iheim@redhat.com>, "Sahina Bose" <sabose@redhat.com>, "infra" <infra@ovirt.org> Sent: Wednesday, March 25, 2015 4:06:28 PM Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
----- Original Message -----
From: "Timothy Asir Jeyasingh" <tjeyasin@redhat.com> To: "Eyal Edri" <eedri@redhat.com> Cc: "Sandro Bonazzola" <sbonazzo@redhat.com>, "Dusmant-staff" <dusmant-staff@redhat.com>, devel@ovirt.org, "Dan Kenigsberg" <danken@redhat.com>, "Gil Klein" <gklein@redhat.com>, "Itamar Heim" <iheim@redhat.com>, "Sahina Bose" <sabose@redhat.com>, "infra" <infra@ovirt.org> Sent: Wednesday, March 25, 2015 12:29:25 PM Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
Can i just send a fix patch to fix the spec file only which will fix the build related issues. (Just a one line fix)
So that the complete fix (38942) can be merged later on. There are few ovirt patches which are using this vdsm function got merged already.
Yes. as long as it fixes the repoclosure issue and all required RPMs are available in currently released EL7.
Regards, Tim
----- Original Message -----
From: "Eyal Edri" <eedri@redhat.com> To: "Timothy Asir Jeyasingh" <tjeyasin@redhat.com> Cc: "Sandro Bonazzola" <sbonazzo@redhat.com>, "Dusmant-staff" <dusmant-staff@redhat.com>, devel@ovirt.org, "Dan Kenigsberg" <danken@redhat.com>, "Gil Klein" <gklein@redhat.com>, "Itamar Heim" <iheim@redhat.com>, "Sahina Bose" <sabose@redhat.com>, "infra" <infra@ovirt.org> Sent: Wednesday, March 25, 2015 3:42:51 PM Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
----- Original Message -----
From: "Timothy Asir Jeyasingh" <tjeyasin@redhat.com> To: "Sandro Bonazzola" <sbonazzo@redhat.com> Cc: "Dusmant-staff" <dusmant-staff@redhat.com>, devel@ovirt.org Sent: Wednesday, March 25, 2015 9:38:06 AM Subject: Re: [ovirt-devel] [URGENT][ACTION REQUIRED] please fix VDSM requirements
Please give me one more day time. The fix patch is waiting for review.
I have to say this is highly unorthodox timothy, to knowingly keep CI broken due to missing deps for another full day, rather then reverting the patch that caused this. this blocks several flows, including QA testing for 3.6.0 initial builds and in addition failing CI jobs.
Please explain why the patch can't be reverted ASAP and how does justified keeping the CI broken & postponing release to QE.
Eyal.
Regards, Tim
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: devel@ovirt.org, "Dan Kenigsberg" <danken@redhat.com>, "Timothy Asir Jeyasingh" <tjeyasin@redhat.com>, "Balamurugan Arumugam" <barumuga@redhat.com> Sent: Wednesday, March 25, 2015 12:42:37 PM Subject: [URGENT][ACTION REQUIRED] please fix VDSM requirements
Hi, we still have repository closure error and CI jobs broken by the blivet requirement introduced with https://gerrit.ovirt.org/35498 on Mar 18.
The merged patch https://gerrit.ovirt.org/38974 requiring it only at runtime is not enough to fix CI and repository issues. Please either revert the blivet requirement at all or try to get https://gerrit.ovirt.org/38942 in as soon as possible. It's one week since last time VDSM has been successfully tested by CI, please address the issue. Thanks,
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
participants (2)
-
Eyal Edri -
Timothy Asir Jeyasingh