OSDOCS-5259: MicroShift sos reports #57828
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@opayne1: This pull request references OSDOCS-5259 which is a valid jira issue. In response to this:
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/test-infra repository. |
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
@opayne1: This pull request references OSDOCS-5259 which is a valid jira issue. In response to this:
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/test-infra repository. |
2 similar comments
|
@opayne1: This pull request references OSDOCS-5259 which is a valid jira issue. In response to this:
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/test-infra repository. |
|
@opayne1: This pull request references OSDOCS-5259 which is a valid jira issue. In response to this:
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/test-infra repository. |
openshift-ci
bot
added
the
size/M
openshift-ci
bot
added
size/L
|
🤖 Updated build preview is available at: Build log: https://circleci.com/gh/ocpdocs-previewbot/openshift-docs/14118 |
|
@opayne1: This pull request references OSDOCS-5259 which is a valid jira issue. In response to this:
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/test-infra repository. |
opayne1
changed the title
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
| + | ||
| [source,terminal] | ||
| ---- | ||
| $ sudo report --upload |
There was a problem hiding this comment.
| $ sudo report --upload | |
| $ sudo sos report --upload |
We should verify that this is how support wants this done.
There was a problem hiding this comment.
I tried to test the above but it looks like above command collects the sos report again and uploads it. It does not upload existing report. May be we should add a command here which actually uploads the existing sos report instead of generating a new one ?
Above command generates sos report for whole system and just not for microshift.
There was a problem hiding this comment.
@vwalek can you help with this procedure? Do we usually tell users to generate a report and then upload it, or is uploading it when the report is generated normal?
There was a problem hiding this comment.
@dhellmann yes, we will first collect the sosreport and use the redhat attachment tool to upload that. I haven't seen the option to --upload, but I will check it on my lab.
There was a problem hiding this comment.
Hi. looking at the definition of the upload, the upload should be used if you have specific server you want to push it.
--upload Upload archive to a policy-default location
--upload-url UPLOAD_URL
Upload the archive to specified server
--upload-directory UPLOAD_DIRECTORY
Specify upload directory for archive
--upload-user UPLOAD_USER
Username to authenticate to server with
--upload-pass UPLOAD_PASS
Password to authenticate to server with
--upload-method {auto,put,post}
HTTP method to use for uploading
--upload-no-ssl-verify
Disable SSL verification for upload url
--upload-protocol {auto,https,ftp,sftp}
Manually specify the upload protocol
I am not sure if we want to document that you can push it directly to some location.
I would leave it optional, like you can push it to your own server using SFTP, SCP or HTTP protocols.
Usually, the sosreport is collected to the bastion host and use of the redhat attachment tool or run the tool directly from the RHEL system.
I don't think the --upload should be part of the sos collection docs.
When running the sos report the system will ask you the ticket number to upload it directly, but that's optional.
There was a problem hiding this comment.
Thank you! We will leave those out.
|
lgtm, thank you! |
|
/lgtm |
|
@opayne1: This pull request references OSDOCS-5259 which is a valid jira issue. In response to this:
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/test-infra repository. |
opayne1
added
the
peer-review-needed
| + | ||
| [source,terminal] | ||
| ---- | ||
| $ sos report --upload --batch --clean --all-logs --profile microshift |
There was a problem hiding this comment.
| $ sos report --upload --batch --clean --all-logs --profile microshift | |
| $ sos report --batch --clean --all-logs --profile microshift |
Based on @vwalek 's comments, I think we want to remove the upload option that I had suggested adding previously.
|
/lgtm |
|
/remove-label peer-review-needed |
openshift-ci
bot
added
peer-review-in-progress
|
/label peer-review-done |
openshift-ci
bot
added
peer-review-done
|
/cherrypick enterprise-4.13 |
|
@opayne1: new pull request created: #58753 In response to this:
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/test-infra repository. |
9 participants
[WIP]OSDOCS-5259: MicroShift sos reports
Version(s):
4.13 only
Issue:
https://issues.redhat.com/browse/OSDOCS-5259
Link to docs preview:
https://57828--docspreview.netlify.app/microshift/latest/microshift_support/microshift-sos-report.html
QE review:
Additional information: