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

The "Overwrite" alert button for a host results in "Page not found" error #195

Open
saulp opened this issue Nov 8, 2019 · 3 comments
Open

Comments

@saulp
Copy link

saulp commented Nov 8, 2019

Hi Paul,

I was trying to overwrite an alert for a single host, but got a "Page not found" error. I had seen this before, so I updated via docker to the (then) most recent version, 0.40, but the issue remains.

I noticed the resulting URL is to a non-existing service (e.g. http://my_server:8000/service/26 ) so maybe that is the issue... Note that attempting to add an overwrite to a project doesn't yield the error, it's only for a host.

I recorded a 40-sec video: https://www.loom.com/share/8976856bf2034428b24ab92df7030db4

(I'd like to take it down after you no longer need it, please let me know)

Thanks again,
Saul

@kfdm
Copy link
Collaborator

kfdm commented Nov 10, 2019

Thanks for the report. I'll take a look 🙇

@saulp
Copy link
Author

saulp commented Nov 28, 2019

Thanks Paul! Let me know if there is any other info I can provide? At the moment I have a workaround process where I add the exception via the Project page (which does not result in the error as you can see in the first half of the video)... but this is something I'd like to address before sharing this tool with the rest of my team.

Thanks again for your help :)

@kfdm
Copy link
Collaborator

kfdm commented Dec 13, 2019

Right now, Rules must belong to either the Site (Global), Service, or Project, so it's not so surprising (to me) that trying to overwrite an alert for a single host throws an error.

I've spent some time over the last several days trying to decide on a roadmap for what I want to work on the next term, which I've tried to collect in this milestone.

There's some API refactoring I want to take care of first, but then I want to re-factor the Host model in #222
This should make it easier fix the HostDetail page, which should also make it easier to fix the actual bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants