Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1359808 - resolveip is not IPv6 compatible
Summary: resolveip is not IPv6 compatible
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: mariadb
Version: rh-mariadb101
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.0
Assignee: Michal Schorm
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-25 13:27 UTC by Honza Horak
Modified: 2017-06-26 14:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-26 14:27:38 UTC


Attachments (Terms of Use)

Description Honza Horak 2016-07-25 13:27:41 UTC
Description of problem:
resolveip is not IPv6 compatible

See the comment in mariadb/mariadb-10.1.14/extra/resolveip.c:
"Not compatible with IPv6!  Probably should use getnameinfo()."

Version-Release number of selected component (if applicable):
rh-mariadb101-mariadb-10.1.14-2.el7

How reproducible:
not sure whether there are any real issues

Steps to Reproduce:
1. 
2.
3.

Actual results:
we have resolveip not working on IPv6 only machine

Expected results:
resolveip works even on IPv6 only machine

Additional info:

It seems that resolveip is used only in mysql_install_db.sh, and only in branch which is triggered by this option:
  --cross-bootstrap    For internal use.  Used when building the MariaDB system
                       tables on a different host than the target.

So it probably does not influence anything.

Comment 3 Honza Horak 2017-06-26 14:27:38 UTC
(In reply to Honza Horak from comment #0)
> It seems that resolveip is used only in mysql_install_db.sh, and only in
> branch which is triggered by this option:
>   --cross-bootstrap    For internal use.  Used when building the MariaDB
> system
>                        tables on a different host than the target.
> 
> So it probably does not influence anything.

Actually it's wise-versa, the resolvip is NOT used when --cross-bootstrap is used:

if test "$cross_bootstrap" -eq 0 -a "$in_rpm" -eq 0 -a "$force" -eq 0

But this ^ condition also shows that it is only used when --rpm is NOT used, which we do. So, it is still true, that this issue should not have any real consequences in our packages. Let's close it as WONTFIX then and feel free to re-open if there is some issue in real use case.


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