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

Fix flower deployment on k8s #191

Merged
merged 2 commits into from May 26, 2019

Conversation

Projects
None yet
1 participant
@c-w
Copy link
Member

commented May 26, 2019

The flower pod is currently crashing with the following error:

Traceback (most recent call last):
  File "/usr/local/bin/flower", line 10, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.6/site-packages/flower/__main__.py", line 11, in main
    flower.execute_from_commandline()
  File "/usr/local/lib/python3.6/site-packages/celery/bin/base.py", line 298, in execute_from_commandline
    return self.handle_argv(self.prog_name, argv[1:])
  File "/usr/local/lib/python3.6/site-packages/flower/command.py", line 56, in handle_argv
    return self.run_from_argv(prog_name, argv)
  File "/usr/local/lib/python3.6/site-packages/flower/command.py", line 33, in run_from_argv
    self.apply_env_options()
  File "/usr/local/lib/python3.6/site-packages/flower/command.py", line 71, in apply_env_options
    value = option.type(value)
ValueError: invalid literal for int() with base 10: 'tcp://10.0.75.166:8080'

This is because k8s auto-injects a variable of the form {deployment_name}_PORT which mistakenly gets read by flower: FLOWER_PORT=tcp://10.0.75.166:8080. Namespacing all the k8s objects with the release name should fix this issue.

@c-w c-w merged commit efeed75 into master May 26, 2019

3 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
pyup.io/safety-ci No dependencies with known security vulnerabilities.
Details

@c-w c-w deleted the fix-flower branch May 26, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.