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

qBittorrent unable to deploy #3117

Closed
1 task done
lps-rocks opened this issue Jul 10, 2022 · 4 comments · Fixed by #3119
Closed
1 task done

qBittorrent unable to deploy #3117

lps-rocks opened this issue Jul 10, 2022 · 4 comments · Fixed by #3119
Labels
bug Something isn't working

Comments

@lps-rocks
Copy link

App Name

qbittorrent

SCALE Version

22.02.1

App Version

11.0.11

Application Events

[]core.ServicePort{core.ServicePort{Name:"torrenttcp", Protocol:"TCP", AppProtocol:(*string)(nil), Port:65301, TargetPort:intstr.IntOrString{Type:0, IntVal:65301, StrVal:""}, NodePort:31271}, core.ServicePort{Name:"torrentudp", Protocol:"UDP", AppProtocol:(*string)(nil), Port:65301, TargetPort:intstr.IntOrString{Type:0, IntVal:65301, StrVal:""}, NodePort:31271}}: may not contain more than 1 protocol when type is 'LoadBalancer'

Application Logs

N/A

Application Configuration

Change the stock torrent service ports (TCP and UDP) to anything (as long as they match). Everything else defaults.

Describe the bug

Fails to deploy citing two ports cannot share the same port. The port service type is left as 'Simple' however the error cites type 'Loadbalancer'

To Reproduce

Deploy 'qbittorrent' application version 11.0.11 - It fails to deploy when both the TCP and UDP torrent service ports are the same. Prior to version 11.0.11 it deploys just fine.

Expected Behavior

Deployment should occur

Screenshots

N/A

Additional Context

N/A

I've read and agree with the following

  • I've checked all open and closed issues and my issue is not there.
@lps-rocks lps-rocks added the bug Something isn't working label Jul 10, 2022
@Ornias1993
Copy link
Member

The issue here is that iX neglected to actually backport the enable toggle two times in a row. We missed that because they gave us the impression privately that the first missing backport was a mustake and would look into backporting on 22.02.2, which did not happen either.

Changes will be reverted by @stavros-k shortly :)

@Ornias1993
Copy link
Member

@all-contributors please add @lps-rocks for bug

@allcontributors
Copy link
Contributor

@Ornias1993

I've put up a pull request to add @lps-rocks! 🎉

@truecharts-admin
Copy link
Collaborator

This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists

@truecharts truecharts locked and limited conversation to collaborators Feb 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants