Bug 1553938 - configure summary TIRPC result is misleading
Summary: configure summary TIRPC result is misleading
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: build
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-09 23:11 UTC by James Le Cuirot
Modified: 2018-06-20 18:01 UTC (History)
1 user (show)

Fixed In Version: glusterfs-v4.1.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-20 18:01:56 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description James Le Cuirot 2018-03-09 23:11:40 UTC
Description of problem:
Requesting ipv6-default even if you explicitly disable libtirpc will then implicitly enable libtirpc because that is required. That is fine but the configure summary then shows TIRPC as disabled when it is not.

The result could also be made clearer by stating that TIRPC is "missing" when it has been tried but not found.

This should be looked at following bug #1553926 otherwise the configure line below will not do what you expect.

Version-Release number of selected component (if applicable):
4.0.0, master (940f870f) with my fix for bug #1553926 applied.

How reproducible:
Always.

Steps to Reproduce:
./configure --with-ipv6-default --without-libtirpc

Actual results:
IPV6 default         : yes
Use TIRPC            : no

Expected results:
IPV6 default         : yes
Use TIRPC            : yes

Comment 1 Worker Ant 2018-03-09 23:13:49 UTC
REVIEW: https://review.gluster.org/19693 (build: Fix misleading TIRPC result in configure summary) posted (#1) for review on master by James Le Cuirot

Comment 2 Worker Ant 2018-03-24 05:14:59 UTC
COMMIT: https://review.gluster.org/19693 committed in master by "Amar Tumballi" <amarts> with a commit message- build: Fix misleading TIRPC result in configure summary

Requesting ipv6-default even if you explicitly disable libtirpc will
then implicitly enable libtirpc because that is required. That is fine
but the configure summary should not then show TIRPC as disabled when
it is not.

The result has also been made clearer by stating that TIRPC is
"missing" when it has been tried but not found.

BUG: 1553938
Change-Id: I945bd6859aaf3defa682b0d05ee34a9827b9c45f
Signed-off-by: James Le Cuirot <chewi>

Comment 3 Shyamsundar 2018-06-20 18:01:56 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-v4.1.0, please open a new bug report.

glusterfs-v4.1.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/announce/2018-June/000102.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.