-
Notifications
You must be signed in to change notification settings - Fork 13
Issues with clank install #63
Comments
Adding to that, Jon and I tried to switch from Ubuntu 16.04 to 14.04 LTS and we passed those above errors. During the installation, we add a global variable in However after that, we failed at the stage **: TASK [app-generate-ini-config : run generate script for app] ********************* The specific errors we are getting are And some other errors like Apologize for throwing so many installation errors at one time. It would be much appreciated if any of you can point us the direction of fix them. Thanks for your help! |
@xuhang57 no apologies necessary - thank you for providing details for us. |
|
To Lucas' feedback:
commit f14a9a7 resolves this as much as it communicates the need for the variables in the distribution file. |
To Jonathan's (@lokl8) feeback: As you noted, we are using 14.04.3 so we haven't hit this issue with uWSGI yet. Thank you for sharing this, as it'll be of great assistance as we shift to 16.04. For context/reference:
I will open an issue in the Atmosphere Repository on GitHub so we can investigate updating to 2.0.13 as a resolution. @lokI8 - within the That way I can target a potential fix to that branch.
Okay - this is great feedback. Our intent is to provide
Did you get this Some background, the |
Hi Andrew (@lenards), thanks for the quick response! Greatly appreciated. Our ATMOSPHERE_BRANCH is just set to "" in our variables.yml, I believe this means we're just working off master. After looking through the variables.yml file again, it appears we missed the "DB_VERSION: 9.3" variable. I'd imagine this is why changing the defaults.yml and Ubuntu.yml in setup-postgres/vars didn't impact anything. Oops! We are using Ansible version 2.1.0.0. Yes, that apt-get error for ruby was found in 16.04. There is no package for 16.04 ubuntu that is just flat "Ruby$version". Instead, it appears apt-get installs a set of packages that it reg-ex matches to "Ruby1.9.1". We didn't experience this error once we switched over to 14.04. Our latest error, once adding the variables you provided, is: "Testing for preconditions...", "", "Local variables.ini missing section: celeryd.default", "", "", "Configuration files were not generated.", "", "FAILED. "]. This is bizarre, because we clearly have the celeryd.default section in our variables.yml file, under the ATMO header... we just added the few variables to the end of that section, as you specified. |
@lokI8 - you are correct, |
@lokI8 - that error is unexpected regarding |
For the error - you'll want to look at Also, I gave you a slight misleading outline for those variables. But having more than one |
For Clank - we have only verified and tested it with Ansible 2.0. I have experienced problems with Ansible 2.1 and passing along variables to parameterized roles (see Ansible Issues 16320). So that may (unconfirmed) lead to the issue with |
Hello @lokI8! Thank you for being patient as we flesh out these issues. Like @lenards said above, we have yet to test this on 16.04. In regards to the the |
The file is indeed named variables.ini.ini. Should I just mv the file, or should I fix a typo somewhere else? Also, there is no ATMO header before all of the sections, but there is a "cleryd.default" section. Should I change this to "celeryd.default" as well? Is this file generated, or static? |
@lokI8 I added a quick fix to the |
@lokI8 The
|
I just want to assess where this is: @lokI8 @xuhang57 I believe the remaining issue is to address:
Which I am guessing that 16.04 doesn't have a 1.9 dependency because Ruby 2.0+ is what projects likely should be using. Perhaps our defined Redis PPA is contributing to that. We will investigate. Was the following issue with
|
@lokI8 Regarding:
The What I would encourage you to do is verify the spelling of |
We did indeed have the same misspelling in our variables.yml as well. We've fixed that and have continued on. The most recent error is during the app-django-manage-collectstatic role. We are getting a syntax error on line 192 of Thanks for all the help =) |
@lokI8 - I was hoping not to give you the "you could clone Atmosphere & set the |
Okay Jonathan - again, sorry about this. We have logstash configured in our environments, so the template doesn't handle this gracefully. If you just give # LOGSTASH
LOGSTASH_HOST = 'redact.make-redaction-cool-again.org'
LOGSTASH_PORT = 0
try:
import logstash
import threepio
has_logstash = True
except ImportError:
has_logstash = False |
@lenards Thanks for your help. Adding the 0 to the We now stuck on filling up the parameters in Thanks so much! |
Hi @xuhang57, Empty variables for So - valid, empty/default values like this: IRODS_HOST: ''
IRODS_PORT: 0
IRODS_ZONE: ''
IRODS_ADMIN_USER: ''
IRODS_ADMIN_PASS: '' Note: I believe that the We have provided some context to the variables in Thank you for your persistence & patience. |
Thank you Lance. I will close this. We appreciate all the feedback and patience. |
Relates to feedback from [Clank Issue 63](cyverse/clank#63) where the uWSGI 2.0.9 on Ubuntu 16.04 encounters a compile on pip install. This will require verification in the dev environment. A merge into dev can be verified using the QA regression tests, both API & QA.
Hello all,
I'm installing atmosphere using clank in a 16.04 Ubuntu vm, and we've hit a few issues that we thought you guys might want to know about.
The atmosphere repo cloned to /opt/dev/atmosphere has uWSGI version 2.0.9 in it's requirements.txt. We are hitting a compilation error on this package described here: unbit/uwsgi#1262. We've tried changing the version number to 2.0.13, but then clank won't let us pass the cloning of the atmosphere repo, as we've made modifications and it can't pull. We're trying on an older version of Ubuntu now.
Two more issues you guys might want to know about:
The text was updated successfully, but these errors were encountered: