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

Documentation: No way to remove proxy #10658

Open
Firstyear opened this issue Aug 26, 2016 · 7 comments
Open

Documentation: No way to remove proxy #10658

Firstyear opened this issue Aug 26, 2016 · 7 comments
Assignees
Labels
component/install kind/question lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P2

Comments

@Firstyear
Copy link

Firstyear commented Aug 26, 2016

Once set, there is no documented method to remove the proxy defined in the install. This is an issue, is the proxy breaks some use cases, and I need to remove it.

Current Result

Have to re-install my entire set of openshift servers.

Expected Result

I can find the documentation telling me how to remove the proxy value.

@Firstyear Firstyear changed the title Documentation Documentation: No way to remove proxy Aug 26, 2016
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 6, 2018
@Firstyear
Copy link
Author

/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 7, 2018
@greenled
Copy link

I am facing the same issue. Any workaround?

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 25, 2018
@Firstyear
Copy link
Author

/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 25, 2018
@Firstyear
Copy link
Author

/lifecycle frozen

@openshift-ci-robot openshift-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label May 25, 2018
@Firstyear
Copy link
Author

This is still an issue.

I want to raise a strong objection to the use of your "bot" to close out issues that you don't work on. I think it's offensive to the community and your users, and the issues we face.

I raise issues because they are of concern to myself in production and others who may face them. To disregard them so blatantly is not a positive thing.

Please stop automatically closing issues, and please investigate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/install kind/question lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/P2
Projects
None yet
Development

No branches or pull requests

7 participants