Bug 1518950
Summary: | ovirt-log-collector-analyzer: sosreport-foobar-Logcollector-9175126/dev/null: Cannot mknod: Operation not permitted\ntar: Exiting with failure status due to previous errors | ||
---|---|---|---|
Product: | [oVirt] ovirt-log-collector | Reporter: | Douglas Schilling Landgraf <dougsland> |
Component: | General | Assignee: | Douglas Schilling Landgraf <dougsland> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Necpal <dnecpal> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4.2.0 | CC: | bugs, dougsland, fgarciad, gwatson, lsvaty, lveyde, ylavi |
Target Milestone: | ovirt-4.2.2 | Flags: | rule-engine:
ovirt-4.2?
rule-engine: ovirt-4.3? rule-engine: planning_ack? rule-engine: devel_ack+ lsvaty: testing_ack+ |
Target Release: | 4.2.3 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | ovirt-log-collector-4.2.3 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-03-29 10:53:29 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1456888 |
Description
Douglas Schilling Landgraf
2017-11-29 21:09:21 UTC
Hello Douglas, can you provide verification steps, please? (In reply to David Necpal from comment #2) > Hello Douglas, > > can you provide verification steps, please? Please try to use ovirt-log-collector-analyzer against the sosreport provided by comment#1. The tool should not fail with error: "dev/null: Cannot mknod: Operation not permitted\ntar: Exiting with failure status due to " Verified based on suggested steps from comment#3 against the sosreport provided by comment#1 on version ovirt-log-collector-analyzer-4.2.4-1.el7ev.noarch This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |