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

Make Bug reports work without the need of working DNS client. #1374

Closed
vlabo opened this issue Nov 29, 2023 · 3 comments
Closed

Make Bug reports work without the need of working DNS client. #1374

vlabo opened this issue Nov 29, 2023 · 3 comments
Labels
stale ATTRIBUTE: this issue has not had recent activity suggestion TYPE: idea for new feature or improvements

Comments

@vlabo
Copy link
Member

vlabo commented Nov 29, 2023

What would you like to add or change?:
It would be nice if users can report issues even if the DNS configuration is broken.

Why do you and others need this?:
I don't know if this is practical but hard-coding the ticket server IP can remove the need of a working DNS to report bugs or comparability issues.

@vlabo vlabo added the suggestion TYPE: idea for new feature or improvements label Nov 29, 2023
@safing safing deleted a comment from github-actions bot Nov 29, 2023
@dhaavi
Copy link
Member

dhaavi commented Dec 3, 2023

I think this is a great idea. But I'll have to think about how to do this in a good way.

Currently our infrastructure will automatically change DNS when the ingest proxy is rescheduled on another node. This means we currently have I think three possible IPs which might change without notice.
So maybe we should just try all three?

Also, if we start doing this stuff, this might be interesting for other things as well, like checking for updates. So this should be done in the core, not the UI. Which in turn means that the report should go via the core, not made by the UI directly.

So, there is quite some stuff to unpack here. I will think about what a good first step into this direction would be.

Copy link

github-actions bot commented Feb 5, 2024

This issue has been automatically marked as inactive because it has not had activity in the past two months.

If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.

@github-actions github-actions bot added the stale ATTRIBUTE: this issue has not had recent activity label Feb 5, 2024
Copy link

This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.

If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale ATTRIBUTE: this issue has not had recent activity suggestion TYPE: idea for new feature or improvements
Projects
None yet
Development

No branches or pull requests

2 participants