kurokobo
commented
7 months ago Perhaps dup of: https://github.com/ansible/awx/issues/15038 It's already addressed and the fix will be shipped with the next versioned release.
Closed sysadmin-info closed 6 months ago
kurokobo
commented
7 months ago Perhaps dup of: https://github.com/ansible/awx/issues/15038 It's already addressed and the fix will be shipped with the next versioned release.
bbourchanin
commented
7 months ago Still have "Minified React error #188;" on 24.2.0.
When i append url with "?lang=fr" or "?lang=en", or "?no_stdout=" ... it works
Edit: Ok i have resolved my pb by deleting on ansible.cfg
fosterseth
commented
7 months ago @sysadmin-info are you still having this issue? if not, we can go ahead and close this ticket. Thanks!
sysadmin-info
commented
7 months ago 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 https://github.com/ansible/awx/issues/15071#issuecomment-2052203130, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFULAOTUKG6G3MM35PSFNVLY5AMQTAVCNFSM6AAAAABF2H7QLSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJSGIYDGMJTGA . You are receiving this because you were mentioned.Message ID: @.***>
TheRealHaoLiu
commented
6 months ago @sysadmin-info thanks for the extremely detailed issue, please check the latest release to see if the problem can be reproduced
as for the UI change please submit a PR.
closing this issue for now since its been more than a month and other have reported the root cause has been addressed
rexberg
Please confirm the following
security@ansible.cominstead.)Bug Summary
HI,
the bug is identical like the one described here: https://github.com/ansible/awx/issues/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
install newest k3s using this command:
Do not modify coreDNS. Do not install ingress.
Install HELM
Install the newest AWX version with newest AWX operator from the scratch using the below ansible playbook:
Perform 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.