Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJan Pazdziora (Red Hat)
2013-06-05 15:10:15 UTC
Description of problem:
I did run command
ipa-getkeytab -s server.example.com -p HTTP/broker.example.net -k /var/www/openshift/broker/httpd/conf.d/http.keytab
under es_ES.utf8 locales (export LC_ALL=es_ES.utf8; export LANG=es_ES.utf8) and it ended with
Failed to add key to the keytab
I would expect localized message.
Version-Release number of selected component (if applicable):
ipa-client-3.0.0-26.el6_4.2.x86_64
How reproducible:
Deterministic.
Steps to Reproduce:
1. Set Spanish locales.
2. Have server and principal and try to run ipa-getkeytab with -k parameter pointing to nonexistent directory.
Actual results:
Failed to add key to the keytab
Expected results:
No se pudo agregar clave de la tabla de claves
Additional info:
I believe that no localization works for IPA CLI tools because the .mo file is ipa.mo (for example /usr/share/locale/es/LC_MESSAGES/ipa.mo) while the bindtextdomain(PACKAGE, LOCALEDIR); is called with PACKAGE set to ipa-client or ipa-server.
When I do
cd /usr/share/locale/es/LC_MESSAGES ; ln -s ipa.mo ipa-client.mo
the command ipa-getkeytab reports Spanish message.
Comment 2Jan Pazdziora (Red Hat)
2013-06-05 15:12:36 UTC
Of course, completeness of the localization is another issue
$ git grep 'Failed to add key to the keytab'
install/po/es.po:msgid "Failed to add key to the keytab\n"
install/po/fr.po:msgid "Failed to add key to the keytab\n"
install/po/ipa.pot:msgid "Failed to add key to the keytab\n"
install/po/pl.po:msgid "Failed to add key to the keytab\n"
install/po/uk.po:msgid "Failed to add key to the keytab\n"
ipa-client/ipa-getkeytab.c: _("Failed to add key to the keytab\n"));
but getting what we have to actually work (it seems like a packaging error) would be a good start. And testing it.
and when pointing to a non-existent dir:
# ipa-getkeytab -s `hostname` -p HTTP/cloud-qe-3.testrelm.test -k /aaa/nk.keytab
No se pudo agregar clave de la tabla de claves
[translates to - Failed to add key key table]
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2015-0442.html