| *** noonedeadpunk_ is now known as noonedeadpunk | 08:14 | |
| ihalomi_ | hey, not sure if this is right channel but i have problem with my account at opendev. I changed prefered email in my ubuntu one account and now I cannot login into opendev account. It sents me to this page https://review.opendev.org/SignInFailure,SIGN_IN,Contact+site+administrator who should I contact about it? I think its because there is already account in opendev using my new prefered email but ubuntu one account used to creat | 11:32 |
|---|---|---|
| frickler | ihalomi_: #opendev is a better channel, responded there | 11:51 |
| noonedeadpunk | Hey folks | 16:42 |
| noonedeadpunk | I need some help I guess. I'm trying to fix CI for Vitrage, but looks like AODH installation in devstack is also broken. And I'm not _very_ good in debugging devstack issues. So maybe this is smth known :) | 16:43 |
| noonedeadpunk | So aodh wsgi fails with that: https://zuul.opendev.org/t/openstack/build/39c110a20e8e495e88f987901d3caeb0/log/controller/logs/apache/aodh_log.txt | 16:43 |
| noonedeadpunk | Which sounds like either path is wrong or dunno even... | 16:44 |
| clarkb | noonedeadpunk: thats an import error for aodh in the wsgi script /var/www/aodh/app. That means aodh isn't installed or it isn't installed in your python path | 16:45 |
| clarkb | noonedeadpunk: I would cross check how other services are installing themselves to be executable under wsgi | 16:46 |
| clarkb | this may be fallout from the install everything into a virtualenv effort and if aodh is a plugin maybe it didn't get updated to do the same or update paths etc | 16:46 |
| noonedeadpunk | I kinda wonder if that could be also that some kind of migration from providing wsgi script to using the module... | 16:49 |
| noonedeadpunk | just aodh jobs looks like working nicely and apache config is exactly the same: https://zuul.opendev.org/t/openstack/build/32fa462543e548d199b38ab82440948c/log/controller/logs/apache_config/aodh_conf.txt | 16:50 |
| clarkb | https://opendev.org/openstack/aodh/src/commit/c19cb61f46c1f0bda6c6494ad20e51141e23d052/devstack/plugin.sh#L67-L90 it is a plugin and it does appear to have some code to deal with virtualenv installs | 16:54 |
| clarkb | interesting | 16:54 |
| clarkb | /opt/stack/data/venv is where aodh is installed in the failing job | 16:55 |
| clarkb | noonedeadpunk: in the passing job you have https://zuul.opendev.org/t/openstack/build/32fa462543e548d199b38ab82440948c/log/controller/logs/_.localrc_auto.txt#46 in the failing job you do not | 16:57 |
| clarkb | and the venv code in the aodh plugin I linked is for per projcet venvs which is a dead code path I think. The venv codepath in devstack uses a global venv with everything installed in it | 16:58 |
| clarkb | the update you will want to make is if global venv is set then update the aodh config similar to how it updates the project venv into the config there | 16:58 |
| frickler | I wonder why aodh is running with mod_wsgi instead of uwsgi. do they do that in their own tests, too? | 16:59 |
| clarkb | frickler: per the aodh_conf.txt file noonedeadpunk linked it appears they use mod wsgi there too | 17:00 |
| noonedeadpunk | aha | 17:00 |
| clarkb | the plugin does have some uwsgi stuff in it though | 17:00 |
| noonedeadpunk | Ok, now it's way more clear. Except on how to fix, but will figure that part, thanks clarkb! | 17:02 |
| noonedeadpunk | And sorry for the stupid question, but I really barely touched devstack in last 3-4 years | 17:02 |
| clarkb | you just have to follow the breadcrumbs: cannot import aodh -> where is aodh installed -> aodh is installed in a venv -> is the venv in mod_wsgi's python path? | 17:03 |
| clarkb | I guess asking "is aodh installed" is the first question | 17:04 |
| noonedeadpunk | Yeah, just that other aodh services seem to be running normally, except API really confused me | 17:05 |
| frickler | ah, aodh sets GLOBAL_VENV="False" | 17:05 |
| clarkb | frickler: yup | 17:05 |
| clarkb | so they will stop working at some point in the future without updates | 17:05 |
| frickler | you'll need to do that in your job config, too. except that this is a bad idea ... exactly | 17:05 |
| noonedeadpunk | So I assume ideally aodh devstack plugin should be checked ideally... | 17:06 |
| clarkb | noonedeadpunk: I would update the aodh devstack plugin to handle global_venv the code is mostly there it just needs a different flag check for the global venv and then to write the virtualenv to the wsgi config | 17:07 |
| clarkb | the same change can remove the GLOBAL_VENV=false setting to self test | 17:07 |
| clarkb | https://opendev.org/openstack/aodh/src/commit/c19cb61f46c1f0bda6c6494ad20e51141e23d052/devstack/plugin.sh#L67-L90 this is what needs to be updated for mod wsgi | 17:07 |
| clarkb | not sure about uwsgi | 17:07 |
| noonedeadpunk | ok-ok, gotcha, will try to come up with smth, thanks again! | 17:09 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!