#1245 "Error looking up public keys" while ssh to replica using IP address.
Closed: Fixed None Opened 8 years ago by sgallagh.

https://bugzilla.redhat.com/show_bug.cgi?id=801719 (Red Hat Enterprise Linux 6)

+++ This bug was initially created as a clone of Bug #801410 +++

Description of problem:


Version-Release number of selected component (if applicable):
ipa-server-2.2.0-3.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install ipa-server with dns
2. Install ipa-server replica

3. [root@primenova ~]# ipa dnsrecord-find example.com goldbug
  Record name: @
  NS record: primenova.example.com., goldbug.example.com.
...
  Record name: goldbug
  A record: 10.65.201.101
  SSHFP record: 1 1 A7E007E7EFF842656F17C0A12BEDAD7522C04C1B, 2 1
BED1634D80799DEFDE344DAFDDDF8B56E0EB75E5
-----------------------------
Number of entries returned 10
-----------------------------

4. [root@primenova ~]# ssh goldbug.example.com
root@goldbug.example.com's password:

5. [root@primenova ~]# ssh 10.65.201.101


Actual results:
Error looking up public keys
root@10.65.201.101's password:

Expected results:
Reverse SSHFP lookup should be successful and "Error looking up public keys"
should not be displayed.

Additional info:


--- Additional comment from mkosek@redhat.com on 2012-03-09 04:20:41 EST ---

This check is for SSSD, I wil clone the BZ to this component. I can leave this
BZ as a tracker for IPA.

Fields changed

blockedby: =>
blocking: =>
coverity: =>
feature_milestone: =>
owner: somebody => jcholast
status: new => assigned
tests: => 0
testsupdated: => 0
upgrade: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.8.2 (LTM)
priority: major => blocker

Fixed by:
- master
- bd03e67
- d0a8981
- sssd-1-8
- 0a5a81f
- 7d862a1

resolution: => fixed
status: assigned => closed

See freeipa ticket https://fedorahosted.org/freeipa/ticket/2657

The issue is still there.
Reopening.

milestone: SSSD 1.8.2 (LTM) => NEEDS_TRIAGE
priority: blocker => major
resolution: fixed =>
status: closed => reopened

Re-closing. The issue reported there is new and completely different from this ticket. It just coincidentally prints the same error message.

milestone: NEEDS_TRIAGE => SSSD 1.8.2 (LTM)
priority: major => blocker
resolution: => fixed
status: reopened => closed

Metadata Update from @sgallagh:
- Issue assigned to jcholast
- Issue set to the milestone: SSSD 1.8.2 (LTM)

3 years ago

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

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2287

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.

Login to comment on this ticket.

Metadata