Bug 1423063 - glusterfs-fuse RPM now depends on gfapi
Summary: glusterfs-fuse RPM now depends on gfapi
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: packaging
Version: 3.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anoop C S
QA Contact:
URL:
Whiteboard:
Depends On: 1423448
Blocks: glusterfs-3.10.0
TreeView+ depends on / blocked
 
Reported: 2017-02-17 00:35 UTC by Shyamsundar
Modified: 2017-03-06 17:46 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.10.0
Clone Of:
: 1423448 (view as bug list)
Environment:
Last Closed: 2017-02-27 15:29:27 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Shyamsundar 2017-02-17 00:35:48 UTC
Description of problem:
While upgrading from 3.8.8 to 3.10, I found that glusterfs-fuse now has a dependency to glusterfs-api package, this is due to gf_attach.

Version-Release number of selected component (if applicable):
3.10

How reproducible:
Always

Steps to Reproduce:
1. Upgrade the rpms on a client from 3.8.8. to 3.10 and this new dependency will show up

Additional info:

Based on the mail thread discussion, we need to package this along with glusterfs-server, as it is more useful at the server end of things.

Comment 1 Worker Ant 2017-02-17 16:34:22 UTC
REVIEW: https://review.gluster.org/16664 (build: Add gf_attach to glusterfs-server package) posted (#1) for review on release-3.10 by Anoop C S (anoopcs)

Comment 2 Worker Ant 2017-02-18 18:23:47 UTC
COMMIT: https://review.gluster.org/16664 committed in release-3.10 by Shyamsundar Ranganathan (srangana) 
------
commit 62936feedb7f085259763594d11af34060a42fc9
Author: Anoop C S <anoopcs>
Date:   Fri Feb 17 12:37:27 2017 +0530

    build: Add gf_attach to glusterfs-server package
    
    Previously gf_attach was listed under glusterfs-fuse sub-package which
    introduced the dependency for glusterfs-api. So as per the discussion
    on gluster-devel[1] moving it to glusterfs-server.
    
    [1] http://lists.gluster.org/pipermail/gluster-devel/2017-February/052111.html
    
    > Change-Id: I3d646d7c2e556d8f37e6da67bdedd0738739e01b
    > BUG: 1423448
    > Signed-off-by: Anoop C S <anoopcs>
    > Reviewed-on: https://review.gluster.org/16660
    > Smoke: Gluster Build System <jenkins.org>
    > Reviewed-by: Shyamsundar Ranganathan <srangana>
    > Reviewed-by: Niels de Vos <ndevos>
    > NetBSD-regression: NetBSD Build System <jenkins.org>
    > CentOS-regression: Gluster Build System <jenkins.org>
    
    (cherry picked from commit 8e7a8ea818a1cc7fb23b412023a735b3939194f4)
    
    Change-Id: I3d646d7c2e556d8f37e6da67bdedd0738739e01b
    BUG: 1423063
    Signed-off-by: Anoop C S <anoopcs>
    Reviewed-on: https://review.gluster.org/16664
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Niels de Vos <ndevos>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>

Comment 3 Shyamsundar 2017-02-27 15:29:27 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.0, please open a new bug report.

glusterfs-3.10.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/gluster-devel/2017-February/052173.html
[2] https://www.gluster.org/pipermail/gluster-users/

Comment 4 Shyamsundar 2017-03-06 17:46:38 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.0, please open a new bug report.

glusterfs-3.10.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://lists.gluster.org/pipermail/gluster-users/2017-February/030119.html
[2] https://www.gluster.org/pipermail/gluster-users/


Note You need to log in before you can comment on or make changes to this bug.