Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-27689

REX/AnsibleREX job fails to run on on IPV6 host when its registered to IPv4 Satellite

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • 0
    • Important
    • None

      Description of problem:

       

      How reproducible:

      Always

      Is this issue a regression from an earlier version:

      No

      Steps to Reproduce:

      1. Sync RHEL repositories, publish CV, Create AK on Satellite with IPv4

      2. Register a host with a workaround from https://issues.redhat.com/browse/SAT-27688

      3. Try to run a REX/AnsibleREX job on IPv6 host

      Actual behavior:
      IPv6 host can't reach to the Satellite with FQDN or IP causing REX/AnsibleREX job to fail with following error,

      1:Error initializing command: RuntimeError - Could not establish connection to remote host using any available authentication method, tried publickey
      2: 
      3:Authentication method 'publickey' failed with:
      4:ssh: connect to host 2620:52:0:9f:f816:3eff:fe8d:7871 port 22: Network is unreachable
      5:Exit status: EXCEPTION
      6:StandardError: Job execution failed 

      Expected behavior:

      IPv6 host can be reached to IPv4 Satellite directly or with a proxy jump, and REX/AnsibleREX job runs successfully on IPv6 host

      Business Impact / Additional info:

      foreman-proxy user is able to ssh to IPv6 host using a proxy jump

      [root@satellite-ipv4 ~]# ssh -J root@infra-ipv64-proxy.redhat.com -i ~foreman-proxy/.ssh/id_rsa_foreman_proxy root@host-ipv6.redhat.com "cat /etc/redhat-release"
      root@infra-ipv64-proxy.redhat.com's password:
      Red Hat Enterprise Linux release 9.4 (Plow) 

       

            Unassigned Unassigned
            gtalreja@redhat.com Gaurav Talreja
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: