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

Cannot remove repair #119654

Open
jdeath opened this issue Jun 14, 2024 · 3 comments
Open

Cannot remove repair #119654

jdeath opened this issue Jun 14, 2024 · 3 comments

Comments

@jdeath
Copy link
Contributor

jdeath commented Jun 14, 2024

The problem

I get a constant repair issue.

I added options in the config.json of my addon and it has caused a persistent repair to show in settings.

The default configuration for add-ons and Home Assistant has changed. To update the configuration with the new defaults, a restart is required for the following:

Restarting the addon does nothing and the repair stays. If I uninstall the addon, I can submit the repair and it goes away. Reinstalling the addon, even with an incremented version, and the repair comes back. The addon works fine, just the repair will not go away.

I deleted the .storage/repairs.issue_registry but repair comes back

I did not find anything in a log to indicate the actual issue.

What version of Home Assistant Core has the issue?

core-2024.6.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

No response

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@issue-triage-workflows
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@Leah96xxx
Copy link

Issue persists. Still no way to remove or force ignore repairs

@home-assistant
Copy link

home-assistant bot commented Nov 2, 2024

Hey there @home-assistant/supervisor, mind taking a look at this issue as it has been labeled with an integration (hassio) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of hassio can trigger bot actions by commenting:

  • @home-assistant close Closes the issue.
  • @home-assistant rename Awesome new title Renames the issue.
  • @home-assistant reopen Reopen the issue.
  • @home-assistant unassign hassio Removes the current integration label and assignees on the issue, add the integration domain after the command.
  • @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
  • @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


hassio documentation
hassio source
(message by IssueLinks)

@github-actions github-actions bot removed the stale label Nov 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants
@joostlek @jdeath @Leah96xxx and others