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.

Sign up for GitHub

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

Jump to bottom

Netbox Upgrade Script Fails When Python3 is not installed as /usr/bin/python3 #6496

Closed
ArcticSnowman opened this issue May 27, 2021 · 2 comments
Closed

Netbox Upgrade Script Fails When Python3 is not installed as /usr/bin/python3 #6496

ArcticSnowman opened this issue May 27, 2021 · 2 comments
Assignees
@jeremystretch
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@ArcticSnowman
Copy link

NetBox version

v2.7.0 to v2.11.12

Python version

3.6

Steps to Reproduce

install python3 somewhere other than /usr/bin/python3
Add to path
run ./upgrade

Expected Behavior

./upgrade should run using the python3 found in the PATH

Observed Behavior

]# ./upgrade.sh
Creating a new virtual environment at /var/lib/netbox-2.7.12/venv...
./upgrade.sh: line 20: /usr/bin/python3: No such file or directory
--------------------------------------------------------------------
ERROR: Failed to create the virtual environment. Check that you have
the required system packages installed and the following path is
writable: /var/lib/netbox-2.7.12/venv
--------------------------------------------------------------------
@ArcticSnowman ArcticSnowman added the type: bug A confirmed report of unexpected behavior in the application label May 27, 2021
@jeremystretch jeremystretch added the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label May 27, 2021
@jeremystretch
Copy link
Member

IIRC, we specify the full path to ensure that the system Python executable is used, rather the one from a virtual environment that might happen to be active. I'm not sure this really matters, though.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels May 28, 2021
@jeremystretch jeremystretch self-assigned this May 28, 2021
@jeremystretch jeremystretch mentioned this issue Jun 4, 2021
Merged
@thoms27
Copy link

thoms27 commented Jun 7, 2021

Same issue with V2.11.6

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jeremystretch @ArcticSnowman @thoms27