From bugzilla at redhat.com Mon Jul 1 06:04:34 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 01 Jul 2019 06:04:34 +0000 Subject: [Gluster-infra] [Bug 1514369] Make Gluster code history available with cregit In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1514369 Yaniv Kaul changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |WONTFIX Last Closed| |2019-07-01 06:04:34 --- Comment #1 from Yaniv Kaul --- Unlikely to happen if did not happen by now. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 1 06:04:56 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 01 Jul 2019 06:04:56 +0000 Subject: [Gluster-infra] [Bug 1516198] Create jenkins@build.gluster.org and send to /dev/null In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1516198 Yaniv Kaul changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |WONTFIX Last Closed| |2019-07-01 06:04:56 --- Comment #1 from Yaniv Kaul --- Closing old BZs. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 1 06:07:48 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 01 Jul 2019 06:07:48 +0000 Subject: [Gluster-infra] [Bug 1503529] Investigate having a mirror of download server In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1503529 Yaniv Kaul changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mscherer at redhat.c | |om) --- Comment #2 from Yaniv Kaul --- Still relevant? -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 1 06:08:12 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 01 Jul 2019 06:08:12 +0000 Subject: [Gluster-infra] [Bug 1641021] gd2-smoke do not seems to clean itself after a crash In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1641021 Yaniv Kaul changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mscherer at redhat.c | |om) --- Comment #2 from Yaniv Kaul --- Patch merged. Can we close this? -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 1 08:07:51 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 01 Jul 2019 08:07:51 +0000 Subject: [Gluster-infra] [Bug 1503529] Investigate having a mirror of download server In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1503529 M. Scherer changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(mscherer at redhat.c | |om) | --- Comment #3 from M. Scherer --- Still relevant but I want first make sure tarball generation is automated before. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 1 09:53:59 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 01 Jul 2019 09:53:59 +0000 Subject: [Gluster-infra] [Bug 1516198] Create jenkins@build.gluster.org and send to /dev/null In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1516198 M. Scherer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mscherer at redhat.com Resolution|WONTFIX |CURRENTRELEASE --- Comment #2 from M. Scherer --- This was done, so it should't be closed won't fix. -- You are receiving this mail because: You are on the CC list for the bug. From mscherer at redhat.com Thu Jul 4 16:06:05 2019 From: mscherer at redhat.com (Michael Scherer) Date: Thu, 04 Jul 2019 18:06:05 +0200 Subject: [Gluster-infra] Migration of the builders to Fedora 30 Message-ID: <1af917bd44ba629a663014eaee0a24208b422aca.camel@redhat.com> Hi, I have upgraded for testing some of the builder to F30 (because F28 is EOL and people did request newer version of stuff), and I was a bit surprised to see the result of the test of the jobs. So we have 10 jobs that run on those builders. 5 jobs run without trouble: - python-lint - clang-scan - clang-format - 32-bit-build-smoke - bugs-summary 1 is disabled, tsan. I didn't try to run it. 4 fails: - python-compliance - fedora-smoke - gluster-csi-containers - glusterd2-containers The job python-compliance fail like this: https://build.gluster.org/job/python-compliance/5813/ The fedora-smoke job, who is building on newer fedora (so newer gcc), is failling too: https://build.gluster.org/job/fedora-smoke/6753/console Gluster-csi-containers is having trouble to run https://build.gluster.org/job/gluster-csi-containers/304/console but before, it did fail with "out of space": https://build.gluster.org/job/gluster-csi-containers/303/console and it also fail (well, should fail) with this: 16:51:07 make: *** No targets specified and no makefile found. Stop. which is indeed not present in the git repo, so this seems like the job is unmaintained. The last one to fail is glusterd2-containers: https://build.gluster.org/job/glusterd2-containers/323/console This one is fun, because it fail, but appear as ok on jenkins. It fail because of some ansible issue, due to newer Fedora. So, since we need to switch, here is what I would recommend: - switch the working job to F30 - wait 2 weeks, and switch fedora-smoke and python-compliance to F30. This will force someone to fix the problem. - drop the non fixed containers jobs, unless someone fix them, in 1 month. -- Michael Scherer Sysadmin, Community Infrastructure -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From atumball at redhat.com Thu Jul 4 16:25:19 2019 From: atumball at redhat.com (Amar Tumballi Suryanarayan) Date: Thu, 4 Jul 2019 21:55:19 +0530 Subject: [Gluster-infra] [Gluster-devel] Migration of the builders to Fedora 30 In-Reply-To: <1af917bd44ba629a663014eaee0a24208b422aca.camel@redhat.com> References: <1af917bd44ba629a663014eaee0a24208b422aca.camel@redhat.com> Message-ID: On Thu, Jul 4, 2019 at 9:37 PM Michael Scherer wrote: > Hi, > > I have upgraded for testing some of the builder to F30 (because F28 is > EOL and people did request newer version of stuff), and I was a bit > surprised to see the result of the test of the jobs. > > So we have 10 jobs that run on those builders. > > 5 jobs run without trouble: > - python-lint > - clang-scan > - clang-format > - 32-bit-build-smoke > - bugs-summary > > 1 is disabled, tsan. I didn't try to run it. > > 4 fails: > - python-compliance > OK to run, but skip voting, so we can eventually (soonish) fix this. > - fedora-smoke > Ideally we should soon fix it. Effort is ON. We have a bug for this: https://bugzilla.redhat.com/show_bug.cgi?id=1693385#c5 > - gluster-csi-containers > - glusterd2-containers > > OK to drop for now. > The job python-compliance fail like this: > https://build.gluster.org/job/python-compliance/5813/ > > The fedora-smoke job, who is building on newer fedora (so newer gcc), > is failling too: > https://build.gluster.org/job/fedora-smoke/6753/console > > Gluster-csi-containers is having trouble to run > https://build.gluster.org/job/gluster-csi-containers/304/console > https://bugzilla.redhat.com/show_bug.cgi?id=1693385#c5 > but before, it did fail with "out of space": > https://build.gluster.org/job/gluster-csi-containers/303/console > > and it also fail (well, should fail) with this: > 16:51:07 make: *** No targets specified and no makefile found. Stop. > > which is indeed not present in the git repo, so this seems like the job is > unmaintained. > > > The last one to fail is glusterd2-containers: > > https://build.gluster.org/job/glusterd2-containers/323/console > > This one is fun, because it fail, but appear as ok on jenkins. It fail > because of some ansible issue, due to newer Fedora. > > So, since we need to switch, here is what I would recommend: > - switch the working job to F30 > - wait 2 weeks, and switch fedora-smoke and python-compliance to F30. This > will force someone to fix the problem. > - drop the non fixed containers jobs, unless someone fix them, in 1 month. > Looks like a good plan. > > -- > Michael Scherer > Sysadmin, Community Infrastructure > > > > _______________________________________________ > > Community Meeting Calendar: > > APAC Schedule - > Every 2nd and 4th Tuesday at 11:30 AM IST > Bridge: https://bluejeans.com/836554017 > > NA/EMEA Schedule - > Every 1st and 3rd Tuesday at 01:00 PM EDT > Bridge: https://bluejeans.com/486278655 > > Gluster-devel mailing list > Gluster-devel at gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-devel > > -- Amar Tumballi (amarts) -------------- next part -------------- An HTML attachment was scrubbed... URL: From bugzilla at redhat.com Thu Jul 4 16:42:15 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 04 Jul 2019 16:42:15 +0000 Subject: [Gluster-infra] [Bug 1641021] gd2-smoke do not seems to clean itself after a crash In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1641021 Michael S. changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED CC| |misc at zarb.org Resolution|--- |CURRENTRELEASE Last Closed| |2019-07-04 16:42:15 --- Comment #3 from Michael S. --- Yup -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 8 02:40:39 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 08 Jul 2019 02:40:39 +0000 Subject: [Gluster-infra] [Bug 1720453] Unable to access review.gluster.org In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1720453 Deepshikha khandelwal changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED CC| |dkhandel at redhat.com Resolution|--- |CURRENTRELEASE Last Closed| |2019-07-08 02:40:39 --- Comment #4 from Deepshikha khandelwal --- It is fixed now. Closing it. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 8 04:31:17 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 08 Jul 2019 04:31:17 +0000 Subject: [Gluster-infra] [Bug 1727723] New: Build+Packaging Automation Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1727723 Bug ID: 1727723 Summary: Build+Packaging Automation Product: GlusterFS Version: mainline Status: NEW Component: project-infrastructure Assignee: bugs at gluster.org Reporter: spamecha at redhat.com CC: bugs at gluster.org, gluster-infra at gluster.org Target Milestone: --- Classification: Community Description of problem: Currently for every release, packages for Debian(9 & 10) and Ubuntu(bionic,cosmic,eoan,disco,xenial) need to be built manually. To automate this process in the same way as fedora and centos are triggered. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 8 04:29:41 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 08 Jul 2019 04:29:41 +0000 Subject: [Gluster-infra] [Bug 1727722] New: Build+Packaging Automation Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1727722 Bug ID: 1727722 Summary: Build+Packaging Automation Product: GlusterFS Version: mainline Status: NEW Component: project-infrastructure Assignee: bugs at gluster.org Reporter: spamecha at redhat.com CC: bugs at gluster.org, gluster-infra at gluster.org Target Milestone: --- Classification: Community Description of problem: Currently for every release, packages for Debian(9 & 10) and Ubuntu(bionic,cosmic,eoan,disco,xenial) need to be built manually. To automate this process in the same way as fedora and centos are triggered. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 8 04:40:25 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 08 Jul 2019 04:40:25 +0000 Subject: [Gluster-infra] [Bug 1727727] New: Build+Packaging Automation Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1727727 Bug ID: 1727727 Summary: Build+Packaging Automation Product: GlusterFS Version: mainline Status: NEW Component: project-infrastructure Assignee: bugs at gluster.org Reporter: spamecha at redhat.com CC: bugs at gluster.org, gluster-infra at gluster.org Target Milestone: --- Classification: Community Description of problem: Currently for every release, packages for Debian(9 & 10) and Ubuntu(bionic,cosmic,eoan,disco,xenial) need to be built manually. To automate this process in the same way as fedora and centos are triggered. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 8 04:32:20 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 08 Jul 2019 04:32:20 +0000 Subject: [Gluster-infra] [Bug 1727724] New: Build+Packaging Automation Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1727724 Bug ID: 1727724 Summary: Build+Packaging Automation Product: GlusterFS Version: mainline Status: NEW Component: project-infrastructure Assignee: bugs at gluster.org Reporter: spamecha at redhat.com CC: bugs at gluster.org, gluster-infra at gluster.org Target Milestone: --- Classification: Community Description of problem: Currently for every release, packages for Debian(9 & 10) and Ubuntu(bionic,cosmic,eoan,disco,xenial) need to be built manually. To automate this process in the same way as fedora and centos are triggered. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 9 05:02:41 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 09 Jul 2019 05:02:41 +0000 Subject: [Gluster-infra] [Bug 1728120] New: Not able to access core https://build.gluster.org/job/regression-test-with-multiplex/1402/consoleFull Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1728120 Bug ID: 1728120 Summary: Not able to access core https://build.gluster.org/job/regression-test-with-mul tiplex/1402/consoleFull Product: GlusterFS Version: mainline Status: NEW Component: project-infrastructure Assignee: bugs at gluster.org Reporter: moagrawa at redhat.com CC: bugs at gluster.org, gluster-infra at gluster.org Target Milestone: --- Classification: Community Description of problem: Not able to access the core from the link https://build.gluster.org/job/regression-test-with-multiplex/1402/consoleFull Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 9 10:50:39 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 09 Jul 2019 10:50:39 +0000 Subject: [Gluster-infra] [Bug 1728120] Not able to access core https://build.gluster.org/job/regression-test-with-multiplex/1402/consoleFull In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1728120 M. Scherer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mscherer at redhat.com --- Comment #1 from M. Scherer --- 20:29:51 + scp -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -i '' /archives/archived_builds/build-install-regression-test-with-multiplex-1402.tar.bz2 _logs-collector at logs.aws.gluster.org:/var/www/glusterfs-logs/regression-test-with-multiplex-1402.bz2 20:29:51 Warning: Identity file not accessible: No such file or directory. 20:29:51 Warning: Permanently added 'logs.aws.gluster.org,18.219.45.211' (ECDSA) to the list of known hosts. 20:29:51 Permission denied (publickey,gssapi-keyex,gssapi-with-mic). seems there is a key that wasn't deployed properly, I am looking at it. In the mean time, I ill copy the file manually. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 9 10:55:03 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 09 Jul 2019 10:55:03 +0000 Subject: [Gluster-infra] [Bug 1728120] Not able to access core https://build.gluster.org/job/regression-test-with-multiplex/1402/consoleFull In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1728120 --- Comment #2 from M. Scherer --- Seems that this job never worked, there is no binding for the ssh key. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 9 11:37:16 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 09 Jul 2019 11:37:16 +0000 Subject: [Gluster-infra] [Bug 1728120] Not able to access core https://build.gluster.org/job/regression-test-with-multiplex/1402/consoleFull In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1728120 Deepshikha khandelwal changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dkhandel at redhat.com --- Comment #3 from Deepshikha khandelwal --- Yes. Log thing never worked for this job. I will add the credential binding for this job. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 9 11:41:43 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 09 Jul 2019 11:41:43 +0000 Subject: [Gluster-infra] [Bug 1728120] Not able to access core https://build.gluster.org/job/regression-test-with-multiplex/1402/consoleFull In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1728120 --- Comment #4 from Deepshikha khandelwal --- Fix: https://review.gluster.org/#/c/build-jobs/+/23019/ -- You are receiving this mail because: You are on the CC list for the bug. From atumball at redhat.com Tue Jul 9 12:03:06 2019 From: atumball at redhat.com (Amar Tumballi Suryanarayan) Date: Tue, 9 Jul 2019 17:33:06 +0530 Subject: [Gluster-infra] [Gluster-devel] Migration of the builders to Fedora 30 In-Reply-To: References: <1af917bd44ba629a663014eaee0a24208b422aca.camel@redhat.com> Message-ID: On Thu, Jul 4, 2019 at 9:55 PM Amar Tumballi Suryanarayan < atumball at redhat.com> wrote: > > > On Thu, Jul 4, 2019 at 9:37 PM Michael Scherer > wrote: > >> Hi, >> >> I have upgraded for testing some of the builder to F30 (because F28 is >> EOL and people did request newer version of stuff), and I was a bit >> surprised to see the result of the test of the jobs. >> >> So we have 10 jobs that run on those builders. >> >> 5 jobs run without trouble: >> - python-lint >> - clang-scan >> - clang-format >> - 32-bit-build-smoke >> - bugs-summary >> >> 1 is disabled, tsan. I didn't try to run it. >> >> 4 fails: >> - python-compliance >> > > OK to run, but skip voting, so we can eventually (soonish) fix this. > > >> - fedora-smoke >> > > Ideally we should soon fix it. Effort is ON. We have a bug for this: > https://bugzilla.redhat.com/show_bug.cgi?id=1693385#c5 > Can we re-run this on latest master? I think we are ready for fedora-smoke on fedora30 on latest master. > >> - gluster-csi-containers >> - glusterd2-containers >> >> > OK to drop for now. > > >> The job python-compliance fail like this: >> https://build.gluster.org/job/python-compliance/5813/ >> >> The fedora-smoke job, who is building on newer fedora (so newer gcc), >> is failling too: >> https://build.gluster.org/job/fedora-smos some new vol option that ought >> to be set?ke/6753/console >> >> >> Gluster-csi-containers is having trouble to run >> https://build.gluster.org/job/gluster-csi-containers/304/console >> https://bugzilla.redhat.com/show_bug.cgi?id=1693385#c5 >> but before, it did fail with "out of space": >> https://build.gluster.org/job/gluster-csi-containers/303/console >> >> and it also fail (well, should fail) with this: >> 16:51:07 make: *** No targets specified and no makefile found. Stop. >> >> which is indeed not present in the git repo, so this seems like the job >> is unmaintained. >> >> >> The last one to fail is glusterd2-containers: >> >> https://build.gluster.org/job/glusterd2-containers/323/console >> >> This one is fun, because it fail, but appear as ok on jenkins. It fail >> because of some ansible issue, due to newer Fedora. >> >> So, since we need to switch, here is what I would recommend: >> - switch the working job to F30 >> - wait 2 weeks, and switch fedora-smoke and python-compliance to F30. >> This will force someone to fix the problem. >> - drop the non fixed containers jobs, unless someone fix them, in 1 month. >> > > Looks like a good plan. > > >> >> -- >> Michael Scherer >> Sysadmin, Community Infrastructure >> >> >> >> _______________________________________________ >> >> Community Meeting Calendar: >> >> APAC Schedule - >> Every 2nd and 4th Tuesday at 11:30 AM IST >> Bridge: https://bluejeans.com/836554017 >> >> NA/EMEA Schedule - >> Every 1st and 3rd Tuesday at 01:00 PM EDT >> Bridge: https://bluejeans.com/486278655 >> >> Gluster-devel mailing list >> Gluster-devel at gluster.org >> https://lists.gluster.org/mailman/listinfo/gluster-devel >> >> > > -- > Amar Tumballi (amarts) > -- Amar Tumballi (amarts) -------------- next part -------------- An HTML attachment was scrubbed... URL: From sankarshan.mukhopadhyay at gmail.com Wed Jul 10 04:49:31 2019 From: sankarshan.mukhopadhyay at gmail.com (Sankarshan Mukhopadhyay) Date: Wed, 10 Jul 2019 10:19:31 +0530 Subject: [Gluster-infra] New workflow proposal for glusterfs repo In-Reply-To: References:

