Skip to content

Conversation

@jmagak
Copy link
Member

@jmagak jmagak commented Dec 8, 2025

@rhdh-bot
Copy link
Collaborator

rhdh-bot commented Dec 8, 2025

Copy link

@gabriel-farache gabriel-farache left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

review for proc-troubleshooting-missing-workflows.adoc

Copy link

@elai-shalev elai-shalev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmagak overall loos good, added some comments

@elai-shalev
Copy link

@jmagak
One additional thing I had in mind, we have this blog post on many different customer questions which are toubleshoot related.
Maybe some of the information from there could be integrated to the troubleshooting section of the docs.
@pkliczewski wdyt?

@pkliczewski
Copy link

Maybe some of the information from there could be integrated to the troubleshooting section of the docs. @pkliczewski wdyt?

Good pointer @elai-shalev . It would be great to add this blog post to this section

@jmagak
Copy link
Member Author

jmagak commented Dec 10, 2025

Maybe some of the information from there could be integrated to the troubleshooting section of the docs.

Great suggestion, @elai-shalev and @pkliczewski. How about I work on this separately by introducing a section like what we have here, in our docs?

@elai-shalev
Copy link

elai-shalev commented Dec 10, 2025

Maybe some of the information from there could be integrated to the troubleshooting section of the docs.

Great suggestion, @elai-shalev and @pkliczewski. How about I work on this separately by introducing a section like what we have here, in our docs?

This Q&A section like the example will work, looks good. I agree it could be in another PR

Copy link

@elai-shalev elai-shalev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

More comments

@jmagak jmagak force-pushed the RHIDP-9238-Troubleshooting-Guide branch from afd6933 to d2ada27 Compare December 11, 2025 12:29
Copy link

@elai-shalev elai-shalev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@sonarqubecloud
Copy link

@jmagak
Copy link
Member Author

jmagak commented Dec 11, 2025

/cherry-pick release-1.7

@openshift-cherrypick-robot
Copy link
Contributor

@jmagak: once the present PR merges, I will cherry-pick it on top of release-1.7 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.7

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@jmagak
Copy link
Member Author

jmagak commented Dec 11, 2025

/cherry-pick release-1.8

@openshift-cherrypick-robot
Copy link
Contributor

@jmagak: once the present PR merges, I will cherry-pick it on top of release-1.8 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.8

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@Gerry-Forde Gerry-Forde merged commit addebcb into redhat-developer:main Dec 11, 2025
5 checks passed
@openshift-cherrypick-robot
Copy link
Contributor

@jmagak: new pull request created: #1642

In response to this:

/cherry-pick release-1.7

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-cherrypick-robot
Copy link
Contributor

@jmagak: new pull request created: #1643

In response to this:

/cherry-pick release-1.8

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants