-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
OTBR 2.4.7 manifest issue #3472
Comments
I'm seeing something very similar trying to update from OTBR 2.4.6, also on HAOS on a Yellow and running 2024.2.2. |
Same issue as above same version of home assistant. Running on Green Hardware. |
I attempted with 2024.2.2 2024.2.1 both failed on the new 2.4.7. Restored my backup to 2.4.6 and it is now up. |
At the point in time when this issue got created the add-on was still building. The current add-on system updates the metadata at the same time as the build is happening, so this leads to this race condition. Also, since there are no later reports of that problem I assume this was the only problem. I am closing this issue as this is not really OTBR related but more a build system issue. |
Describe the issue you are experiencing
Can't install homeassistant/amd64-addon-otbr:2.4.7: 404 Client Error for http+docker:https://localhost/v1.43/images/create?tag=2.4.7&fromImage=homeassistant%2Famd64-addon-otbr&platform=linux%2Famd64: Not Found ("manifest for homeassistant/amd64-addon-otbr:2.4.7 not found: manifest unknown: manifest unknown")
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
OpenThread Border Router
What is the version of the add-on?
2.4.7
Steps to reproduce the issue
...
Shutdown system retry but still fails
System Health information
No repairs available
Anything in the Supervisor logs that might be useful for us?
Anything in the add-on logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: