Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-6.1 released
On 4/18/19 3:40 AM, Niels de Vos wrote: > On Wed, Apr 17, 2019 at 06:30:46PM +, jenk...@build.gluster.org wrote: >> SRC: >> https://build.gluster.org/job/release-new/86/artifact/glusterfs-6.1.tar.gz >> HASH: >> https://build.gluster.org/job/release-new/86/artifact/glusterfs-6.1.sha512sum > > Packages are available in the testing repository of the CentOS Storage > SIG. Please try them out and let us know if they are working as > expected. Tested, works as expected. Please tag them for a release. > > # yum install centos-release-gluster6 > # yum --enablerepo=centos-gluster6-test install glusterfs-server > > Thanks, > Niels > ___ > maintainers mailing list > maintain...@gluster.org > https://lists.gluster.org/mailman/listinfo/maintainers > ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-5.6 released
On 4/11/19 9:57 AM, Shyam Ranganathan wrote: > On 4/9/19 9:37 AM, Niels de Vos wrote: >> On Tue, Apr 09, 2019 at 11:56:31AM +, jenk...@build.gluster.org wrote: >>> SRC: >>> https://build.gluster.org/job/release-new/85/artifact/glusterfs-5.6.tar.gz >>> HASH: >>> https://build.gluster.org/job/release-new/85/artifact/glusterfs-5.6.sha512sum >> >> Packages from the CentOS Storage SIG should be landing in the testing >> repository very soon from now. Please let us know any test results. >> >> CentOS 7: >> >> # yum install centos-release-gluster5 >> # yum --enablerepo=centos-gluster5-test install glusterfs-server > > Poornima, are you testing these out? Niels, tested out CentOS packages, 5.6 installs and works as expected. Please mark them for a release. > >> >> CentOS 6: >> >> # yum install centos-release-gluster5 >> # yum --enablerepo=centos-gluster5-test install glusterfs-fuse >> >> Thanks, >> Niels >> ___ >> maintainers mailing list >> maintain...@gluster.org >> https://lists.gluster.org/mailman/listinfo/maintainers >> > ___ > maintainers mailing list > maintain...@gluster.org > https://lists.gluster.org/mailman/listinfo/maintainers > ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] Requesting for an early 5.6 release
On 4/11/19 9:58 AM, Patrick Matthäi wrote: > > Am 08.04.2019 um 16:04 schrieb Shyam Ranganathan: >> On 4/6/19 1:47 AM, Poornima Gurusiddaiah wrote: >>> Hi, >>> >>> We had a critical bug [1], that got introduced in gluster release 5. >>> There are users waiting on an update with the fix. Hence requesting for >>> an out of band release for 5.6. Myself and jiffin, volunteer to do some >>> tasks of the release- tagging(?) testing. But would need help with the >>> builds and other tasks. > > Hi, > > Debian Buster 10 is now in freeze and I were able to pull in version 5.5 > instead of 5.4 for it. Pulling again a new upstream version to buster > could be difficult.. > > Could you point me to the bug report and the diff for the critical fix, > so that I can upload this explicit change to buster? Here you go, Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1673058 Fix/patch: https://review.gluster.org/c/glusterfs/+/22404 commit ID on release-5 branch: 1fba86169b0850c3fcd02e56d0ddbba3efe9ae78 > > ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] Requesting for an early 5.6 release
On 4/6/19 1:47 AM, Poornima Gurusiddaiah wrote: > Hi, > > We had a critical bug [1], that got introduced in gluster release 5. > There are users waiting on an update with the fix. Hence requesting for > an out of band release for 5.6. Myself and jiffin, volunteer to do some > tasks of the release- tagging(?) testing. But would need help with the > builds and other tasks. Tagging and building a tarball needs rights on the release branch, also it takes about 10 minutes to do, hence I can take care of the same. Packaging is still done by just 2 folks, so added the packaging list to this mail, to understand if they need any assistance and their time constraints. Post packaging, we test if the RPMS are fine, and upgrade from an older version. I use containers to test the same as detailed here [1]. Helping out with this step can be useful, and I will assume till I hear otherwise that you would taking care of the same for this minor release. Other activities include, - prepare release notes - Upload release notes to the doc site - Announce the release - Close bugs fixed in the release post the announcement Again, something I can take care of, and should take about 30 minutes overall. Shyam [1] Package testing: https://hackmd.io/-yC3Ol68SwaRWr8bzaL8pw# ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-4.1.8 released
On 3/28/19 8:05 AM, Niels de Vos wrote: > On Wed, Mar 27, 2019 at 10:12:28PM +, jenk...@build.gluster.org wrote: >> SRC: >> https://build.gluster.org/job/release-new/84/artifact/glusterfs-4.1.8.tar.gz >> HASH: >> https://build.gluster.org/job/release-new/84/artifact/glusterfs-4.1.8.sha512sum >> >> This release is made off jenkins-release-84 > > Packages from the CentOS Storage SIG (el6 + el7) should land in the > testing repository within the next hour or so. Please check them out and > provide any results of the testing: Tested install and a short volume creation, data addition test, packages look fine and can be marked for release. > ># yum install centos-release-gluster41 ># yum install --enablerepo=centos-gluster*-test glusterfs-server > > Thanks, > Niels > > > ___ > maintainers mailing list > maintain...@gluster.org > https://lists.gluster.org/mailman/listinfo/maintainers > ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-5.5 released
On 3/19/19 11:28 PM, Kaleb Keithley wrote: > It seems I neglected to tag the packages for testing. > > I've fixed that. Hopefully the packages land on buildlogs.centos.org > <http://buildlogs.centos.org> soon. Tested, passed and can be released. Thanks Kaleb! > > On Tue, Mar 19, 2019 at 10:58 AM Shyam Ranganathan <mailto:srang...@redhat.com>> wrote: > > On 3/16/19 2:03 AM, Kaleb Keithley wrote: > > Packages for the CentOS Storage SIG are now available for testing. > > Please try them out and report test results on this list. > > > > # yum install centos-release-gluster > > # yum install --enablerepo=centos-gluster5-test glusterfs-server > > The buildlogs servers do not yet have the RPMs for 5.5 to test. I did > try to go and use the build artifacts from > https://cbs.centos.org/koji/buildinfo?buildID=25417 but as there is no > repo file, unable to install pointing to this source as the repo. > > Can this be fixed, or some alternate provided, so that the packages can > be tested and reported back for publishing? > > Thanks, > Shyam > ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-5.4 released
On 3/13/19 10:44 AM, Shyam Ranganathan wrote: > On 3/13/19 9:09 AM, Kaleb Keithley wrote: >> The v5.4 tag was made and a release job was run which gave us >> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz. >> If the v5.4 tag is moved then there's a logical disconnect between the >> tag and _that_ tar file, or more accurately the files in that tar file. >> >> Shyam and I discussed the merits of releasing v5.5 versus respinning >> builds with patches. Respinning builds with patches isn't uncommon. The >> difference in the amount of work between one or the other is negligible. >> In the end Shyam (mainly) decided to go with respinning with patches >> because a full up "release" for him is a lot more work. (And we both >> have other $dayjob things we need to be working on instead of endlessly >> spinning releases and packages.) > > Considering all comments/conversations, I think I will tag a v5.5 with > the required commits and update the 5.4 release-notes to call it 5.5 > with the added changes. > > Give me a couple of hours :) Well that took longer (sorry was out sick for some time). 5.4 is now tagged and the release tarball generated for packaging. > >> >> >> On Wed, Mar 13, 2019 at 8:52 AM Amar Tumballi Suryanarayan >> mailto:atumb...@redhat.com>> wrote: >> >> I am totally fine with v5.5, my suggestion for moving the tag was if >> we consider calling 5.4 with these two patches. >> >> Calling the release as 5.5 is totally OK, and we call it out >> specifically in our version numbering scheme, as if something is >> very serious, we can break 'release date' train. >> >> -Amar >> >> On Wed, Mar 13, 2019 at 6:13 PM Kaleb Keithley > <mailto:kkeit...@redhat.com>> wrote: >> >> The Version tag should be (considered) immutable. Please don't >> move it. >> >> If you want to add another tag to help us remember this issue >> that's fine. >> >> The other option which Shyam and I discussed was tagging v5.5. >> >> >> On Wed, Mar 13, 2019 at 8:32 AM Amar Tumballi Suryanarayan >> mailto:atumb...@redhat.com>> wrote: >> >> We need to tag different commit may be? So the 'git checkout >> v5.4' points to the correct commit? >> >> On Wed, 13 Mar, 2019, 4:40 PM Shyam Ranganathan, >> mailto:srang...@redhat.com>> wrote: >> >> Niels, Kaleb, >> >> We need to respin 5.4 with the 2 additional commits as >> follows, >> >> commit a00953ed212a7071b152c4afccd35b92fa5a682a (HEAD -> >> release-5, >> core: make compute_cksum function op_version compatible >> >> commit 8fb4631c65f28dd0a5e0304386efff3c807e64a4 >> dict: handle STR_OLD data type in xdr conversions >> >> As the current build breaks rolling upgrades, we had >> held back on >> announcing 5.4 and are now ready with the fixes that can >> be used to >> respin 5.4. >> >> Let me know if I need to do anything more from my end >> for help with the >> packaging. >> >> Once the build is ready, we would be testing it out as >> usual. >> >> NOTE: As some users have picked up 5.4 the announce >> would also carry a >> notice, that they need to do a downserver upgrade to the >> latest bits >> owing to the patches that have landed in addition to the >> existing content. >> >> Thanks, >> Shyam >> >> On 3/5/19 8:59 AM, Shyam Ranganathan wrote: >> > On 2/27/19 5:19 AM, Niels de Vos wrote: >> >> On Tue, Feb 26, 2019 at 02:47:30PM +, >> jenk...@build.gluster.org >> <mailto:jenk...@build.gluster.org> wrote: >> >>> SRC: >> >> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz >> >>> HASH: >> >> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum >>
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-5.4 released
On 3/13/19 9:09 AM, Kaleb Keithley wrote: > The v5.4 tag was made and a release job was run which gave us > https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz. > If the v5.4 tag is moved then there's a logical disconnect between the > tag and _that_ tar file, or more accurately the files in that tar file. > > Shyam and I discussed the merits of releasing v5.5 versus respinning > builds with patches. Respinning builds with patches isn't uncommon. The > difference in the amount of work between one or the other is negligible. > In the end Shyam (mainly) decided to go with respinning with patches > because a full up "release" for him is a lot more work. (And we both > have other $dayjob things we need to be working on instead of endlessly > spinning releases and packages.) Considering all comments/conversations, I think I will tag a v5.5 with the required commits and update the 5.4 release-notes to call it 5.5 with the added changes. Give me a couple of hours :) > > > On Wed, Mar 13, 2019 at 8:52 AM Amar Tumballi Suryanarayan > mailto:atumb...@redhat.com>> wrote: > > I am totally fine with v5.5, my suggestion for moving the tag was if > we consider calling 5.4 with these two patches. > > Calling the release as 5.5 is totally OK, and we call it out > specifically in our version numbering scheme, as if something is > very serious, we can break 'release date' train. > > -Amar > > On Wed, Mar 13, 2019 at 6:13 PM Kaleb Keithley <mailto:kkeit...@redhat.com>> wrote: > > The Version tag should be (considered) immutable. Please don't > move it. > > If you want to add another tag to help us remember this issue > that's fine. > > The other option which Shyam and I discussed was tagging v5.5. > > > On Wed, Mar 13, 2019 at 8:32 AM Amar Tumballi Suryanarayan > mailto:atumb...@redhat.com>> wrote: > > We need to tag different commit may be? So the 'git checkout > v5.4' points to the correct commit? > > On Wed, 13 Mar, 2019, 4:40 PM Shyam Ranganathan, > mailto:srang...@redhat.com>> wrote: > > Niels, Kaleb, > > We need to respin 5.4 with the 2 additional commits as > follows, > > commit a00953ed212a7071b152c4afccd35b92fa5a682a (HEAD -> > release-5, > core: make compute_cksum function op_version compatible > > commit 8fb4631c65f28dd0a5e0304386efff3c807e64a4 > dict: handle STR_OLD data type in xdr conversions > > As the current build breaks rolling upgrades, we had > held back on > announcing 5.4 and are now ready with the fixes that can > be used to > respin 5.4. > > Let me know if I need to do anything more from my end > for help with the > packaging. > > Once the build is ready, we would be testing it out as > usual. > > NOTE: As some users have picked up 5.4 the announce > would also carry a > notice, that they need to do a downserver upgrade to the > latest bits > owing to the patches that have landed in addition to the > existing content. > > Thanks, > Shyam > > On 3/5/19 8:59 AM, Shyam Ranganathan wrote: > > On 2/27/19 5:19 AM, Niels de Vos wrote: > >> On Tue, Feb 26, 2019 at 02:47:30PM +, > jenk...@build.gluster.org > <mailto:jenk...@build.gluster.org> wrote: > >>> SRC: > > https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz > >>> HASH: > > https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum > >> > >> Packages for the CentOS Storage SIG are now available > for testing. > >> Please try them out and report test results on this list. > >> > >> # yum install centos-release-gluster > >> # yum install --enablerepo=centos-gluster5-test > glusterfs-server > > > > Due to patch [1] upgrades are broken, so we are > awaitin
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-5.4 released
Niels, Kaleb, We need to respin 5.4 with the 2 additional commits as follows, commit a00953ed212a7071b152c4afccd35b92fa5a682a (HEAD -> release-5, core: make compute_cksum function op_version compatible commit 8fb4631c65f28dd0a5e0304386efff3c807e64a4 dict: handle STR_OLD data type in xdr conversions As the current build breaks rolling upgrades, we had held back on announcing 5.4 and are now ready with the fixes that can be used to respin 5.4. Let me know if I need to do anything more from my end for help with the packaging. Once the build is ready, we would be testing it out as usual. NOTE: As some users have picked up 5.4 the announce would also carry a notice, that they need to do a downserver upgrade to the latest bits owing to the patches that have landed in addition to the existing content. Thanks, Shyam On 3/5/19 8:59 AM, Shyam Ranganathan wrote: > On 2/27/19 5:19 AM, Niels de Vos wrote: >> On Tue, Feb 26, 2019 at 02:47:30PM +, jenk...@build.gluster.org wrote: >>> SRC: >>> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz >>> HASH: >>> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum >> >> Packages for the CentOS Storage SIG are now available for testing. >> Please try them out and report test results on this list. >> >> # yum install centos-release-gluster >> # yum install --enablerepo=centos-gluster5-test glusterfs-server > > Due to patch [1] upgrades are broken, so we are awaiting a fix or revert > of the same before requesting a new build of 5.4. > > The current RPMs should hence not be published. > > Sanju/Hari, are we reverting this patch so that we can release 5.4, or > are we expecting the fix to land in 5.4 (as in [2])? > > Thanks, > Shyam > > [1] Patch causing regression: https://review.gluster.org/c/glusterfs/+/22148 > > [2] Proposed fix on master: https://review.gluster.org/c/glusterfs/+/22297/ > ___ > maintainers mailing list > maintain...@gluster.org > https://lists.gluster.org/mailman/listinfo/maintainers > ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-5.4 released
On 3/5/19 10:10 AM, Sanju Rakonde wrote: > > > On Tue, Mar 5, 2019 at 7:29 PM Shyam Ranganathan <mailto:srang...@redhat.com>> wrote: > > On 2/27/19 5:19 AM, Niels de Vos wrote: > > On Tue, Feb 26, 2019 at 02:47:30PM +, > jenk...@build.gluster.org <mailto:jenk...@build.gluster.org> wrote: > >> SRC: > https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz > >> HASH: > > https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum > > > > Packages for the CentOS Storage SIG are now available for testing. > > Please try them out and report test results on this list. > > > > # yum install centos-release-gluster > > # yum install --enablerepo=centos-gluster5-test glusterfs-server > > Due to patch [1] upgrades are broken, so we are awaiting a fix or revert > of the same before requesting a new build of 5.4. > > The current RPMs should hence not be published. > > Sanju/Hari, are we reverting this patch so that we can release 5.4, or > are we expecting the fix to land in 5.4 (as in [2])? > > > Shyam, I need some more time(approximately 1 day) to provide the fix. If > we have 1 more day with us, we can wait. Or else we can revert the > patch[1] and continue with the release. We can wait a day, let me know tomorrow regarding the status. Thanks. > > > Thanks, > Shyam > > [1] Patch causing regression: > https://review.gluster.org/c/glusterfs/+/22148 > > [2] Proposed fix on master: > https://review.gluster.org/c/glusterfs/+/22297/ > > > > -- > Thanks, > Sanju ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-5.4 released
On 2/27/19 5:19 AM, Niels de Vos wrote: > On Tue, Feb 26, 2019 at 02:47:30PM +, jenk...@build.gluster.org wrote: >> SRC: >> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz >> HASH: >> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum > > Packages for the CentOS Storage SIG are now available for testing. > Please try them out and report test results on this list. > > # yum install centos-release-gluster > # yum install --enablerepo=centos-gluster5-test glusterfs-server Due to patch [1] upgrades are broken, so we are awaiting a fix or revert of the same before requesting a new build of 5.4. The current RPMs should hence not be published. Sanju/Hari, are we reverting this patch so that we can release 5.4, or are we expecting the fix to land in 5.4 (as in [2])? Thanks, Shyam [1] Patch causing regression: https://review.gluster.org/c/glusterfs/+/22148 [2] Proposed fix on master: https://review.gluster.org/c/glusterfs/+/22297/ ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] Release 5.4: Earlier than Mar-10th
Thank you all, merging the patches and tagging the release today. Shyam On 2/26/19 6:50 AM, Atin Mukherjee wrote: > Milind - response inline. > > Shyam - I'm not sure if you're tracking this. But at this point any > blocker bugs attached to 5.4 should also have clones of release-6 and > attached to the release tracker, otherwise we'll regress! > > On Tue, Feb 26, 2019 at 5:00 PM Milind Changire <mailto:mchan...@redhat.com>> wrote: > > On Fri, Feb 8, 2019 at 8:26 PM Shyam Ranganathan > mailto:srang...@redhat.com>> wrote: > > Hi, > > There have been several crashes and issues reported by users on the > latest 5.3 release. Around 10 patches have been merged since 5.3 > and we > have a few more addressing the blockers against 5.4 [1]. > > The original date was March 10th, but we would like to > accelerate a 5.4 > release to earlier this month, once all critical blockers are fixed. > > Hence there are 3 asks in this mail, > > 1) Packaging team, would it be possible to accommodate an 5.4 > release > around mid-next week (RC0 for rel-6 is also on the same week)? > Assuming > we get the required fixes by then. > > 2) Maintainers, what other issues need to be tracked as > blockers? Please > add them to [1]. > > 3) Current blocker status reads as follows: > - Bug 1651246 - Failed to dispatch handler > - This shows 2 patches that are merged, but there is no patch that > claims this is "Fixed" hence bug is still in POST state. What other > fixes are we expecting on this? > - @Milind request you to update the status > > Bug 1651246 has been addressed. > Patch has been merged on master > <https://review.gluster.org/c/glusterfs/+/1> as well as > release-5 <https://review.gluster.org/c/glusterfs/+/22237> branches. > Above patch addresses logging issue only. > > > Isn't this something which is applicable to release-6 branch as well? I > don't find https://review.gluster.org/#/c/glusterfs/+/1/ in > release-6 branch which means we're going to regress this in release 6 if > this isn't backported and marked as blocker to release 6. > > > > - Bug 1671556 - glusterfs FUSE client crashing every few days with > 'Failed to dispatch handler' > - Awaiting fixes for identified issues > - @Nithya what would be the target date? > > - Bug 1671603 - flooding of "dict is NULL" logging & crash of > client process > - Awaiting a fix, what is the potential target date for the same? > - We also need the bug assigned to a person > > Bug 1671603 has been addressed. > Patch has been posted on master > <https://review.gluster.org/c/glusterfs/+/22126> and merged on > release-5 <https://review.gluster.org/c/glusterfs/+/22127> branches. > > > Are you sure the links are correct? Patch posted against release 5 > branch is abandoned? And also just like above, same question for > release-6 branch, I don't see a patch? > > Above patch addresses logging issue only. > > > Thanks, > Shyam > > [1] Release 5.4 tracker: > https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.4 > ___ > maintainers mailing list > maintain...@gluster.org <mailto:maintain...@gluster.org> > https://lists.gluster.org/mailman/listinfo/maintainers > > > > -- > Milind > > ___ > maintainers mailing list > maintain...@gluster.org <mailto:maintain...@gluster.org> > https://lists.gluster.org/mailman/listinfo/maintainers > ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] Release 5.4: Earlier than Mar-10th
Time to reset and understand where we are at here. The dates are slipping, but the tracker is still having the following blockers. We need to either understand when these would be fixed, and take a call on creating 5.4 with known issues not addressed in the blocker, or wait for the fixes. Responses to the bugs and updates to bugzilla would help deciding on the same. 1) Title: glustereventsd does not start on Ubuntu 16.04 LTS https://bugzilla.redhat.com/show_bug.cgi?id=1649054 @aravinda, any updates? Should we wait, of will this take more time? 2) Title: glusterfs FUSE client crashing every few days with 'Failed to dispatch handler' https://bugzilla.redhat.com/show_bug.cgi?id=1671556 All patches against the bug are merged, but bug remains in POST state, as none of the patches claim that the issue "Fixes" the reported problem. Are we awaiting more patches for the same? Du/Milind/Nithya? 3) Title: flooding of "dict is NULL" logging & crash of client process https://bugzilla.redhat.com/show_bug.cgi?id=1671603 Still in NEW state, Du/Amar, do we have a date for resolution? Thanks, Shyam On 2/18/19 10:13 AM, Shyam Ranganathan wrote: > We have more blockers against 5.4 now marked. Would like to ask the list > and understand what we want to get done with by 5.4 and what the > timeline looks like. > > The bug list: > https://bugzilla.redhat.com/buglist.cgi?bug_id=1667103_id_type=anddependson=tvp > > 1) https://bugzilla.redhat.com/show_bug.cgi?id=1649054 > Title: glustereventsd does not start on Ubuntu 16.04 LTS > Assignee: Aravinda > @aravinda can we understand target dates here? > > 2) https://bugzilla.redhat.com/show_bug.cgi?id=1671556 > Title: glusterfs FUSE client crashing every few days with 'Failed to > dispatch handler' > Assignee: Nithya (working on Du and Milind) > @du/@milind can we get an update on this bug and how far away we are? > > 3) https://bugzilla.redhat.com/show_bug.cgi?id=1671603 > Title: flooding of "dict is NULL" logging & crash of client process > Assignee: None (Amar has most of the comments) > @amar, do we need 2 bugs here? Also, how far away is a fix? > > 4) https://bugzilla.redhat.com/show_bug.cgi?id=1676356 > Title: glusterfs FUSE client crashing every few days with 'Failed to > dispatch handler' > Assignee: Du > @du, we are still waiting to get > https://review.gluster.org/c/glusterfs/+/22189 merged, right? > > Shyam > On 2/13/19 4:09 AM, Raghavendra Gowdappa wrote: >> >> >> On Wed, Feb 13, 2019 at 2:24 PM Nithya Balachandran > <mailto:nbala...@redhat.com>> wrote: >> >> Adding Raghavendra G and Milind who are working on the patches so >> they can update on when they should be ready. >> >> On Fri, 8 Feb 2019 at 20:26, Shyam Ranganathan > <mailto:srang...@redhat.com>> wrote: >> >> Hi, >> >> There have been several crashes and issues reported by users on the >> latest 5.3 release. Around 10 patches have been merged since 5.3 >> and we >> have a few more addressing the blockers against 5.4 [1]. >> >> The original date was March 10th, but we would like to >> accelerate a 5.4 >> release to earlier this month, once all critical blockers are fixed. >> >> Hence there are 3 asks in this mail, >> >> 1) Packaging team, would it be possible to accommodate an 5.4 >> release >> around mid-next week (RC0 for rel-6 is also on the same week)? >> Assuming >> we get the required fixes by then. >> >> 2) Maintainers, what other issues need to be tracked as >> blockers? Please >> add them to [1]. >> >> 3) Current blocker status reads as follows: >> - Bug 1651246 - Failed to dispatch handler >> - This shows 2 patches that are merged, but there is no patch that >> claims this is "Fixed" hence bug is still in POST state. What other >> fixes are we expecting on this? >> - @Milind request you to update the status >> >> - Bug 1671556 - glusterfs FUSE client crashing every few days with >> 'Failed to dispatch handler' >> - Awaiting fixes for identified issues >> - @Nithya what would be the target date? >> >> >> Fix @ https://review.gluster.org/#/c/glusterfs/+/22189/ >> >> waiting on reviews. I am hoping to get this merged by end of this week >> and send a backport. >> >> >> - Bug 1671603 - flooding of "dict is NULL" logging & crash of >> client process
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-5.3 released
On 1/17/19 11:09 AM, Niels de Vos wrote: > On Wed, Jan 16, 2019 at 08:48:16PM +, jenk...@build.gluster.org wrote: >> SRC: >> https://build.gluster.org/job/release-new/77/artifact/glusterfs-5.3.tar.gz >> HASH: >> https://build.gluster.org/job/release-new/77/artifact/glusterfs-5.3.sha512sum > > Packages for CentOS 6 & 7 are available in the testing repository. > Please try them out and let me know when I can mark them for release to > the CentOS mirrors. Tested, good to release. Thanks! > > # yum install centos-release-gluster > # yum install glusterfs-server > > Thanks, > Niels > ___ > maintainers mailing list > maintain...@gluster.org > https://lists.gluster.org/mailman/listinfo/maintainers > ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-4.1.7 released
On 1/17/19 11:08 AM, Niels de Vos wrote: > On Wed, Jan 16, 2019 at 08:49:38PM +, jenk...@build.gluster.org wrote: >> SRC: >> https://build.gluster.org/job/release-new/78/artifact/glusterfs-4.1.7.tar.gz >> HASH: >> https://build.gluster.org/job/release-new/78/artifact/glusterfs-4.1.7.sha512sum > > Packages for CentOS 6 & 7 are available in the testing repository. > Please try them out and let me know when I can mark them for release to > the CentOS mirrors. Tested, good to release. Thanks! > > # yum install centos-release-gluster41 > # yum install glusterfs-fuse > > Thanks, > Niels > ___ > maintainers mailing list > maintain...@gluster.org > https://lists.gluster.org/mailman/listinfo/maintainers > ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-users] Announcing Gluster release 5.2
On 12/13/18 2:13 PM, Lindolfo Meira wrote: > Links for OpenSUSE Leap packages never work :/ I assume you are trying the link at [3] IOW, http://download.opensuse.org/repositories/home:/glusterfs:/Leap15-5/openSUSE_Leap_15/ That did not take me anywhere as well, but on backtracking the right link seems to be, http://download.opensuse.org/repositories/home:/glusterfs:/Leap15-5/openSUSE_Leap_15.0/ @Kaleb can you confirm? and if so we may need to modify [3] accordingly. [3] https://download.gluster.org/pub/gluster/glusterfs/5/5.2/SUSE/ ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-5.2 released
On 12/13/18 6:05 AM, Niels de Vos wrote: > On Thu, Dec 13, 2018 at 02:42:17AM +, jenk...@build.gluster.org wrote: >> SRC: >> https://build.gluster.org/job/release-new/76/artifact/glusterfs-5.2.tar.gz >> HASH: >> https://build.gluster.org/job/release-new/76/artifact/glusterfs-5.2.sha512sum > > Packages for CentOS 6 & 7 have been built and should become available > for testing shortly. Please try them out and report success/failures > back. Thanks! > > # yum install centos-release-gluster > # yum install glusterfs-server Tested client and server bits, works fine (including upgrade from 5.1). Please tag them for GA. > > > ___ > maintainers mailing list > maintain...@gluster.org > https://lists.gluster.org/mailman/listinfo/maintainers > ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
[gluster-packaging] Fwd: [Gluster-users] Announcing Glusterfs release 3.12.15 (Long Term Maintenance)
Packaging team, The arbiter stale lock issue seems to be biting a few folks (as per the traffic on the lists). Can we make a one-off 4.1 release in October for the same? Thanks, Shyam Forwarded Message Subject: Re: [Gluster-users] Announcing Glusterfs release 3.12.15 (Long Term Maintenance) Date: Wed, 17 Oct 2018 09:18:25 -0400 From: Shyam Ranganathan To: Dmitry Melekhov , gluster-us...@gluster.org On 10/17/2018 12:21 AM, Dmitry Melekhov wrote: > #1637989 <https://bugzilla.redhat.com/1637989>: data-self-heal in > arbiter volume results in stale locks. > > > Could you tell me, please, when 4.1 with fix will be released? Tagging the release is on the 20th of the month [1], packages should be available 2-3 days from then. Also, post the first 3-4 minor releases the release schedule was changed to releasing minor releases every 2 months [2]. This puts the next 4.1 release in November [3]. This bug seems critical enough to make a release earlier, so we may make a out of band release next week (20th of October), after discussing the same with the packaging team (will update the list once we make a decision). [1] Release schedule: https://www.gluster.org/release-schedule/ [2] Release cadence announce: https://lists.gluster.org/pipermail/announce/2018-July/000103.html [3] Next 4.1 release in the release notes: https://docs.gluster.org/en/latest/release-notes/4.1.5/ > > Thank you! > > > > > 16.10.2018 19:41, Jiffin Tony Thottan пишет: >> >> The Gluster community is pleased to announce the release of Gluster >> 3.12.15 (packages available at [1,2,3]). >> >> Release notes for the release can be found at [4]. >> >> Thanks, >> Gluster community >> >> >> [1] https://download.gluster.org/pub/gluster/glusterfs/3.12/3.12.15/ >> [2] https://launchpad.net/~gluster/+archive/ubuntu/glusterfs-3.12 >> <https://launchpad.net/%7Egluster/+archive/ubuntu/glusterfs-3.12> >> [3] https://build.opensuse.org/project/subprojects/home:glusterfs >> [4] Release notes: >> https://gluster.readthedocs.io/en/latest/release-notes/3.12.15/ >> >> >> ___ >> Gluster-users mailing list >> gluster-us...@gluster.org >> https://lists.gluster.org/mailman/listinfo/gluster-users > > > > > ___ > Gluster-users mailing list > gluster-us...@gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-users > ___ Gluster-users mailing list gluster-us...@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-users ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-5.0rc1 released
On 10/10/2018 03:58 AM, Niels de Vos wrote:
> On Fri, Oct 05, 2018 at 03:04:41PM -0400, Kaleb S. KEITHLEY wrote:
>> On 10/5/18 12:44 PM, jenk...@build.gluster.org wrote:
>>> SRC:
>>> https://build.gluster.org/job/release-new/71/artifact/glusterfs-5.0rc1.tar.gz
>>> HASH:
>>> https://build.gluster.org/job/release-new/71/artifact/glusterfs-5.0rc1.sha512sum
>>>
>>> This release is made off jenkins-release-71
>>>
>> GlusterFS 5.0rc1 Packages for:
>>
>> * el6, el7, el8 (CentOS, RHEL)...
>> * Fedora 27, 28, 29...
>> * Debian stretch/9, buster/10
>
> And since Monday the CentOS Storage SIG packages are also available.
> Sorry for forgetting to send out a note.
>
> 1. install centos-release-gluster5:
>- for CentOS-6:
> http://cbs.centos.org/kojifiles/packages/centos-release-gluster5/0.9/1.el6.centos/noarch/centos-release-gluster5-0.9-1.el6.centos.noarch.rpm
>- for CentOS-7:
> http://cbs.centos.org/kojifiles/packages/centos-release-gluster5/0.9/1.el7.centos/noarch/centos-release-gluster5-0.9-1.el7.centos.noarch.rpm
>
># yum install ${CENTOS_RELEASE_GLUSTER5_URL}
>
> 2. the centos-gluster5-test repository should be enabled by default, so
>
># yum install glusterfs-fuse
>
> 3. report back to this email
Tested install, upgrade procedure with heal and other client IO traffic
as well. All tests passed as required.
>
>
> Thanks!
> Niels
> ___
> maintainers mailing list
> maintain...@gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers
>
___
packaging mailing list
packaging@gluster.org
https://lists.gluster.org/mailman/listinfo/packaging
[gluster-packaging] Last minor release for 3.12?
Hi, 3.12 goes EOL with release-5, which is in about a week as most things are settled at present. We have the following open patches against 3.12: https://review.gluster.org/q/project:glusterfs+branch:release-3.12+status:open My thinking is that we do a final bug fix release for 3.12 (as the release is on the 10th of each month), before we EOL it. Thoughts? @Jiffin I would suggest we wait a day for any inputs else, tag and generate the 3.12.next release. Thanks, Shyam ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-5.0rc0 released
On 09/25/2018 05:36 PM, Niels de Vos wrote:
> On Tue, Sep 18, 2018 at 11:55:46AM -0400, Kaleb S. KEITHLEY wrote:
>> On 09/17/2018 08:44 PM, jenk...@build.gluster.org wrote:
>>> SRC:
>>> https://build.gluster.org/job/release-new/69/artifact/glusterfs-5.0rc0.tar.gz
>>> HASH:
>>> https://build.gluster.org/job/release-new/69/artifact/glusterfs-5.0rc0.sha512sum
>>>
>>> This release is made off jenkins-release-69
>
> Packages from the CentOS Storage SIG can now be tested from the testing
> repository. Please let me know if any dependencies are missing or when
> there are issues with any of the components.
>
> 1. install centos-release-gluster5:
>- for CentOS-6:
> http://cbs.centos.org/kojifiles/packages/centos-release-gluster5/0.9/1.el6.centos/src/centos-release-gluster5-0.9-1.el6.centos.src.rpm
>- for CentOS-7:
> http://cbs.centos.org/kojifiles/packages/centos-release-gluster5/0.9/1.el7.centos/src/centos-release-gluster5-0.9-1.el7.centos.src.rpm
The above should be:
http://cbs.centos.org/kojifiles/packages/centos-release-gluster5/0.9/1.el7.centos/noarch/centos-release-gluster5-0.9-1.el7.centos.noarch.rpm
IOW, not from src, but from arch directory, right Niels (cross checking)?
Corrected the same and installed (and upgraded from 4.1.5) client and
server bits for FUSE testing. Packages and dependencies look good.
>
># yum install ${CENTOS_RELEASE_GLUSTER5_URL}
>
> 2. the centos-gluster5-test repository should be enabled by default, so
>
># yum install glusterfs-fuse
>
> 3. report back to this email
>
> Thanks!
> Niels
> ___
> maintainers mailing list
> maintain...@gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers
>
___
packaging mailing list
packaging@gluster.org
https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-4.1.5 released
On 09/21/2018 10:55 AM, Niels de Vos wrote: > On Fri, Sep 21, 2018 at 02:14:45PM +, jenk...@build.gluster.org wrote: >> SRC: >> https://build.gluster.org/job/release-new/70/artifact/glusterfs-4.1.5.tar.gz >> HASH: >> https://build.gluster.org/job/release-new/70/artifact/glusterfs-4.1.5.sha512sum > > Packages for the CentOS Storage SIG are being built and should land in > the testing repositories soon. Please let me know if these packages work > OK for you. Tested, works fine and can be released. Thanks. > > # yum -y install centos-release-gluster > # yum -y --enablerepo=centos-gluster-test* install glusterfs-server > (run your tests) > > Thanks, > Niels > ___ > maintainers mailing list > maintain...@gluster.org > https://lists.gluster.org/mailman/listinfo/maintainers > ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-5.0rc0 released
We need the following projects tagged as well, 1) Glusterd2: @Kaushal I see https://github.com/gluster/glusterd2/tree/v5.0.0-rc0 is this the one? We need to version this 5.0rc0 as we are now in a different versioning scheme for GlusterFS. 2) gfapi-python: This needs to be py3 compliant as otherwise Fedora packaging will drop the same. @ppai request you look into this. Shyam On 09/17/2018 08:44 PM, jenk...@build.gluster.org wrote: > SRC: > https://build.gluster.org/job/release-new/69/artifact/glusterfs-5.0rc0.tar.gz > HASH: > https://build.gluster.org/job/release-new/69/artifact/glusterfs-5.0rc0.sha512sum > > This release is made off jenkins-release-69 > > > > ___ > maintainers mailing list > maintain...@gluster.org > https://lists.gluster.org/mailman/listinfo/maintainers > ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] glusterfs-4.1.2 released
On 07/26/2018 03:22 AM, Niels de Vos wrote: > On Wed, Jul 25, 2018 at 02:48:22PM -0400, Shyam Ranganathan wrote: >> On 07/24/2018 10:10 AM, Niels de Vos wrote: >>> On Tue, Jul 24, 2018 at 01:04:39PM +, jenk...@build.gluster.org wrote: >>>> SRC: >>>> https://build.gluster.org/job/release-new/63/artifact/glusterfs-4.1.2.tar.gz >>>> HASH: >>>> https://build.gluster.org/job/release-new/63/artifact/glusterfs-4.1.2.sha512sum >>>> >>>> This release is made off jenkins-release-63 >>> >>> CentOS packages have been built and should become available for testing >>> shortly. >> >> Tested the install and basic functioning of client and server bits on >> FUSE, found things to be in working order. > > Thanks! Packages have been marked for release and hopefully land on the > mirrors later today. > > We could setup a Jenkins job in the CentOS CI to do automated testing > once RPMs are built. Scripts that can be executed on client and server, > or an ansible playbook would be the easiest to integrate. Is there > someone that would like to provide these? Well I have been asking for (something like) this after posting my testing scheme around RPM sanity. It will save about 30 minutes of my time, each time we package, but more importantly help us around timezones to not delay this. This is how I test [1], so before we automate, is this acceptable? I see this scheme as viable for minor releases, for major releases we need to perform upgrade testing, which is more elaborate (test the doc and new options etc.) and needs more time to automate. I state this, so that we understand we can automate minor update RPM testing as I see it, but not for major versions *yet*. [1] Package testing: https://hackmd.io/-yC3Ol68SwaRWr8bzaL8pw# > > Niels > ___ packaging mailing list packaging@gluster.org https://lists.gluster.org/mailman/listinfo/packaging
[gluster-packaging] Release 4.1.1 and 3.12.11
Hi, 2 New releases have been packaged that address the CVE [1]. Request packaging team to get the packages out for testing, so that we can publish the versions at the earliest. Thanks, Shyam [1] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10841 ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-3.12.9 released
On 04/24/2018 04:11 PM, Niels de Vos wrote: > On Tue, Apr 24, 2018 at 02:16:05PM +, jenk...@build.gluster.org wrote: >> SRC: >> https://build.gluster.org/job/release-new/50/artifact/glusterfs-3.12.9.tar.gz >> HASH: >> https://build.gluster.org/job/release-new/50/artifact/glusterfs-3.12.9.sha512sum >> >> This release is made off jenkins-release-50 > > Packages have been built for Fedora 27 and the CentOS Storage SIG. > Please test and let us know if the packages can be released to the > mirrors. > > Fedora: > https://bodhi.fedoraproject.org/updates/FEDORA-2018-6dc9145693 > > CentOS: > # yum install centos-release-gluster > # yum --enablerepo=centos-gluster312-test install glusterfs-server Tested (using scheme as in [1]), and packages are found fine for release. [1] Package testing: https://hackmd.io/-yC3Ol68SwaRWr8bzaL8pw# ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-3.10.12 released
On 04/24/2018 04:12 PM, Niels de Vos wrote: > On Tue, Apr 24, 2018 at 02:26:27PM +, jenk...@build.gluster.org wrote: >> SRC: >> https://build.gluster.org/job/release-new/52/artifact/glusterfs-3.10.12.tar.gz >> HASH: >> https://build.gluster.org/job/release-new/52/artifact/glusterfs-3.10.12.sha512sum >> >> This release is made off jenkins-release-52 > > Packages have been built for Fedora 26 and the CentOS Storage SIG. > Please test and let us know if the packages can be released to the > mirrors. > > Fedora: > https://bodhi.fedoraproject.org/updates/FEDORA-2018-f9e0f1caf7 > > CentOS: > # yum install centos-release-gluster310 > # yum --enablerepo=centos-gluster310-test install glusterfs-server Tested (using scheme as in [1]), and packages are found fine for release. [1] Package testing: https://hackmd.io/-yC3Ol68SwaRWr8bzaL8pw# ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-4.0.1 released
On 03/21/2018 02:45 PM, Kaleb S. KEITHLEY wrote: > * RHEL and CentOS el7 and el6 (el6 client-side only) in CentOS Storage > SIG at [4]. > > All the LATEST and STM-4.0 symlinks have been created or updated to > point to the 4.0.1 release. > > Please test the CentOS packages and give feedback so that packages can > be tagged for release. Tested, works fine, good to go. ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-4.0.0 released (v4.0.0-2 respin)
On 03/12/2018 03:40 PM, Shyam Ranganathan wrote: >> Please test the CentOS packages and give feedback so that packages can >> be tagged for release. > Tested and the test passes! We are good to publish. Humble, are the container images done and published? Further, I am thinking we provide a readme of sorts on the download server, on how to get to the container image, here [1]. Thoughts? Shyam [1] https://download.gluster.org/pub/gluster/glusterfs/4.0/4.0.0-2/ ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-4.0.0 released
On 03/12/2018 08:35 AM, Niels de Vos wrote: > On Mon, Mar 12, 2018 at 04:41:02PM +0530, Humble Devassy Chirammal wrote: >> Hi Shyam, >> >> I was asking for centos release rpm for glusterfs 4 release. Any way I have >> figured it out >> https://github.com/CentOS-Storage-SIG/centos-release-gluster40 > That will only become available in CentOS Extras once there is an > email for the CentOS Announce mailinglist. The package is available for > centos-extras-testing, but there is no official CentOS repository that > we may use for that. > > Please refrain from using the package for non-testing activities until > it and all the other packages are available on the CentOS mirrors. +1 we need package testing completed, before we roll out the containers. Expect a mail on the thread [1] ack'ing the packages as good to go before creating the container images, like so [2] Shyam [1] 4.0.0-2 package request: http://lists.gluster.org/pipermail/maintainers/2018-March/004204.html [2] Mail acknowledging packages built are sane 3.10.11 example: http://lists.gluster.org/pipermail/maintainers/2018-March/004167.html ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-4.0.0 released
On 03/12/2018 12:59 AM, Humble Devassy Chirammal wrote: > What would be the release rpm for glusterd4 in centos storage sig? I assume glusterd2 is the question? @kaushal, can you help out here? > > --Humble > > > On Mon, Mar 12, 2018 at 6:31 AM, Shyam Ranganathan <srang...@redhat.com > <mailto:srang...@redhat.com>> wrote: > > On 03/11/2018 08:14 AM, Shyam Ranganathan wrote: > > Hi Packaging team (Kaleb), > > > > As mentioned in the threads we had an upgrade issue with 4.0, that broke > > backward compatibility. > > > > The fixes are ready and will be merged shortly into 4.0 branch. > > > > How do we go about packaging 4.0.0-2? Would you be taking in .patch > > files or should I tag again? > > I merged the changes and also updated the release notes with the extra > bug that is now fixed. > > Further I tagged this v4.0.0-2 and redid a release job: > https://build.gluster.org/job/release-new/46/ > <https://build.gluster.org/job/release-new/46/> > > I assume we redo GA packages with this tarball, and number it 4.0.0-2 as > is required. > > @Kaleb/@Niels lmk if there is something more I need to do. > > > > > The fixes are: > > - https://review.gluster.org/#/c/19696/ > <https://review.gluster.org/#/c/19696/> > > - https://review.gluster.org/#/c/19694/ > <https://review.gluster.org/#/c/19694/> > > > > Thanks, > > Shyam > > > > On 03/06/2018 10:25 AM, jenk...@build.gluster.org > <mailto:jenk...@build.gluster.org> wrote: > >> SRC: > > https://build.gluster.org/job/release-new/45/artifact/glusterfs-4.0.0.tar.gz > > <https://build.gluster.org/job/release-new/45/artifact/glusterfs-4.0.0.tar.gz> > >> HASH: > > https://build.gluster.org/job/release-new/45/artifact/glusterfs-4.0.0.sha512sum > > <https://build.gluster.org/job/release-new/45/artifact/glusterfs-4.0.0.sha512sum> > >> > >> This release is made off jenkins-release-45 > >> > >> > >> > >> ___ > >> maintainers mailing list > >> maintain...@gluster.org <mailto:maintain...@gluster.org> > >> http://lists.gluster.org/mailman/listinfo/maintainers > <http://lists.gluster.org/mailman/listinfo/maintainers> > >> > > ___ > > maintainers mailing list > > maintain...@gluster.org <mailto:maintain...@gluster.org> > > http://lists.gluster.org/mailman/listinfo/maintainers > <http://lists.gluster.org/mailman/listinfo/maintainers> > > > ___ > packaging mailing list > packaging@gluster.org <mailto:packaging@gluster.org> > http://lists.gluster.org/mailman/listinfo/packaging > <http://lists.gluster.org/mailman/listinfo/packaging> > > ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-3.10.11 released
On 03/02/2018 04:50 PM, Shyam Ranganathan wrote: >> * RHEL/CentOS el6 and el7 are built in CentOS Storage SIG and tagged for >> testing, but they have not appeared at [4] at the time of this writing. >> In the mean time they can be downloaded from [5]. Please test and give >> feedback on #gluster-devel on freenode or the gluster-devel mailing list >> so they can be tagged for release. > Tested, client and server packages upgrade and work as expected from > 3.10.10.to 3.10.11. > Are the CentOS SIG packages released? I would like to announce this release. Thanks, Shyam ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-4.0.0 released
On 03/06/2018 10:25 AM, jenk...@build.gluster.org wrote: > SRC: > https://build.gluster.org/job/release-new/45/artifact/glusterfs-4.0.0.tar.gz > HASH: > https://build.gluster.org/job/release-new/45/artifact/glusterfs-4.0.0.sha512sum > > This release is made off jenkins-release-45 Some call outs! 1) @kaushal GD2 tags for GA need to be created and shared (if not already done) 2) @humble Once the packages are created for CentOS SIG, and validated (usually by me), you would need to crank out the container images Thanks! > > > > ___ > maintainers mailing list > maintain...@gluster.org > http://lists.gluster.org/mailman/listinfo/maintainers > ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-4.0.0rc0 released
On 02/26/2018 01:53 PM, jenk...@build.gluster.org wrote: > SRC: > https://build.gluster.org/job/release-new/42/artifact/glusterfs-4.0.0rc0.tar.gz > HASH: > https://build.gluster.org/job/release-new/42/artifact/glusterfs-4.0.0rc0.sha512sum > > This release is made off jenkins-release-42 Please discard, built 4.0.0.rc0 again. Redoing with the right RC1 version. > > > > ___ > maintainers mailing list > maintain...@gluster.org > http://lists.gluster.org/mailman/listinfo/maintainers > ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-3.10.10 released
On 01/31/2018 09:28 AM, Kaleb S. KEITHLEY wrote:
> On 01/30/2018 02:08 PM, jenk...@build.gluster.org wrote:
>> SRC:
>> https://build.gluster.org/job/release-new/39/artifact/glusterfs-3.10.10.tar.gz
>> HASH:
>> https://build.gluster.org/job/release-new/39/artifact/glusterfs-3.10.10.sha512sum
>>
>> This release is made off jenkins-release-39
> Packages for:
>
> * Fedora 27 are on download.gluster.org at [1]. Fedora 26 are in the
> Fedora Updates or Updates-Testing repo. Use `dnf` to install. (Fedora 28
> will come later, or possibly not at all due to libtirpc and rpcgen changes.)
>
> * Debian Jessie/8, Stretch/9, and Buster/10(Sid) are on
> download.gluster.org at [1]
>
> * Ubuntu Trusty/14.04, Xenial/16.04, Artful/17.10, and Bionic/18.04 are
> on Launchpad at [2]
>
> * SuSE SLES12SP3 and Leap42.3 are on OpenSuSE Build Service at [3].
>
> * RHEL/CentOS el6 and el7 are built in CentOS Storage SIG and tagged for
> testing, but they have not appeared at [4] at the time of this writing.
> In the mean time they can be downloaded from [5]. Please test and give
> feedback on #gluster-devel on freenode or the gluster-devel mailing list
> so they can be tagged for release.
>
I tested the packages here. Also, tested an upgrade form .9 to .10 (from
a package standpoint). Things look good, and packages can be marked for
release.
As usual, testing methodology used is this:
https://hackmd.io/GYIwTADCDsDMCGBaArAUxAY0QFhBAbIgJwCMySIwJmAJvGMBvNEA#
(in case folks want to review and add as appropriate).
I will be announcing the release to the lists, shortly.
> The .../LTM-3.10 -> .../3.10/3.10.10 and .../3.10/LATEST ->
> .../3.10/3.10.10 symlinks have been updated
>
> [1] https://download.gluster.org/pub/gluster/glusterfs/3.10
> [2] https://launchpad.net/~gluster/+archive/ubuntu/glusterfs-3.10
> [3] https://build.opensuse.org/project/subprojects/home:glusterfs
> [4] https://buildlogs.centos.org/centos/{6,7}/storage/$arch/gluster-3.10
> [5] http://cbs.centos.org/kojifiles/packages/glusterfs/3.10.10/
>
> --
>
> Kaleb
>
___
packaging mailing list
packaging@gluster.org
http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-devel] [Gluster-Maintainers] Release 4.0: RC0 Tagged
All pending actions as noted in the mail are complete, and 4.0.0rc0 has been tagged. This brings us to the most important phase of 4.0 which is testing out things that are not covered in our automated regression runs and such. For now, let's get some packages (as soon as I trigger the release job) and expect to hear back more around the testing front in the upcoming days and weeks. Thanks, Shyam ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] Release 4.0: Releasing client bits for CentOS6
On 01/31/2018 09:42 AM, Niels de Vos wrote: > On Wed, Jan 31, 2018 at 09:13:26AM -0500, Kaleb S. KEITHLEY wrote: >> On 01/31/2018 09:02 AM, Shyam Ranganathan wrote: >>> Hi, >>> >>> In the gluster maintainers meeting last week, one of the topics touched >>> upon was, should we build CentOS6 client packages for 4.0? >>> >>> The reasoning being, upgrading servers to 4.0 requires moving from >>> CentOS6 (for installations on this base OS version) to CentOS7 and then >>> moving to 4.0 bits on CentOS7. >>> >>> The same across clients would be further tedious. >>> >>> As a result (and based on glusterd2 not being a part of the client >>> packages), should we build and release CentOS6 client packages for 4.0 >>> via the CentOS Storage SIG? >>> >>> This does not mean we run regression tests using CentOS6 clients, like >>> we never ran using CentOS7 bits in our regressions till date. >>> >>> Packaging team, thoughts? and what would it take to make it happen? If >>> agreed upon can it be done for RC0 itself? >> >> Since glusterd2 looks like it will be packaged separate from glusterfs >> we can probably continue to build and distribute glusterfs for el6 from >> the CentOS Storage SIG. > > This can easily be done if there would be a --without-server ./configure > option. At the moment that does not exist yet, so I prefer to wait with > building the packages for CentOS-6 (otherwise users will likely expect > to see glusterfs-server around). So this can be done for RC1 then? > >> And if EPEL has a golang compiler we should be able to do scratch builds >> of glusterd2 packages and distribute that via download.gluster.org. > > I suggest to only do this when users ask for a glusterfs-server on > CentOS-6, and they have a good reason not to move to CentOS-7. Agree. Also there has been not much noise on the initial mail with regards to this announcement in users, possibly post release we may see some noise. > > Niels > ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] Release 4.0: Releasing client bits for CentOS6
Hi, In the gluster maintainers meeting last week, one of the topics touched upon was, should we build CentOS6 client packages for 4.0? The reasoning being, upgrading servers to 4.0 requires moving from CentOS6 (for installations on this base OS version) to CentOS7 and then moving to 4.0 bits on CentOS7. The same across clients would be further tedious. As a result (and based on glusterd2 not being a part of the client packages), should we build and release CentOS6 client packages for 4.0 via the CentOS Storage SIG? This does not mean we run regression tests using CentOS6 clients, like we never ran using CentOS7 bits in our regressions till date. Packaging team, thoughts? and what would it take to make it happen? If agreed upon can it be done for RC0 itself? Other, thoughts on the same. Thanks, Shyam ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] Release 4.0: RC0 build tomorrow (at risk)
Hi Packaging team, Preparation for RC0 is ongoing, I am waiting on scores for this patch [1] (removing experimental code from the release branch) to go through, and the following items to be resolved before tagging RC0. Devel/maintainers, 1) https://review.gluster.org/#/c/18785/ needs a backport, which I have done [3] @niels/@jiffin please vote on the backport so that I know we are ready for this feature in 4.0. 2) https://review.gluster.org/#/c/19223/ (protocol: utilize the version 4 xdr) We need this for RC0, as this brings about the major protocol change in the code, and sooner we have this in a build that we can test the better. At present I do not have cycles to look at the failure here, @amar let us know the status tomorrow, based on which we can take a call on RC0 being tomorrow or postponed a day or two. Other exceptions noted [2] are either in or is too late to get in at the moment, and hence are out of scope for 4.0. Shyam [1] Patch removing experimental code: https://review.gluster.org/#/c/19389/ [2] 4.0 exceptions awaited: http://lists.gluster.org/pipermail/gluster-devel/2018-January/054315.html [3] Backport for lease APIs: https://review.gluster.org/#/c/19390/ ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-3.13.2 released
On 01/23/2018 07:51 AM, Niels de Vos wrote: > On Tue, Jan 23, 2018 at 11:56:04AM +0100, Niels de Vos wrote: >> On Mon, Jan 22, 2018 at 12:22:37PM -0500, Shyam Ranganathan wrote: >>> On 01/20/2018 08:32 AM, Niels de Vos wrote: >>>> On Sat, Jan 20, 2018 at 11:55:33AM +, jenk...@build.gluster.org wrote: >>>>> SRC: >>>>> https://build.gluster.org/job/release-new/38/artifact/glusterfs-3.13.2.tar.gz >>>>> HASH: >>>>> https://build.gluster.org/job/release-new/38/artifact/glusterfs-3.13.2.sha512sum >>>> >>>> Packages for CentOS 6 and 7 have been built and will become available in >>>> the testing repository within the next few hours. Please test and let me >>>> know when they can be marked for release. >>>> >>>> # yum install centos-release-gluster313 >>>> # yum --enablerepo=centos-gluster313-test install glusterfs-server >>> >>> There seems to be a problem with our userspace-rcu dependency. As >>> follows, if this package is updated, we get into the following >>> dependency issue. >>> >>> Niels, is there a way to get this corrected? >>> >>> ---> Package userspace-rcu.x86_64 0:0.7.16-3.el7 will be updated >>> --> Processing Dependency: liburcu-bp.so.1()(64bit) for package: >>> glusterfs-server-3.13.2-1.el7.x86_64 >>> --> Processing Dependency: liburcu-cds.so.1()(64bit) for package: >>> glusterfs-server-3.13.2-1.el7.x86_64 >>> ---> Package userspace-rcu.x86_64 0:0.10.0-3.el7 will be an update >>> --> Finished Dependency Resolution >>> Error: Package: glusterfs-server-3.13.2-1.el7.x86_64 >>> (@centos-gluster313-test) >>>Requires: liburcu-bp.so.1()(64bit) >>>Removing: userspace-rcu-0.7.16-3.el7.x86_64 (@centos-gluster310) >>>liburcu-bp.so.1()(64bit) >>>Updated By: userspace-rcu-0.10.0-3.el7.x86_64 (centos-gluster313) >>> ~liburcu-bp.so.6()(64bit) >>> Error: Package: glusterfs-server-3.13.2-1.el7.x86_64 >>> (@centos-gluster313-test) >>>Requires: liburcu-cds.so.1()(64bit) >>>Removing: userspace-rcu-0.7.16-3.el7.x86_64 (@centos-gluster310) >>>liburcu-cds.so.1()(64bit) >>>Updated By: userspace-rcu-0.10.0-3.el7.x86_64 (centos-gluster313) >>> ~liburcu-cds.so.6()(64bit) >> >> It seems that the glusterfs-3.13 packages got built against >> userspace-rcu-0.7 and not the newer 0.10 version. There seems to have >> been some kind of build-override in the >> storage7-gluster-common-candidate tag, removing the 0.7 version from >> there made the 0.10 version available for glusterfs-3.13. >> >> Next steps: >> - rebuild glusterfs-3.13.2 >> - verify none of the other versions that require 0.7 have been broken >> >> Note that it might have been possible that others can install >> glusterfs-3.13.x when EPEL is enabled. Fedora EPEL provides a (possibly >> and surely untested) compatible older version of userspace-rcu. Also, >> userspace-rcu was only updated in CentOS-7 for ppc64le/aarch64 fixes, >> these architectures are not available for CentOS-6. > > Packages are available now, please run your test again when you have the > time. The YUM metadata will need to get updated, so you may need to > clean that first: > > # yum -y --enablerepo=centos-gluster313-test clean all Tested, and works fine. Thanks for the rebuild. So, for CentOS6 the RPM version is still 3.13.2-1 and is bumped for CentOS7 only? As I tested on CentOS6 as well this time, and found only the 1 version available, hence asking. Otherwise, ready to be published. > > Thanks! > Niels > ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-3.13.2 released
On 01/20/2018 08:32 AM, Niels de Vos wrote: > On Sat, Jan 20, 2018 at 11:55:33AM +, jenk...@build.gluster.org wrote: >> SRC: >> https://build.gluster.org/job/release-new/38/artifact/glusterfs-3.13.2.tar.gz >> HASH: >> https://build.gluster.org/job/release-new/38/artifact/glusterfs-3.13.2.sha512sum > > Packages for CentOS 6 and 7 have been built and will become available in > the testing repository within the next few hours. Please test and let me > know when they can be marked for release. > > # yum install centos-release-gluster313 > # yum --enablerepo=centos-gluster313-test install glusterfs-server There seems to be a problem with our userspace-rcu dependency. As follows, if this package is updated, we get into the following dependency issue. Niels, is there a way to get this corrected? ---> Package userspace-rcu.x86_64 0:0.7.16-3.el7 will be updated --> Processing Dependency: liburcu-bp.so.1()(64bit) for package: glusterfs-server-3.13.2-1.el7.x86_64 --> Processing Dependency: liburcu-cds.so.1()(64bit) for package: glusterfs-server-3.13.2-1.el7.x86_64 ---> Package userspace-rcu.x86_64 0:0.10.0-3.el7 will be an update --> Finished Dependency Resolution Error: Package: glusterfs-server-3.13.2-1.el7.x86_64 (@centos-gluster313-test) Requires: liburcu-bp.so.1()(64bit) Removing: userspace-rcu-0.7.16-3.el7.x86_64 (@centos-gluster310) liburcu-bp.so.1()(64bit) Updated By: userspace-rcu-0.10.0-3.el7.x86_64 (centos-gluster313) ~liburcu-bp.so.6()(64bit) Error: Package: glusterfs-server-3.13.2-1.el7.x86_64 (@centos-gluster313-test) Requires: liburcu-cds.so.1()(64bit) Removing: userspace-rcu-0.7.16-3.el7.x86_64 (@centos-gluster310) liburcu-cds.so.1()(64bit) Updated By: userspace-rcu-0.10.0-3.el7.x86_64 (centos-gluster313) ~liburcu-cds.so.6()(64bit) > > Thanks, > Niels > ___ > maintainers mailing list > maintain...@gluster.org > http://lists.gluster.org/mailman/listinfo/maintainers > ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] Release 4.0: Making it happen! (GlusterD2)
On 01/11/2018 02:01 AM, Kaushal M wrote: >> - (thought/concern) Jenkins smoke job (or other jobs) that builds RPMs >> will not build GD2 (as the source is not available) and will continue as >> is (which means there is enough spec file magic here that we can specify >> during release packaging to additionally build GD2) > The glusterfs spec file can be updated to include building GD2 from > its release tarball. I don't remember exactly but, rpmbuild might have > ways to automatically download sources/dependencies. We can check if > this is true. > So, I do not know if this is a real problem (yet!). But I do hope I have conveyed my concern/problem right, hence restating below. The in (glusterfs) tree spec file if modified to build GD2 in addition by default, will fail to do so (or need changes) in the smoke jobs that we have, and this may need addressing. Kaushal, based on your thoughts, I assume the in tree spec file is changed to point to a specific release tarball (always) and remaining rpmbuild voodoo will make this happen. The question/concern though is that we need this updated for every release (minor or major) IMO. But, worth a start. My thought/suggestion is to write the spec in such a fashion (if at all possible) that makes it optional to build with GD2, hence can be used for packaging, but avoided in the smoke. Shyam ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] Release 4.0: Making it happen! (GlusterD2)
On 01/11/2018 02:04 AM, Kaushal M wrote: > On Thu, Jan 11, 2018 at 1:56 AM, Kaleb S. KEITHLEY <kkeit...@redhat.com> > wrote: >> comments inline >> >> On 01/10/2018 02:08 PM, Shyam Ranganathan wrote: >> >> Hi, (GD2 team, packaging team, please read) >> >> Here are some things we need to settle so that we can ship/release GD2 >> along with Gluster 4.0 release (considering this is a separate >> repository as of now). >> >> 1) Generating release package (read as RPM for now) to go with Gluster >> 4.0 release >> >> Proposal: >> - GD2 makes github releases, as in [1] >> >> - GD2 Releases (tagging etc.) are made in tandem to Gluster releases >> - So, when an beta1/RC0 is tagged for gluster release, this will >> receive a coordinated release (if required) from the GD2 team >> - GD2 team will receive *at-least* a 24h notice on a tentative >> Gluster tagging date/time, to aid the GD2 team to prepare the required >> release tarball in github >> >> This is a no-op. In github creating a tag or a release automatically creates >> the tar source file. Ah! yes so it does. Was not aware of this, but I guess what Kaushal adds below maybe valid as well. Will let you folks arrive at the right tarball (and possibly right location to pick it up from). The tarball mechanism as such (as discussed with Kaleb) stands I assume. > > While true, this tarball isn't enough. The GD2 build scripts lookup > versioning from git tags or from a VERSION file (same as glusterfs). > Both of these are not present in the tarball github generates. > The GD2 release script generates tarballs that have everything > required to build a properly versioned GD2. > >> >> - Post a gluster tag being created, and the subsequent release job is >> run for gluster 4.0, the packaging team will be notified about which GD2 >> tag to pick up for packaging, with this gluster release >> - IOW, a response to the Jenkins generated packaging job, with the >> GD2 version/tag/release to pick up >> >> - GD2 will be packaged as a sub-package of the glusterfs package, and >> hence will have appropriate changes to the glusterfs spec file (or other >> variants of packaging as needed), to generate one more package (RPM) to >> post in the respective download location >> >> - The GD2 sub-package version would be the same as the release version >> that GD2 makes (it will not be the gluster package version, at least for >> now) >> >> IMO it's clearer if the -glusterd2 sub-package has the same version as the >> rest of the glusterfs-* packages. >> > > +1. We will follow glusterfs versioning not just for the packages, but > for the source itself. Agreed! > >> The -glusterd2 sub-package's Summary and/or its %description can be used to >> identify the version of GD2. >> >> Emphasis on IMO. It is possible for the -glusterd sub-package to have a >> version that's different than the parent package(s). >> >> - For now, none of the gluster RPMs would be dependent on the GD2 RPM >> in the downloads, so any user wanting to use GD2 would have to install >> the package specifically and then proceed as needed >> >> - (thought/concern) Jenkins smoke job (or other jobs) that builds RPMs >> will not build GD2 (as the source is not available) and will continue as >> is (which means there is enough spec file magic here that we can specify >> during release packaging to additionally build GD2) >> >> 2) Generate a quick start or user guide, to aid using GD2 with 4.0 >> >> @Kaushal if this is generated earlier (say with beta builds of 4.0 >> itself) we could get help from the community to test drive the same and >> provide feedback to improve the guide for users by the release (as >> discussed in the maintainers meeting) >> >> One thing not covered above is what happens when GD2 fixes a high priority >> bug between releases of glusterfs. >> >> Once option is we wait until the next release of glusterfs to include the >> update to GD2. >> >> Or we can respin (rerelease) the glusterfs packages with the updated GD2. >> I.e. glusterfs-4.0.0-1 (containing GD2-1.0.0) -> glusterfs-4.0.0-2 >> (containing GD2-1.0.1). >> >> Or we can decide not to make a hard rule and do whatever makes the most >> sense at the time. If the fix is urgent, we respin. If the fix is not urgent >> it waits for the next Gluster release. (From my perspective though I'd >> rather not do respins, I've already got plenty of work doing the regular >> releases.) I would think we f
[gluster-packaging] Release 4.0: Making it happen! (GlusterD2)
Hi, (GD2 team, packaging team, please read) Here are some things we need to settle so that we can ship/release GD2 along with Gluster 4.0 release (considering this is a separate repository as of now). 1) Generating release package (read as RPM for now) to go with Gluster 4.0 release Proposal: - GD2 makes github releases, as in [1] - GD2 Releases (tagging etc.) are made in tandem to Gluster releases - So, when an beta1/RC0 is tagged for gluster release, this will receive a coordinated release (if required) from the GD2 team - GD2 team will receive *at-least* a 24h notice on a tentative Gluster tagging date/time, to aid the GD2 team to prepare the required release tarball in github - Post a gluster tag being created, and the subsequent release job is run for gluster 4.0, the packaging team will be notified about which GD2 tag to pick up for packaging, with this gluster release - IOW, a response to the Jenkins generated packaging job, with the GD2 version/tag/release to pick up - GD2 will be packaged as a sub-package of the glusterfs package, and hence will have appropriate changes to the glusterfs spec file (or other variants of packaging as needed), to generate one more package (RPM) to post in the respective download location - The GD2 package version would be the same as the release version that GD2 makes (it will not be the gluster package version, at least for now) - For now, none of the gluster RPMs would be dependent on the GD2 RPM in the downloads, so any user wanting to use GD2 would have to install the package specifically and then proceed as needed - (thought/concern) Jenkins smoke job (or other jobs) that builds RPMs will not build GD2 (as the source is not available) and will continue as is (which means there is enough spec file magic here that we can specify during release packaging to additionally build GD2) 2) Generate a quick start or user guide, to aid using GD2 with 4.0 @Kaushal if this is generated earlier (say with beta builds of 4.0 itself) we could get help from the community to test drive the same and provide feedback to improve the guide for users by the release (as discussed in the maintainers meeting). Thanks, Shyam [1] github GD2 releases: https://github.com/gluster/glusterd2/releases ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-3.10.7 released
On 10/31/2017 04:41 AM, Niels de Vos wrote: On Mon, Oct 30, 2017 at 05:28:35PM +, Gluster Build System wrote: SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.10.7.tar.gz This release is made off v3.10.7 Packages are available in the testing repository of the CentOS Storage SIG. Please test and let me know when they can be marked for release to the mirrors. # yum install centos-release-gluster310 # yum --enablerepo=centos-gluster310-test install glusterfs-server-3.10.7 (verify versions, run tests, ...) Niels quick question, where can I find the glusterfs debug info packages for the latest releases in the SIG? I am seeing 3.8 versions available but not later ones, maybe I am looking at the wrong places? Thanks, Niels ___ maintainers mailing list maintain...@gluster.org http://lists.gluster.org/mailman/listinfo/maintainers ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-3.10.7 released
On 10/31/2017 04:41 AM, Niels de Vos wrote: On Mon, Oct 30, 2017 at 05:28:35PM +, Gluster Build System wrote: SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.10.7.tar.gz This release is made off v3.10.7 Packages are available in the testing repository of the CentOS Storage SIG. Please test and let me know when they can be marked for release to the mirrors. # yum install centos-release-gluster310 # yum --enablerepo=centos-gluster310-test install glusterfs-server-3.10.7 (verify versions, run tests, ...) Tested above aspects for the provided packages, and things work as expected. Did a slightly different test, upgrading the RPMs from 3.10.6 to 3.10.7 from the server to check client backward compat and then the client, this went well as well. Packages are fine. FUSE and gluster server packages are tested. Thanks, Niels ___ maintainers mailing list maintain...@gluster.org http://lists.gluster.org/mailman/listinfo/maintainers ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-3.12.0 released
On 08/31/2017 11:06 AM, Shyam Ranganathan wrote: On 08/31/2017 10:11 AM, Niels de Vos wrote: * RHEL/CentOS el6 and el7 are in CentOS Storage SIG staging at [4]. Please test and give feedback on #gluster-devel on freenode or the gluster-devel mailing list so they can be moved to the staging area. ok, so I just tested the above, we now need to test the ones below as well? Packages for the CentOS Storage SIG are available in the testing repositories (for CentOS 6 & 7). In order to test these, you can most easily install the release package that enables the repository: - on CentOS 7: # yum installhttp://cbs.centos.org/kojifiles/work/tasks/7787/217787/centos-release-gluster312-0.9-1.el7.centos.noarch.rpm # yum install glusterfs-server - on CentOS 6: # yum installhttp://cbs.centos.org/kojifiles/work/tasks/7821/217821/centos-release-gluster312-0.9-1.el6.centos.noarch.rpm # yum install glusterfs-server I rolled my own repo file for testing the installs and such, as reported. So what else needs to be done here? Or, rather should we be doing the following as well? All dependencies should get pulled in automatically (CentOS Extras is enabled by default). If there are any problems with installing packages listed on [4], please let me know. Tested FUSE client and Gluster server packages, things work fine. See [1] to understand how/what was tested (the steps were slightly modified as I learn and also to adapt to the locations for the said repos). A centos-release-gluster312 package has been prepared for inclusion in CentOS Extras. Once this package is available on the mirrors, users will get glusterfs-3.12 when they "yum install centos-release-gluster". Before the sync to the CentOS mirrors can happen, I need a confirmation that the repositories are in a good state. After that, I can mark packages for releasing to the mirrors and get the new repositories included in the CentOS Teams sync-configuration. I assume what is done above is sufficient let me know otherwise. Possibly the next time we should get a single request, reduces the work till this install testing is manual. As a last step, I can request the new centos-release-gluster312 package to be included in CentOS Extras. This will need an email to the CentOS Announce list as well. [1] Package testing: https://hackmd.io/GYIwTADCDsDMCGBaArAUxAY0QFhBAbIgJwCMySIwJmAJvGMBvNEA# ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-3.12.0 released
On 08/31/2017 10:11 AM, Niels de Vos wrote: * RHEL/CentOS el6 and el7 are in CentOS Storage SIG staging at [4]. Please test and give feedback on #gluster-devel on freenode or the gluster-devel mailing list so they can be moved to the staging area. ok, so I just tested the above, we now need to test the ones below as well? Packages for the CentOS Storage SIG are available in the testing repositories (for CentOS 6 & 7). In order to test these, you can most easily install the release package that enables the repository: - on CentOS 7: # yum installhttp://cbs.centos.org/kojifiles/work/tasks/7787/217787/centos-release-gluster312-0.9-1.el7.centos.noarch.rpm # yum install glusterfs-server - on CentOS 6: # yum installhttp://cbs.centos.org/kojifiles/work/tasks/7821/217821/centos-release-gluster312-0.9-1.el6.centos.noarch.rpm # yum install glusterfs-server I rolled my own repo file for testing the installs and such, as reported. So what else needs to be done here? Or, rather should we be doing the following as well? All dependencies should get pulled in automatically (CentOS Extras is enabled by default). If there are any problems with installing packages listed on [4], please let me know. A centos-release-gluster312 package has been prepared for inclusion in CentOS Extras. Once this package is available on the mirrors, users will get glusterfs-3.12 when they "yum install centos-release-gluster". Before the sync to the CentOS mirrors can happen, I need a confirmation that the repositories are in a good state. After that, I can mark packages for releasing to the mirrors and get the new repositories included in the CentOS Teams sync-configuration. Possibly the next time we should get a single request, reduces the work till this install testing is manual. As a last step, I can request the new centos-release-gluster312 package to be included in CentOS Extras. This will need an email to the CentOS Announce list as well. ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
Re: [gluster-packaging] [Gluster-Maintainers] glusterfs-3.10.5 released
On 08/12/2017 11:56 AM, Niels de Vos wrote: On Sat, Aug 12, 2017 at 12:49:14PM +, Gluster Build System wrote: SRC: http://bits.gluster.org/pub/gluster/glusterfs/src/glusterfs-3.10.5.tar.gz This release is made off v3.10.5 Packages for the CentOS Storage SIG are available for testing. Please let me know when someone tried them (even minor checks are sufficient) so that I can mark them for releasing to the CentOS mirrors. # yum install centos-release-gluster310 # yum --enablerepo=centos-gluster310-test install \ glusterfs-server-3.10.5-1.el7 Done! - packages are fine and install ok (fuse-client and server) - Basic volume creation, mount and a few operations are succesful We can release this into the mirrors. I never received any feedback for the 3.10.4 packages, and have now tagged them for release (fingers crossed!). Once the CentOS team does a new sync run, the 3.10.4 packages will be available on the mirrors. Thanks, Niels ___ maintainers mailing list maintain...@gluster.org http://lists.gluster.org/mailman/listinfo/maintainers ___ packaging mailing list packaging@gluster.org http://lists.gluster.org/mailman/listinfo/packaging
