SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Radarr: Unable to upgrade Radarr to new version, update script state no update path available. #573

New Issue
Closed
opened 2025-11-20 04:50:26 -05:00 by saavagebueno · 8 comments
saavagebueno commented 2025-11-20 04:50:26 -05:00
Owner
Copy Link

Originally created by @JNR8 on GitHub (Feb 21, 2025).

✅ Have you read and understood the above guidelines?

Yes

📜 What is the name of the script you are using?

Radarr Update Script

📂 What was the exact command used to execute the script?

update

📝 Provide a clear and concise description of the issue.

Radarr indicates a new version is available. When running the "update" script in the Containers shell a message stating "There is currently no update path available." appears.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

log into Container shell
type update
select yes
observer error.

❌ Paste the full error output (if available).

There is currently no update path available.

🖼️ Additional context (optional).

No response

Originally created by @JNR8 on GitHub (Feb 21, 2025). ### ✅ Have you read and understood the above guidelines? Yes ### 📜 What is the name of the script you are using? Radarr Update Script ### 📂 What was the exact command used to execute the script? update ### 📝 Provide a clear and concise description of the issue. Radarr indicates a new version is available. When running the "update" script in the Containers shell a message stating "There is currently no update path available." appears. ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. log into Container shell type update select yes observer error. ### ❌ Paste the full error output (if available). There is currently no update path available. ### 🖼️ Additional context (optional). _No response_
saavagebueno added the investigation label 2025-11-20 04:50:26 -05:00
saavagebueno commented 2025-11-20 04:50:27 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 21, 2025):

Thats not an bug, radarr doesnt have an update function

@MickLesk commented on GitHub (Feb 21, 2025): Thats not an bug, radarr doesnt have an update function
saavagebueno commented 2025-11-20 04:50:27 -05:00
Author
Owner
Copy Link

@JNR8 commented on GitHub (Feb 21, 2025):

Its not a "Radarr" update function. Its a script provided by the Community Scripts Radarr script to allow easy updates of the Radarr app when new versions are available. It used to work. I've used it before. Since the update scripts were updated at the end of 2024 it fails to update Radarr to the lateest version with the error I mentioned.

I would consider that a "bug" if after a change to the update script it stops functioning as intended.

@JNR8 commented on GitHub (Feb 21, 2025): Its not a "Radarr" update function. Its a script provided by the Community Scripts Radarr script to allow easy updates of the Radarr app when new versions are available. It used to work. I've used it before. Since the update scripts were updated at the end of 2024 it fails to update Radarr to the lateest version with the error I mentioned. I would consider that a "bug" if after a change to the update script it stops functioning as intended.
saavagebueno commented 2025-11-20 04:50:27 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 21, 2025):

Nope.

https://github.com/community-scripts/ProxmoxVE/commits/main/ct/radarr.sh
Check the history. never was an update function implemented for this script.

The Script is not marked as updatable on website. tteck hasnt ever an update implemented for this. This means that it is definitely not a bug and can never have worked before.

@MickLesk commented on GitHub (Feb 21, 2025): Nope. https://github.com/community-scripts/ProxmoxVE/commits/main/ct/radarr.sh Check the history. never was an update function implemented for this script. The Script is not marked as updatable on website. tteck hasnt ever an update implemented for this. This means that it is definitely not a bug and can never have worked before.
saavagebueno commented 2025-11-20 04:50:28 -05:00
Author
Owner
Copy Link

@oOStroudyOo commented on GitHub (Feb 21, 2025):

Radarr has a built-in updater and can be managed from within the Radarr UI

Manual update:
System > Updates > Install

Or if you want auto-updates:
Settings > General > Show Advanced > Updates > Check Automatic > Save Changes

@oOStroudyOo commented on GitHub (Feb 21, 2025): Radarr has a built-in updater and can be managed from within the Radarr UI Manual update: System > Updates > Install Or if you want auto-updates: Settings > General > Show Advanced > Updates > Check Automatic > Save Changes
saavagebueno commented 2025-11-20 04:50:28 -05:00
Author
Owner
Copy Link

@JNR8 commented on GitHub (Feb 21, 2025):

Nope.

https://github.com/community-scripts/ProxmoxVE/commits/main/ct/radarr.sh Check the history. never was an update function implemented for this script.

The Script is not marked as updatable on website. tteck hasnt ever an update implemented for this. This means that it is definitely not a bug and can never have worked before.

Ah, well. I stand corrected. I have never noticed the "not updatable" status on the script page before. But then I would have only looked that page once when I installed the script (ages ago) and then assumed it has the same update process as most other scripts

What added to my consusion is that the Sonarr script has an "Update" script that does update the app, even though it has the same internal update processes within the app that radarr has.

Perhaps an update to the Radarr script to either be the same as the Sonarr update script, or change the update scripts response to indicate the app should be updated using its internal update process. It would improve the end users expirience and avoid this kind of confusion in the future.

@JNR8 commented on GitHub (Feb 21, 2025): > Nope. > > https://github.com/community-scripts/ProxmoxVE/commits/main/ct/radarr.sh Check the history. never was an update function implemented for this script. > > The Script is not marked as updatable on website. tteck hasnt ever an update implemented for this. This means that it is definitely not a bug and can never have worked before. Ah, well. I stand corrected. I have never noticed the "not updatable" status on the script page before. But then I would have only looked that page once when I installed the script (ages ago) and then assumed it has the same update process as most other scripts What added to my consusion is that the Sonarr script has an "Update" script that does update the app, even though it has the same internal update processes within the app that radarr has. Perhaps an update to the Radarr script to either be the same as the Sonarr update script, or change the update scripts response to indicate the app should be updated using its internal update process. It would improve the end users expirience and avoid this kind of confusion in the future.
saavagebueno commented 2025-11-20 04:50:28 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 23, 2025):

new output comes later, we rework the script first

@MickLesk commented on GitHub (Feb 23, 2025): new output comes later, we rework the script first
saavagebueno commented 2025-11-20 04:50:28 -05:00
Author
Owner
Copy Link

@JNR8 commented on GitHub (Feb 23, 2025):

Now I'm confused again.

Your reply says you'll rework the script, but the ticket closure state says you won't.

@JNR8 commented on GitHub (Feb 23, 2025): Now I'm confused again. Your reply says you'll rework the script, but the ticket closure state says you won't.
saavagebueno commented 2025-11-20 04:50:29 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 23, 2025):

The issue hasnt something To-Do with an rework. The Script Work AS excepted. Reworks are our Background Tasks.

@MickLesk commented on GitHub (Feb 23, 2025): The issue hasnt something To-Do with an rework. The Script Work AS excepted. Reworks are our Background Tasks.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label investigation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#573
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?