Bug 2107667
Summary: | When generating sosreport with verbose logging enabled, cannot complete any other operations in Cockpit | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Brian Smith <briasmit> |
Component: | cockpit | Assignee: | Marius Vollmer <mvollmer> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 36 | CC: | dperpeet, mmarusak, mpitt, patrick, pvolpe, stefw, user-cont-team+packit-fas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | cockpit-273-1.fc35 cockpit-273-1.fc36 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-07-29 01:24:33 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Brian Smith
2022-07-15 15:41:22 UTC
I can reproduce this. I enabled `window.debugging = 'all'` during this, and I see gajillions of messages coming through the bridge, which just DoS it. These messages are supposed to land in the sosreport tarball/log file only, but not all sent to the channel. We don't show them in the UI anyway. Thanks for reporting! Yes, I totally missed this misbehavior during development, sorry. We pass "-vvv" to sos when the "Verbose" checkbox is on, which causes it to write all DEBUG level messages to the console. This is pointless with Cockpit. With just "-v", sos will only write WARNING level messages, but will still include DEBUG level messages in the archive itself. So let's just use "-v" with Cockpit. FEDORA-2022-5421bec777 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5421bec777 FEDORA-2022-b60c113cdd has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b60c113cdd FEDORA-2022-b60c113cdd has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-b60c113cdd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b60c113cdd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-5421bec777 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-5421bec777` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5421bec777 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-b60c113cdd has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-5421bec777 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |