Job output not refreshing automatically in AWX 24.1.0 wit operator 2.14.0 #15071
Comments
github-actions
bot
added
component:ui
component:ui_next
needs_triage
type:bug
community
labels
|
Perhaps dup of: #15038 |
|
This was addressed in the 24.2.0 release. |
Edit: Ok i have resolved my pb by deleting on ansible.cfg |
|
@sysadmin-info are you still having this issue? if not, we can go ahead and close this ticket. Thanks! |
|
Hi,
I have not checked it yet. Close it. Until next week I will not have time
to perform a check.
Kind regards
…On Fri, Apr 12, 2024 at 7:44 PM Seth Foster ***@***.***> wrote:
@sysadmin-info <https://github.com/sysadmin-info> are you still having
this issue? if not, we can go ahead and close this ticket. Thanks!
—
Reply to this email directly, view it on GitHub
<#15071 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFULAOTUKG6G3MM35PSFNVLY5AMQTAVCNFSM6AAAAABF2H7QLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJSGIYDGMJTGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please confirm the following
[email protected]instead.)Bug Summary
HI,
the bug is identical like the one described here: #9747
No above solution works. I mean this functionality just does not work and it seems it is related to websocket.
Operator version 2.14.0
AWX version 24.1.0
Database clean installation: PostgreSQL 15
k3s version: v1.28.8+k3s1
OS: Debian 12 with kernel: 6.1.0-18-amd64
I see identical errors that the websocket is not working as expected like it is described in the URL I provided.
The additional error:
The error Uncaught DOMException: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state
indicates that the code is trying to send a message through the WebSocket before the connection has been fully established. This happens because the send method is called immediately after creating the WebSocket, but before the connection has completed the handshake with the server.
To resolve this issue, you should ensure that the send operation in the ws.onopen callback occurs only after the WebSocket connection is fully open. The onopen event is designed to handle this scenario, as it's triggered when the WebSocket connection has been established successfully.
Here's how you can modify the code to ensure the send method is called at the right time:
Version AWX 23.9.0 with Operator 2.12.2 and PostgreSQL 13 is working without any issue. It does not matter do you use NGINX Proxy Manager, ingress or without ingress or do you modify the coreDNS it just works. So I decided to not upgrade to the newest AWX operator, AWX and PostgreSQL.
AWX version
24.1.0
Select the relevant components
Installation method
kubernetes
Modifications
yes
Ansible version
2.14.3
Operating system
Debian 12
Web browser
Chrome
Steps to reproduce
Do not modify coreDNS. Do not install ingress.
Install HELM
curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bashPerform a check using http://IP_ADDRESS:30060
Expected results
Working standard output in jobs view.
Actual results
standard output in jobs does not work and it does not scroll the results of running ansible playbook. Websocket returns the same error like it is presented in the URL I provided.
Additional information
See logs from awx-web pod
logs from google chrome browser console in developer tools
See logs from k3s cluster pod for awx-web
The log snippets indicate interactions with various API endpoints and websocket connections under the /websocket/ path. Here's an analysis of the relevant parts and possible issues:
Websocket Connection Codes (101): The HTTP status code 101 in your logs suggests that websocket connections are being initiated and possibly established ("Switching Protocols"). However, there's an initial 404 error for the websocket endpoint, which could indicate a misconfiguration at some point in time.
Initial 404 Error: The first attempt to access /websocket/ resulted in a 404 (Not Found) error. This could imply that either the websocket service wasn't ready at that moment or there was a misconfiguration in the URL or routing.
Successful Connections: Subsequent attempts to connect to the websocket endpoint returned a 101 status, which means the server accepted the request to switch protocols from HTTP to WebSockets.
Other API Requests: The log shows successful HTTP requests (status 200) to various API endpoints, indicating that the regular HTTP API seems to be functioning well.
The text was updated successfully, but these errors were encountered: