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.

Sign up for GitHub

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

Jump to bottom

Extend troubleshooting guide with self-signed certificate use case #20518

Closed
Tracked by #20553
skabashnyuk opened this issue Sep 23, 2021 · 2 comments
Closed
Tracked by #20553

Extend troubleshooting guide with self-signed certificate use case #20518

skabashnyuk opened this issue Sep 23, 2021 · 2 comments
Labels
area/doc Issues related to documentation kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.

Comments

@skabashnyuk
Copy link
Contributor

Is your task related to a problem? Please describe

Several times reported that Bitbucket integration failed. The common reason was that self-signed certificates were imported incorrectly see more #20335 .

Describe the solution you'd like

We need to extend the troubleshooting guide describing this use-case.

Describe alternatives you've considered

No response

Additional context

No response
@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. area/doc Issues related to documentation labels Sep 23, 2021
@benoitf benoitf added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 23, 2021
@dmytro-ndp dmytro-ndp added severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 23, 2021
@themr0c
Copy link
Contributor

themr0c commented Sep 28, 2021

Referenced in https://issues.redhat.com/browse/RHDEVDOCS-3334

@skabashnyuk skabashnyuk mentioned this issue Sep 29, 2021
Closed
15 tasks
@che-bot
Copy link
Contributor

che-bot commented Mar 27, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

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

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 27, 2022
@che-bot che-bot closed this as completed Apr 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/doc Issues related to documentation kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@themr0c @benoitf @dmytro-ndp @skabashnyuk @che-bot