-
-
Notifications
You must be signed in to change notification settings - Fork 162
Description
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
- Puppet: 7.18
- Ruby: 2.5.1
- Distribution: Ubuntu 18.04
- Module version: this=9.0.0 / puppet-python=6.3.0
How to reproduce (e.g Puppet code you use)
Code with vcsrepo installation method (using module version 8.2.0):
class { 'puppetboard':
default_environment => '*',
manage_git => true,
manage_virtualenv => true,
revision => 'v3.6.1',
}
class { 'puppetboard::apache::vhost':
vhost_name => $facts['fqdn'],
port => 80,
}
After switching to pip installaton method our code looks like (using module version 9.0.0):
class { 'puppetboard':
default_environment => '*',
manage_virtualenv => true,
python_version => '3.7',
}
class { 'puppetboard::apache::vhost':
vhost_name => $facts['fqdn'],
port => 80,
}
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 :
Notice: /Stage[main]/Puppetboard/Python::Pyvenv[/srv/puppetboard/virtenv-puppetboard]/File[/srv/puppetboard/virtenv-puppetboard]/ensure: created (corrective)
Notice: /Stage[main]/Puppetboard/Python::Pyvenv[/srv/puppetboard/virtenv-puppetboard]/Exec[python_virtualenv_/srv/puppetboard/virtenv-puppetboard]/returns: executed successfully (corrective)
Notice: /Stage[main]/Puppetboard/Python::Pip[puppetboard]/Exec[pip_install_puppetboard]/returns: executed successfully (corrective)
Notice: Applied catalog in 26.99 seconds
root@puppet-dev:/srv/puppetboard/virtenv-puppetboard/lib# ls
python3.7
root@puppet-dev:/srv/puppetboard/virtenv-puppetboard/lib/python3.7/site-packages/puppetboard# cat version.py
#
# Puppetboard version module
#
__version__ = '4.2.0'
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.