Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-4955

Console fails to connect to Ansible Tower

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • MCE 2.3.0
    • MCE 2.2.Z, MCE 2.1.Z, MCE 2.3.0, MCE 2.0.Z
    • Console
    • None
    • 1
    • False
    • None
    • False
    • Console Sprint 2023-05
    • Critical
    • Yes

      Description of problem:

      After selecting an Ansible Automation Platform credential when creating/editing an automation template or creating/editing a policy automation, data fails to be fetched from Ansible Tower to list job or workflow job templates and inventories.

      Version-Release number of selected component (if applicable):

      MCE 2.0 - MCE 2.3

      How reproducible:

      Always

      Additional info:

      This problem occurs when the Node.js version is 18.14.0 or higher, which is the case in recent builds of both upstream and downstream images for Node.js v18. The problem is not present in any released versions of MCE but is preventing us from updating the base images to the latest, which may be required soon due to drops in container grade.

      The problem might actually be on the Ansible Tower side, revealed by bug fixes in Node.js. The error we get in the backend varies slightly depending on the Ansible Tower instance we are connecting to.

      https://acmqe-test-ansible.install.dev09.red-chesterfield.com/#/home
      Tower 3.8.5 / Ansible 2.9.27
      self-signed certificate

      ERROR:socket hang up, err{ type:Error, message:socket hang up, stack:Error: socket hang up
          at connResetException (node:internal/errors:717:14)
          at TLSSocket.socketOnEnd (node:_http_client:526:23)
          at TLSSocket.emit (node:events:525:35)
          at TLSSocket.emit (node:domain:489:12)
          at endReadableNT (node:internal/streams/readable:1359:12)
          at processTicksAndRejections (node:internal/process/task_queues:82:21), code:ECONNRESET }
      

      https://ansible-tower-web-svc-tower.apps.collective.aws.red-chesterfield.com/#/login
      Tower 3.8.1 / Ansible 2.9.16
      valid certificate

      ERROR:Premature close, err{ type:Error, message:Premature close, stack:Error [ERR_STREAM_PREMATURE_CLOSE]: Premature close
          at new NodeError (node:internal/errors:399:5)
          at ClientRequest.<anonymous> (node:internal/streams/pipeline:352:14)
          at ClientRequest.emit (node:events:525:35)
          at ClientRequest.emit (node:domain:489:12)
          at TLSSocket.socketCloseListener (node:_http_client:465:9)
          at TLSSocket.emit (node:events:525:35)
          at TLSSocket.emit (node:domain:489:12)
          at node:net:322:12
          at TCP.done (node:_tls_wrap:588:7), code:ERR_STREAM_PREMATURE_CLOSE }
      

              rh-ee-kcormier Kevin Cormier
              rh-ee-kcormier Kevin Cormier
              David Huynh David Huynh
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: