#47414 remove-ds.pl is locale sensitive
Closed: wontfix Opened by rmeggins.

Ticket was cloned from Red Hat Bugzilla (product Fedora EPEL): Bug 969674

Version-Release number of selected component (if applicable):
389-ds-base-1.2.11.15-14.el6_4.x86_64
How reproducible:
each time
Steps to Reproduce:
1.try to remove a instance with remove-ds.pl with a locale different from en-US
2.
3.
Actual results:
# remove-ds.pl -i slapd-elspeth
The following errors occurred during removal:
Error: could not remove selinux label from port '389'.  Error:
/usr/sbin/semanage: Le port tcp/389 est d?fini dans la strat?gie, il ne peut
?tre supprim?
Expected results:
no error message.
Additional info:
the problem is because I run my system with LANG=fr_FR.utf8, so semange error
message are translated, and so the error message is not correctly matched on
removeDSInstance, in this part of the code.
      foreach my $secureport (@{$entry->{"nsslapd-secureport"}})
        {
            my $semanage_err = `semanage port -d -t ldap_port_t -p tcp
$secureport 2>&1`;
            if ($? != 0)  {
                if (($semanage_err !~ /defined in policy, cannot be deleted/)
&& ($semanage_err !~ /is not defined/)) {
                    push @errs, [ 'error_removing_port_label', $secureport,
$semanage_err];
                    debug(1, "Warning: Port $secureport not removed from
selinux policy correctly.  Error: $semanage_err\n");
                }
            }
        }

Luckily, I've never run into the problem before, but if semanage failed I'd have seen the error...

echo $LANG

ja_JP.utf8

semanage port -d -t ldap_port_t -p tcp 11111

/sbin/semanage: ポート tcp/11111 はポリシーで定義されています、 削除できません

semanage port -d -t ldap_port_t -p tcp 22222

/sbin/semanage: ポート tcp/22222 は定義されていません

Duplicate of https://fedorahosted.org/389/ticket/563

Fixed in 389-ds-base-1.3.1.0-1

Metadata Update from @nhosoi:
- Issue set to the milestone: 1.3.3 - 1/14 (January)

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/751

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Duplicate)

Metadata