Message-ID: Following up - what is the agreed upon plan here? On Tue, Jun 25, 2019 at 11:20 AM Amar Tumballi Suryanarayan wrote: > > Adding gluster-devel ML. > > Only concern to my earlier proposal was not making regression runs wait for reviews, but to be triggered automatically after successful smoke. > > The ask was to put burden on machines than on developers, which I agree to start with. Lets watch the expenses due to this change for a month once it gets implemented, and then take stock of the situation. For now, lets reduce one more extra work for developers, ie, marking Verified flag. > > On Tue, Jun 25, 2019 at 11:01 AM Sankarshan Mukhopadhyay wrote: >> >> Amar, can you bring about an agreement/decision on this so that we can >> make progress? >> > > So, My take is: > > Lets make serialized smoke + regression a reality. It may add to overall time, but if there are failures, this has potential to reduce overall machine usage... for a successful patch, the extra few minutes at present doesn't harm as many of our review avg time is around a week. > > >> >> On Tue, Jun 25, 2019 at 10:55 AM Deepshikha Khandelwal >> wrote: >> > >> > >> > >> > On Mon, Jun 24, 2019 at 5:30 PM Sankarshan Mukhopadhyay wrote: >> >> >> >> Checking back on this - do we need more voices or, amendments to >> >> Amar's original proposal before we scope the implementation? >> >> >> >> I read Amar's proposal as desiring an outcome where the journey of a >> >> valid/good patch through the test flows is fast and efficient. > > > Absolutely! This is critical for us to be inclusive community. > >> >> >> >> >> On Wed, Jun 12, 2019 at 11:58 PM Raghavendra Talur wrote: >> >> > >> >> > >> >> > >> >> > On Wed, Jun 12, 2019, 1:56 PM Atin Mukherjee wrote: >> >> >> >> >> >> >> >> >> >> >> >> On Wed, 12 Jun 2019 at 18:04, Amar Tumballi Suryanarayan wrote: >> >> >>> >> >> >>> >> >> >>> Few bullet points: >> >> >>> >> >> >>> * Let smoke job sequentially for below, and if successful, in parallel for others. >> >> >>> - Sequential: >> >> >>> -- clang-format check >> >> >>> -- compare-bugzilla-version-git-branch >> >> >>> -- bugzilla-post >> >> >>> -- comment-on-issue >> >> >>> -- fedora-smoke (mainly don't want warning). >> >> >> >> >> >> >> >> >> +1 >> >> >> >> >> >>> - Parallel >> >> >>> -- all devrpm jobs >> >> >>> -- 32bit smoke >> >> >>> -- freebsd-smoke >> >> >>> -- smoke >> >> >>> -- strfmt_errors >> >> >>> -- python-lint, and shellcheck. >> >> >> >> >> >> >> >> >> I?m sure there must be a reason but would like to know that why do they need to be parallel? Can?t we have them sequentially to have similar benefits of the resource utilisation like above? Or are all these individual jobs are time consuming such that having them sequentially will lead the overall smoke job to consume much longer? > > > Most of these are doing the same thing, make dist, make install, make rpms. but on different arch and with different flags. To start with, we can do these also sequentially. That way, infra team needn't worry about some parallel, some sequential jobs. > >> >> >> >> >> >> >>> >> >> >>> * Remove Verified flag. No point in one more extra button which users need to click, anyways CentOS regression is considered as 'Verification'. >> >> > >> >> > >> >> > The requirement of verified flag by patch owner for regression to run was added because the number of Jenkins machines we had were few and patches being uploaded were many. >> >> >> >> However, do we consider that at present time the situation has >> >> improved to consider the change Amar asks for? >> >> >> >> > >> >> >>> >> >> >>> * In a normal flow, let CentOS regression which is running after 'Verified' vote, be triggered on first 'successful' +1 reviewed vote. >> >> >> >> >> >> >> >> >> As I believe some reviewers/maintainers (including me) would like to see the regression vote to put a +1/+2 in most of the patches until and unless they are straight forward ones. So although with this you?re reducing the burden of one extra click from the patch owner, but on the other way you?re introducing the same burden on the reviewers who would like to check the regression vote. IMHO, I don?t see much benefits in implementing this. >> >> > >> >> > >> >> > Agree with Atin here. Burden should be on machines before people. Reviewers prefer to look at patches that have passed regression. >> >> > >> >> > In github heketi, we have configured regression to run on all patches that are submitted by heketi developer group. If such configuration is possible in gerrit+Jenkins, we should definitely do it that way. >> >> > >> >> > For patches that are submitted by someone outside of the developer group, a maintainer should verify that the patch doesn't do anything harmful and mark the regression to run. >> >> > >> >> >> >> Deepshikha, is the above change feasible in the summation of Amar's proposal? >> > >> > Yes, I'm planning to implement the regression & flag related changes initially if everyone agrees. >> >> >> >> > > > I would say, lets get started on these changes. > > Regards, > Amar > >> >> >> >>> >> >> >>> * For those patches which got pushed to system to just 'validate' behavior, to run sample tests, WIP patches, continue to support 'recheck centos' comment message, so we can run without any vote. Let it not be the norm. >> >> >>> >> >> >>> >> >> >>> With this, I see that we can reduce smoke failures utilize 90% less resources for a patch which would fail smoke anyways. (ie, 95% of the smoke failures would be caught in first 10% of the resource, and time). >> >> >>> >> >> >>> Also we can reduce number of regression running, as review is mandatory to run regression. >> >> >>> >> >> >>> These are just suggestions, happy to discuss more on these. >> >> _______________________________________________ >> >> Gluster-infra mailing list >> >> Gluster-infra at gluster.org >> >> https://lists.gluster.org/mailman/listinfo/gluster-infra >> >> >> >> -- >> sankarshan mukhopadhyay >> >> _______________________________________________ >> Gluster-infra mailing list >> Gluster-infra at gluster.org >> https://lists.gluster.org/mailman/listinfo/gluster-infra > > > > -- > Amar Tumballi (amarts) -- sankarshan mukhopadhyay From dkhandel at redhat.com Wed Jul 10 07:06:01 2019 From: dkhandel at redhat.com (Deepshikha Khandelwal) Date: Wed, 10 Jul 2019 12:36:01 +0530 Subject: [Gluster-infra] [Gluster-devel] Migration of the builders to Fedora 30 In-Reply-To: References: <1af917bd44ba629a663014eaee0a24208b422aca.camel@redhat.com> Message-ID: On Tue, Jul 9, 2019 at 5:34 PM Amar Tumballi Suryanarayan < atumball at redhat.com> wrote: > > > On Thu, Jul 4, 2019 at 9:55 PM Amar Tumballi Suryanarayan < > atumball at redhat.com> wrote: > >> >> >> On Thu, Jul 4, 2019 at 9:37 PM Michael Scherer >> wrote: >> >>> Hi, >>> >>> I have upgraded for testing some of the builder to F30 (because F28 is >>> EOL and people did request newer version of stuff), and I was a bit >>> surprised to see the result of the test of the jobs. >>> >>> So we have 10 jobs that run on those builders. >>> >>> 5 jobs run without trouble: >>> - python-lint >>> - clang-scan >>> - clang-format >>> - 32-bit-build-smoke >>> - bugs-summary >>> >>> 1 is disabled, tsan. I didn't try to run it. >>> >>> 4 fails: >>> - python-compliance >>> >> >> OK to run, but skip voting, so we can eventually (soonish) fix this. >> >> >>> - fedora-smoke >>> >> >> Ideally we should soon fix it. Effort is ON. We have a bug for this: >> https://bugzilla.redhat.com/show_bug.cgi?id=1693385#c5 >> > > Can we re-run this on latest master? I think we are ready for > fedora-smoke on fedora30 on latest master. > I have triggered a test run https://build.gluster.org/job/fedora-smoke/6817/console to fedora-smoke job on fedora30 builders. It is running on latest master. > > >> >>> - gluster-csi-containers >>> - glusterd2-containers >>> >>> >> OK to drop for now. >> > I have disabled these two container jobs: - gluster-csi-containers - glusterd2-containers >> >>> The job python-compliance fail like this: >>> https://build.gluster.org/job/python-compliance/5813/ >>> >>> The fedora-smoke job, who is building on newer fedora (so newer gcc), >>> is failling too: >>> https://build.gluster.org/job/fedora-smos some new vol option that ought >>> to be set?ke/6753/console >>> >>> >>> Gluster-csi-containers is having trouble to run >>> https://build.gluster.org/job/gluster-csi-containers/304/console >>> https://bugzilla.redhat.com/show_bug.cgi?id=1693385#c5 >>> but before, it did fail with "out of space": >>> https://build.gluster.org/job/gluster-csi-containers/303/console >>> >>> and it also fail (well, should fail) with this: >>> 16:51:07 make: *** No targets specified and no makefile found. Stop. >>> >>> which is indeed not present in the git repo, so this seems like the job >>> is unmaintained. >>> >>> >>> The last one to fail is glusterd2-containers: >>> >>> https://build.gluster.org/job/glusterd2-containers/323/console >>> >>> This one is fun, because it fail, but appear as ok on jenkins. It fail >>> because of some ansible issue, due to newer Fedora. >>> >>> So, since we need to switch, here is what I would recommend: >>> - switch the working job to F30 >>> - wait 2 weeks, and switch fedora-smoke and python-compliance to F30. >>> This will force someone to fix the problem. >>> - drop the non fixed containers jobs, unless someone fix them, in 1 >>> month. >>> >> >> Looks like a good plan. >> >> >>> >>> -- >>> Michael Scherer >>> Sysadmin, Community Infrastructure >>> >>> >>> >>> _______________________________________________ >>> >>> Community Meeting Calendar: >>> >>> APAC Schedule - >>> Every 2nd and 4th Tuesday at 11:30 AM IST >>> Bridge: https://bluejeans.com/836554017 >>> >>> NA/EMEA Schedule - >>> Every 1st and 3rd Tuesday at 01:00 PM EDT >>> Bridge: https://bluejeans.com/486278655 >>> >>> Gluster-devel mailing list >>> Gluster-devel at gluster.org >>> https://lists.gluster.org/mailman/listinfo/gluster-devel >>> >>> >> >> -- >> Amar Tumballi (amarts) >> > > > -- > Amar Tumballi (amarts) > _______________________________________________ > Gluster-infra mailing list > Gluster-infra at gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-infra -------------- next part -------------- An HTML attachment was scrubbed... URL: From bugzilla at redhat.com Mon Jul 15 05:47:50 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 15 Jul 2019 05:47:50 +0000 Subject: [Gluster-infra] [Bug 1724957] Grant additional maintainers merge rights on release branches In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1724957 Deepshikha khandelwal changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |CURRENTRELEASE Last Closed| |2019-07-15 05:47:50 --- Comment #3 from Deepshikha khandelwal --- Fixed. Closing bug -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 15 05:49:09 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 15 Jul 2019 05:49:09 +0000 Subject: [Gluster-infra] [Bug 1728120] Not able to access core https://build.gluster.org/job/regression-test-with-multiplex/1402/consoleFull In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1728120 Deepshikha khandelwal changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |CURRENTRELEASE Last Closed| |2019-07-15 05:49:09 -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 16 04:37:17 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 16 Jul 2019 04:37:17 +0000 Subject: [Gluster-infra] [Bug 1697812] mention a pointer to all the mailing lists available under glusterfs project(https://www.gluster.org/community/) In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1697812 Amar Tumballi changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |CURRENTRELEASE Last Closed| |2019-07-16 04:37:17 --- Comment #2 from Amar Tumballi --- Page updated, please check. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 16 04:43:26 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 16 Jul 2019 04:43:26 +0000 Subject: [Gluster-infra] [Bug 1727727] Build+Packaging Automation In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1727727 spamecha at redhat.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Tue Jul 16 05:59:00 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Tue, 16 Jul 2019 05:59:00 +0000 Subject: [Gluster-infra] [Bug 1564130] need option 'cherry-pick to release-x.y' in reviews In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1564130 Deepshikha khandelwal changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(dkhandel at redhat.c | |om) | --- Comment #4 from Deepshikha khandelwal --- No. Jenkins part of automation is pending. I'll pick this up next week. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Thu Jul 18 04:09:07 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 18 Jul 2019 04:09:07 +0000 Subject: [Gluster-infra] [Bug 1730962] New: My emails to gluster-users are not hitting the list Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1730962 Bug ID: 1730962 Summary: My emails to gluster-users are not hitting the list Product: GlusterFS Version: mainline Status: NEW Component: project-infrastructure Assignee: bugs at gluster.org Reporter: ravishankar at redhat.com CC: bugs at gluster.org, gluster-infra at gluster.org Target Milestone: --- Classification: Community Description of problem: I replied to a user on the 16th of July but my email hasn't been delivered to the list yet.The user got my email though and he replied, which made it to the list: https://lists.gluster.org/pipermail/gluster-users/2019-July/036799.html. Follow-up emails from me on the same thread have not been delivered either. I did not get any error for the sent messages. I sent an email to gluster-users-owner at gluster.org for help but I haven't received any response. I'm not sure if the mailing list administration falls under the infra team's purview. If it doesn't feel free to close the bug and possibly point me to whom I can get in touch with regarding the issue. -- You are receiving this mail because: You are on the CC list for the bug. From ravishankar at redhat.com Thu Jul 18 04:46:39 2019 From: ravishankar at redhat.com (Ravishankar N) Date: Thu, 18 Jul 2019 10:16:39 +0530 Subject: [Gluster-infra] Fwd: My email not delivered to the list In-Reply-To: References: Message-ID: <8e766c6d-21dd-0660-b527-5cc6a21ee327@redhat.com> Hello, I have created https://bugzilla.redhat.com/show_bug.cgi?id=1730962 for this. Regards, Ravi -------- Forwarded Message -------- Subject: My email not delivered to the list Date: Wed, 17 Jul 2019 08:55:07 +0530 From: Ravishankar N To: gluster-users-owner at gluster.org Hi, I had replied to the thread "Graceful gluster server retire/poweroff" on gluster-users but I don't see it being delivered to the list. The original poster has got my email though, and his reply to it has made it to the list. Any idea what the problem could be? Regards, Ravi -------------- next part -------------- An HTML attachment was scrubbed... URL: From bugzilla at redhat.com Thu Jul 18 07:53:59 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 18 Jul 2019 07:53:59 +0000 Subject: [Gluster-infra] [Bug 1730962] My emails to gluster-users are not hitting the list In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1730962 M. Scherer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mscherer at redhat.com --- Comment #1 from M. Scherer --- It does fall under our purview. it seems the address you used is not a member of the list and it seems no one moderated the list since months. I am cleaning the moderation queue, it should appear soon. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Thu Jul 18 08:15:04 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 18 Jul 2019 08:15:04 +0000 Subject: [Gluster-infra] [Bug 1730962] My emails to gluster-users are not hitting the list In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1730962 --- Comment #2 from Ravishankar N --- Thanks Michael, that explains it. I had configured Thunderbird on my fresh Fedora install using my kerberos email ID rather than my alias which I use for mailing lists. Let me fix it. -- You are receiving this mail because: You are on the CC list for the bug. From mscherer at redhat.com Thu Jul 18 08:38:43 2019 From: mscherer at redhat.com (Michael Scherer) Date: Thu, 18 Jul 2019 10:38:43 +0200 Subject: [Gluster-infra] Regarding the recent arrival of emails on list Message-ID: <6285ca09acc6fc87d133527ec9ffd6bdde600124.camel@redhat.com> Hi, while working on https://bugzilla.redhat.com/show_bug.cgi?id=1730962, I did notice that no one was moderating the list since end of April, so I decided to clean the queue (around 200 to 300 mails, most non legitimate, but some where). That's why old emails came suddenly, as I figured that even if this was old, some might be useful for archives or something. Sorry for not having looked earlier, it seems we might need to redistribute the responsibility regarding this task since a few people who were doing it likely moved on from the project. -- Michael Scherer Sysadmin, Community Infrastructure -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From bugzilla at redhat.com Thu Jul 18 09:24:54 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 18 Jul 2019 09:24:54 +0000 Subject: [Gluster-infra] [Bug 1731067] New: Need nightly build for release 7 branch Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1731067 Bug ID: 1731067 Summary: Need nightly build for release 7 branch Product: GlusterFS Version: mainline Status: NEW Component: project-infrastructure Severity: high Assignee: bugs at gluster.org Reporter: rkothiya at redhat.com CC: bugs at gluster.org, gluster-infra at gluster.org Target Milestone: --- Classification: Community -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Thu Jul 25 08:29:34 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 25 Jul 2019 08:29:34 +0000 Subject: [Gluster-infra] [Bug 1731067] Need nightly build for release 7 branch In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1731067 Deepshikha khandelwal changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dkhandel at redhat.com Assignee|bugs at gluster.org |dkhandel at redhat.com -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Thu Jul 25 11:41:34 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 25 Jul 2019 11:41:34 +0000 Subject: [Gluster-infra] [Bug 1727727] Build+Packaging Automation In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1727727 hari gowtham changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hgowtham at redhat.com --- Comment #4 from hari gowtham --- For automating the packaging for debian and ubuntu, we have wrote two scripts. packaging. sh is one which the jenkins' slave has to run based on a job that is being triggered by one of us. This will ssh to the respective lab machine and run the generic_script.sh in the machine to build the packages. (We will take care of having the generic_script.sh made available in the lab machine.) The requirements from the infra side are: 1) check if the lab machines are reachable from the jenkins' slave 2) map the credentials that the package.sh needs to ssh to the lab machines, so we can use the key instead of passing passwords. 3) trigger permissions are to be given only for a specific set of people. Amar, Shyam, Kaleb, Sunny, Rinku, Shwetha, Sheetal, and Hari. The scripts are available at: https://github.com/Sheetalpamecha/packaging-scripts/ Will send the package.sh script as a patch to build-jobs once the keys to login are available. And will work on the job simulatenously as well. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Thu Jul 25 13:32:25 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 25 Jul 2019 13:32:25 +0000 Subject: [Gluster-infra] [Bug 1727727] Build+Packaging Automation In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1727727 M. Scherer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mscherer at redhat.com --- Comment #6 from M. Scherer --- We have debian builders (well, we have one, but I can create more quite easily). How much is lots of disk space ? Also, I would prefer a separate step to sign, so we can run that on a separate server that the one where stuff are being built. And yes, we are not going to build stuff in the lab, we can't ssh there. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Thu Jul 25 13:54:31 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 25 Jul 2019 13:54:31 +0000 Subject: [Gluster-infra] [Bug 1713391] Access to wordpress instance of gluster.org required for release management In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1713391 --- Comment #5 from M. Scherer --- So, I do not have the admin credentials for that wordpress instance (I have access for wpengine, which we inherited). I guess that mean I have to find somehow a way to enter. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Thu Jul 25 14:07:06 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 25 Jul 2019 14:07:06 +0000 Subject: [Gluster-infra] [Bug 1713391] Access to wordpress instance of gluster.org required for release management In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1713391 --- Comment #6 from M. Scherer --- Ok, so I found a way to enter, I created myself a account, and created a account for rinku, who should have received a email. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Thu Jul 25 12:42:08 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Thu, 25 Jul 2019 12:42:08 +0000 Subject: [Gluster-infra] [Bug 1727727] Build+Packaging Automation In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1727727 --- Comment #5 from Kaleb KEITHLEY --- (In reply to hari gowtham from comment #4) > The requirements from the infra side are: > 1) check if the lab machines are reachable from the jenkins' slave They are not reachable. You probably need four new build machines in Jenkins: Debian stretch/9, buster/10, and bullseye/11; and Ubuntu bionic/18.04. The debian boxes need lots of disk space, the ubuntu needs slightly less as packages aren't actually built on it, it sends them to Launchpad to build. The machines _must_ be secure as they will, by necessity, have to have gpg private keys that are used to sign the packages installed on them. The machines should be apt update + apt upgraded periodically. There's a small amount of pbuilder setup (see the ~glusterpackager/HOWTO file on the current builders in the lab) that should be updated periodically as well. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 29 05:46:35 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 29 Jul 2019 05:46:35 +0000 Subject: [Gluster-infra] [Bug 1730962] My emails to gluster-users are not hitting the list In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1730962 Deepshikha khandelwal changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dkhandel at redhat.com Flags| |needinfo?(ravishankar at redha | |t.com) --- Comment #3 from Deepshikha khandelwal --- @Ravi Is this resolved for you now? -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 29 05:49:37 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 29 Jul 2019 05:49:37 +0000 Subject: [Gluster-infra] [Bug 1730962] My emails to gluster-users are not hitting the list In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1730962 Ravishankar N changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ravishankar at redha | |t.com) | --- Comment #4 from Ravishankar N --- Yes I have changed to my alias ID while emailing the list and the messages are now getting delivered. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 29 05:51:34 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 29 Jul 2019 05:51:34 +0000 Subject: [Gluster-infra] [Bug 1730962] My emails to gluster-users are not hitting the list In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1730962 Deepshikha khandelwal changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |NOTABUG Last Closed| |2019-07-29 05:51:34 -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 29 06:57:50 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 29 Jul 2019 06:57:50 +0000 Subject: [Gluster-infra] [Bug 1727727] Build+Packaging Automation In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1727727 --- Comment #7 from hari gowtham --- @Misc, I see debian machines have 20GB disks each and Ubuntu has 30GB disk in the current machines. And we did come across debian machine not having enough space to build lately. So a bit more for the new machines in jenkins would be better. About signing, is it fine if we get the password to the machines as a parameter from the person who triggers the jenkins' job and proceed with it to sign in? This way we can make use of the same machine for building and signing the package. But I'm not sure if the parameters are logged somewhere. Which will let others know the password. If that's the case, do we have a work around for this? If manual intervention is necessary for signing, it sort of defeats a portion of this effort. @Kaleb, I wanted to ask about the steps for the initial environment setup. Thanks for informing about it, will look into it once the machines are available. I want to know if the package that are already built on these lab machines have to be moved to these new jenkins' machine as a part of keeping track of packages. And will there be any other work to be done as a part of this movement. Thanks, Hari. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 29 07:54:17 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 29 Jul 2019 07:54:17 +0000 Subject: [Gluster-infra] [Bug 1727727] Build+Packaging Automation In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1727727 --- Comment #8 from M. Scherer --- We can increase the disk size if needed when we hit problems, that shouldn't be a worry. About the password, we can also just store the key on a emulated smartcard on the builder side, and use a password stored on the builder. Therefore, no one will have to type it or share it, and it can't be copied. And that permit automated setup. -- You are receiving this mail because: You are on the CC list for the bug. From bugzilla at redhat.com Mon Jul 29 11:06:11 2019 From: bugzilla at redhat.com (bugzilla at redhat.com) Date: Mon, 29 Jul 2019 11:06:11 +0000 Subject: [Gluster-infra] [Bug 1731067] Need nightly build for release 7 branch In-Reply-To: References: Message-ID: https://bugzilla.redhat.com/show_bug.cgi?id=1731067 --- Comment #1 from Deepshikha khandelwal --- Patch for review https://review.gluster.org/#/c/build-jobs/+/23126/ -- You are receiving this mail because: You are on the CC list for the bug. From mscherer at redhat.com Mon Jul 29 13:06:59 2019 From: mscherer at redhat.com (Michael Scherer) Date: Mon, 29 Jul 2019 15:06:59 +0200 Subject: [Gluster-infra] Jenkins security reboot for plugins Message-ID: <65c9a9b676cbcf4c36d19135543b1dc070a571f9.camel@redhat.com> Hi, a jenkins plugin upgrade is planned. There is a setting "download and reboot once there is no jobs running", so I hope that with any luck, this will work (first time I used the option, so I hope this will not create issue with Gerrit). Also, after a java upgrade on the underlying platform, a dozen or so of jobs seems to have disappeared. Jenkins agent seems to break when a minor version of the rpm is installed (like the main jenkins server...), the issue should now be mitigated as well (ansible to send a signal, and let jenkins reconnect to the builder). -- Michael Scherer Sysadmin, Community Infrastructure -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From mscherer at redhat.com Wed Jul 31 17:31:12 2019 From: mscherer at redhat.com (Michael Scherer) Date: Wed, 31 Jul 2019 19:31:12 +0200 Subject: [Gluster-infra] Ongoing issue with docs.gluster.org Message-ID: <26e3d4c1e1ceeeecb0fb2fcaeff12687eae66251.camel@redhat.com> Hi, people (and nagios) have reported issue with the docs.gluster.org domain. I got texted last night, but the problem solved itself while I was sleeping. It seems to be back, and I restarted the proxy since it seems that readthedocs changed the IP of their load balancer (and it was cached by nginx so slow to propagate) See https://twitter.com/readthedocs/status/1156337277640908801 for the initial report. This is kinda out of the control of the gluster infra team, but do not hesitate to send support, love or money to the volunteers of RTD. We are monitoring the issue. -- Michael Scherer Sysadmin, Community Infrastructure -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: