Bug 1541392 - Insufficient permissions for /dev/null while running 4.2 analyzer on 4.1 sos
Summary: Insufficient permissions for /dev/null while running 4.2 analyzer on 4.1 sos
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-log-collector
Classification: oVirt
Component: analyzer
Version: 4.2.0
Hardware: All
OS: All
medium
high
Target Milestone: ovirt-4.2.2
: ---
Assignee: Douglas Schilling Landgraf
QA Contact: David Necpal
URL:
Whiteboard:
Depends On:
Blocks: bonding, Bug, interface, multiple 1532927
TreeView+ depends on / blocked
 
Reported: 2018-02-02 13:23 UTC by David Necpal
Modified: 2018-03-29 11:06 UTC (History)
3 users (show)

Fixed In Version: ovirt-log-collector-4.2.4-2.el7ev
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-29 11:06:59 UTC
oVirt Team: Integration
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: exception+
sbonazzo: devel_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 88009 0 None None None 2018-02-21 02:29:37 UTC

Description David Necpal 2018-02-02 13:23:31 UTC
Description of problem:
Tar error - Operation not permitted after run 4.2 analyzer with 4.1 sosreport - cannot mknod. 

Version-Release number of selected component (if applicable):
ovirt-log-collector-analyzer-4.2.0-1.el7ev.noarch
ovirt-log-collector-4.1.7-1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Take 4.1 sosreport (ovirt-log-collector on 4.1 engine)
2. copy it to 4.2 engine
3. chown postgres:postgres <sosreport>
4. su - postgres
5. cd /tmp
6. ovirt-log-collector-analyzer <sosreport>

Actual results:
-bash-4.2$ ovirt-log-collector-analyzer sosreport-LogCollector-20180202144325.tar.xz
Preparing environment:
======================
Temporary working directory is /tmp/tmp.XpuQswDZzD
Unpacking postgres data. This can take up to several minutes.
tar: sosreport-LogCollector-20180202144325/sosreport-example.com-20180202144155/dev/null: Cannot mknod: Operation not permitted
tar: Exiting with failure status due to previous errors

Expected results:
4.2 analyzer generates report from 4.1 sosreport

Additional info:

Comment 1 Douglas Schilling Landgraf 2018-02-15 21:04:40 UTC
Hi David,

Could you please:

- Share sosreport-LogCollector-20180202144325.tar.xz ?
- Test against ovirt-log-collector-4.2.3-1.el7ev ?
  Looks like you are using an old version (ovirt-log-collector-analyzer-4.2.0-1.el7ev.noarch)

Comment 3 David Necpal 2018-02-20 11:42:35 UTC
Hello Douglas, 

I don't have this report, because engine was updated. 

I tried test now with:
ovirt-log-collector-analyzer-4.2.3-1.el7ev.noarch

and sosreport from:
ovirt-log-collector-4.1.7-1.el7ev.noarch

the result is:
Missing almost all of information. This report contains only 
    1. Sosreport
    2. Pre-upgrade checks


I will share sosreport and analyzer report.

Comment 6 David Necpal 2018-02-23 18:31:41 UTC
Verified on version:
ovirt-log-collector-4.1.8-1.el7ev.noarch
ovirt-log-collector-analyzer-4.2.4-2.el7ev.noarch

Comment 7 Sandro Bonazzola 2018-03-29 11:06:59 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.