Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enterprise: websocket and streaming endpoints fail with audit logging enabled #9319

Closed
drewbailey opened this issue Nov 11, 2020 · 1 comment · Fixed by #9320
Closed

Enterprise: websocket and streaming endpoints fail with audit logging enabled #9319

drewbailey opened this issue Nov 11, 2020 · 1 comment · Fixed by #9320
Assignees
Labels
theme/enterprise Issues related to Enterprise features type/bug

Comments

@drewbailey
Copy link
Contributor

When audit logging is enabled on enterprise nomad agents, nomad alloc exec fails to upgrade the connection to a websocket. Streaming HTTP requests like nomad monitor and nomad alloc logs -f also fail to flush when sending new output.

               Test:           TestE2E/Nomad_exec/*nomadexec.NomadExecE2ETest_(docker)/TestExecBasicResponses/tty:_streaming
=== RUN   TestE2E/Nomad_exec/*nomadexec.NomadExecE2ETest_(docker)/TestExecBasicResponses/tty:_stty_check
    exec.go:93:
                Error Trace:    exec.go:93
                Error:          Received unexpected error:
                                Unexpected response code: 500 (Internal Server Error
                                failed to upgrade connection: websocket: response does not implement http.Hijacker)
                Test:           TestE2E/Nomad_exec/*nomadexec.NomadExecE2ETest_(docker)/TestExecBasicResponses/tty:_stt
@drewbailey drewbailey self-assigned this Nov 11, 2020
@drewbailey drewbailey added type/bug theme/enterprise Issues related to Enterprise features labels Nov 11, 2020
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
theme/enterprise Issues related to Enterprise features type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant