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

Selfbuild AWX does not Start, daphne has Missing or incorrect metadata for Tower version #1120

Closed
FloThinksPi opened this issue Feb 2, 2018 · 4 comments

Comments

@FloThinksPi
Copy link

ISSUE TYPE
  • Bug Report
COMPONENT NAME
  • Installer
SUMMARY

When Building AWX Tag 1.0.2 the Build produces a awx-0.0.0.tar.gz instead of one with a version number. So one have to do

cp awx/dist/awx-0.0.0.tar.gz awx/dist/awx-1.0.2.1.tar.gz

and rerun the playbook.

The Container then start and are listening to port 80. Howerver the webserver only responds with a internal server error.

In the Logs there is the cause:

2018-02-02 15:11:58,833 ERROR    Missing or incorrect metadata for Tower version.  Ensure Tower was installed using the setup playbook.
Traceback (most recent call last):
  File "/var/lib/awx/venv/awx/bin/daphne", line 11, in <module>
    sys.exit(CommandLineInterface.entrypoint())
  File "/var/lib/awx/venv/awx/lib/python2.7/site-packages/daphne/cli.py", line 144, in entrypoint
    cls().run(sys.argv[1:])
  File "/var/lib/awx/venv/awx/lib/python2.7/site-packages/daphne/cli.py", line 174, in run
    channel_layer = importlib.import_module(module_path)
  File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in import_module
    __import__(name)
  File "/usr/lib/python2.7/site-packages/awx/asgi.py", line 31, in <module>
    raise Exception("Missing or incorrect metadata for Tower version.  Ensure Tower was installed using the setup playbook.")
Exception: Missing or incorrect metadata for Tower version.  Ensure Tower was installed using the setup playbook.
2018-02-02 15:11:58,876 INFO exited: daphne (exit status 1; not expected)

Which leads to a always restarting daphne.
So how is the version information set in AWX. Did i miss something.
The Docu only tells to execute the playbook.

ENVIRONMENT

AWX version: 1.0.2
AWX install method: build without docker-compose
Ansible version: 2.4
Operating System: RHEL 7.4

@FloThinksPi
Copy link
Author

This also happened with 1.0.3.
i found a file called VERSION in the root of the repo after building both versions. However the file was always empty.

@FloThinksPi
Copy link
Author

FloThinksPi commented Feb 5, 2018

Ok this is because RHEL7 uses Git 1.8.3. I compiled my own git 2.16.x and it works now.

@geerlingguy
Copy link
Contributor

Saw the same issue here: geerlingguy/awx-container#28

@FloThinksPi
Copy link
Author

I got behind my error here. I included the awx repo as submodule in my deployment wrapper. However the awx folder gets included in the sdist builder image. But when using a submodule, the .git folder is in the main repo, not in the submodule folder. this resultet in the sdist container saying, /awx was not a git repo and failing to determen the awx version via git commits. so i cahanged my setup so a script clones the repo manually instead of including it as submodule

chrismeyersfsu pushed a commit to chrismeyersfsu/awx that referenced this issue Apr 26, 2018
…dentials

Fixed workflow node credential bug
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants