-
-
Notifications
You must be signed in to change notification settings - Fork 165
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
Unable to install version > 3.6.1 on Ubuntu 18.04 using python 3.7 after module update #374
Comments
Hi @svenboll, thanks for reporting the issue. Changing Sorry for the stupid question but did you (or Puppet) restart Apache/Puppetboard after removing the virtualenv and letting Puppet recreate it? |
Hi @gdubicki , |
You should find the root cause of this 500 in apache2 logs. Can you share it please? |
could this be a wsgi update/plugin error? bash history: error.log (from restart at 08:08:43 to 08:14): bash history: error.log: |
Thanks for that info! I suspect that the puppetboard package did not install for you in the new virtualenv that used Python 3.7, but the error was suppressed and not shown. You should check the pip.log at And while most probably it's the puppetboard package itself, you can also compare the whole list of packages with this good working list from one of my instances on a Centos 7 node using Python 3.8:
If any of the packages is missing, even if you don't see any errors in the log, you can try to install them manually while having the virtualenv activated and see what are the results of that. Please share all the findings! |
So i tested now python 3.7 and python 3.8 venv with the same result of installed packages, and after all i still ended up in "500 - Internal Server Error":
with both python3.7 and 3.8 virtenv there are some suspicious errors in the pip.log:
then i tried to install puppetboard manually, but with no change:
|
The |
Can you please check the WSGI config in your Apache vhost, @svenboll ? Maybe for some reason you don't have the virtualenv configured there. For example I have something like this in my
|
it looks the same for me on my apache vhost conf. i think it could be a similar issue to #369 in my apache2 module folder i can only find these entries related to mod_wsgi, no version for python 3.7 or 3.8 which are the versions i tested. could this be a problem?
|
You are totally right, it seems related to that... You should have mod_wsgi for Python 3.7 or 3.8, whatever you are using. I am not sure how can you get it on Ubuntu though. We are using Centos 7 and Python 3.8 and HTTPD 2.4 from SCL. The HTTP 2.4 is mainly to have a mod_wsgi working with that Python 3.8. We install it using this code:
I hope that it helps! |
We are using puppetboard for almost 2 years now and switched from vcsrepo to pip installation method a few weeks ago.
But after all i don't see a newer version installed than 3.6.1.
First i figured out that on Ubuntu 18.04 the python version installed is 3.6 by default and with puppetboard version 4 the support for python3.6 was removed.
So i decided to use parameter python_version => '3.7', but nothing happened. We are still on version 3.6.1 of puppetboard.
After all, the venv-python directory did not update to python3.7 as expected and is still on python3.6.
So i removed the entire directory /srv/puppetboard/virtenv-puppetboard
puppet sets up a new virtual env with python3.7 (now as expected), but the version of our visible puppetboard was still running on version 3.6.1 and not as seen in the logs with version 4.2.0
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
Code with vcsrepo installation method (using module version 8.2.0):
After switching to pip installaton method our code looks like (using module version 9.0.0):
What are you seeing
Puppetboard version 3.6.1 with old virtualenv directory including python3.6:
After creating a new virtualenv directory with python3.7 i see the following puppetboard. Still on version 3.6.1 but without the graph of failed, changed or unchanged puppet runs!
Output log
puppet run after removing directory /srv/puppetboard/virtenv-puppetboard :
Any additional information you'd like to impart
I don't look at other directories or files relating to apache, wsgi apache module or something else right now.
The text was updated successfully, but these errors were encountered: