-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
ACM 2.15.0, ACM 2.14.1
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
-
Critical
-
Yes
Description of problem:
Ran cluster-curator and created an application with prehooks and they were not able to successfully get info from the tower of the status of the triggered job. The job gets triggered successfully and runs; however, the status of the job is not updated.
Version-Release number of selected component (if applicable):
AAP 2.5.0+0.1758147817
AAP 2.6.0+0.1758169100
How reproducible:
Always
Steps to Reproduce:
- Create a cluster with cluster-curator
- Notice stalling of prehook container and cluster-curator job
- Create an application with ansible hooks
- Notice status does not get updated
Actual results:
- Cluster Lifecycle
(base) almng@almng-mac CLC % kubectl -n almng-mgd-aap25 get job.batch/prehookjob-nn78h
Error from server (NotFound): jobs.batch "prehookjob-nn78h" not found
- Application Lifecycle
TASK [job_runner : Gather Job Info] ******************************************** fatal: [localhost]: FAILED! => {"msg": "An unhandled exception occurred while running the lookup plugin 'ansible.controller.controller_api'. Error was a <class 'ansible.errors.AnsibleError'>, original message: There was an unknown error when trying to connect to https://127.0.0.1/api/controller/v2/jobs/?id=27: URLError <urlopen error [Errno 111] Connection refused>. There was an unknown error when trying to connect to https://127.0.0.1/api/controller/v2/jobs/?id=27: URLError <urlopen error [Errno 111] Connection refused>"}
In both instances, the AnsibleJob is run on the AAP console and is successful.
Expected results:
AnsibleJob is successful.