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.

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

TP rpmspec does not specify nodejs version #5438

Closed
shamrickus opened this issue Jan 14, 2021 · 0 comments · Fixed by #5446
Closed

TP rpmspec does not specify nodejs version #5438

shamrickus opened this issue Jan 14, 2021 · 0 comments · Fixed by #5446
Assignees
Labels
bug something isn't working as intended medium impact impacts a significant portion of a CDN, or has the potential to do so Traffic Portal v1 related to Traffic Portal version 1

Comments

@shamrickus
Copy link
Member

shamrickus commented Jan 14, 2021

I'm submitting a ...

  • bug report

Traffic Control components affected ...

  • Traffic Portal

Current behavior:

Any version of nodejs is accepted as a dependency to TP

Expected behavior:

The nodejs version should either be pinned or restricted to prevent major updates to nodejs which might break TP. Currently the documentation says nodejs 12 or above is required.

@shamrickus shamrickus added the bug something isn't working as intended label Jan 14, 2021
@shamrickus shamrickus changed the title TP rpmspec does not pin nodejs version TP rpmspec does not specify nodejs version Jan 14, 2021
@mitchell852 mitchell852 added the Traffic Portal v1 related to Traffic Portal version 1 label Jan 14, 2021
@mitchell852 mitchell852 added the medium impact impacts a significant portion of a CDN, or has the potential to do so label Jan 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something isn't working as intended medium impact impacts a significant portion of a CDN, or has the potential to do so Traffic Portal v1 related to Traffic Portal version 1
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants