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

ingress_path will never work #684

Closed
jpic opened this issue Dec 7, 2021 · 2 comments
Closed

ingress_path will never work #684

jpic opened this issue Dec 7, 2021 · 2 comments

Comments

@jpic
Copy link

jpic commented Dec 7, 2021

ISSUE TYPE
  • Bug Report
SUMMARY

Currently, the ingress_path setting allows to deploy AWX in a sub path such as /foo instead of /.

However, AWX is unable to serve from anywhere else than / because it builds an index.html that has /static/ links generated by webpack, NOT by Django, as such, does not respect STATIC_URL.

As such, the ingress_path setting will never work before ansible/awx#631 is fixed.

ENVIRONMENT
  • AWX version: Any
  • Operator version: Any
  • Kubernetes version: Any
  • AWX install method: Any
STEPS TO REPRODUCE

Set ingress_path to anything that is not /, such as /foo

EXPECTED RESULTS

AWX loading static from /foo/static/main.xxx.js

ACTUAL RESULTS

AWX failing to load static from /static/main.xxx.js

ADDITIONAL INFORMATION

AWX issue that has been closed but should probably reopen: ansible/awx#631 (comment)

Or, remove ingress_path feature because it can't work.

@shanemcd
Copy link
Member

This will be addressed by #652 and ansible/awx#11342

@shanemcd
Copy link
Member

shanemcd commented Feb 9, 2022

PRs have been merged. This will be in the next release, or you can build from devel in the meantime.

@shanemcd shanemcd closed this as completed Feb 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants