Red Hat Bugzilla – Bug 740850
hbactest does not resolve canonical names during simulation.
Last modified: 2011-12-06 13:32:23 EST
Description of problem: During hbacrule-add-host, adding canonical names e.g. "scroponok" resolves them to "scroponok.lab.eng.pnq.redhat.com", however, during ipa hbactest, entering "scroponok" doesn't work. I had to enter "scroponok.lab.eng.pnq.redhat.com" explicitly. Version-Release number of selected component (if applicable): ipa-server-2.1.1-4.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. [root@kungfupanda ~]# ipa hbacrule-add-host Rule name: rule1 [member host]: cavenger [member host group]: Rule name: rule1 Enabled: TRUE Hosts: cavenger.lab.eng.pnq.redhat.com ------------------------- Number of members added 1 ------------------------- 2.[root@kungfupanda ~]# ipa hbactest User name: kaushik Source host: scroponok.lab.eng.pnq.redhat.com Target host: cavenger.lab.eng.pnq.redhat.com Service: sshd -------------------- Access granted: True -------------------- 3. # ipa hbactest User name: kaushik Source host: scroponok Target host: cavenger Service: sshd --------------------- Access granted: False --------------------- Actual results: Does not resolve the canonical name and displays "Access granted: False" Expected results: Should resolve canonical name and display "Access granted: True" as it does while entering the complete fqdn. Additional info:
Upstream ticket: https://fedorahosted.org/freeipa/ticket/1862
Fixed upstream master: 3e1c04f9333ac3f4333d5cf99579e85a44c9573b ipa-2-1: caaacc9a611c5e3230189b2c4636e7d568c21f45
[root@bumblebee ~]# ipa hbactest User name: user1 Source host: external Target host: bumblebee Service: vsftpd -------------------- Access granted: True -------------------- matched: allow_all matched: rule1 [root@bumblebee ~]# Verified. Version: ipa-server-2.1.3-3.el6.x86_64
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Do not document
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. http://rhn.redhat.com/errata/RHSA-2011-1533.html