Bug 1500311

Summary:	`open': Not a directory - /var/lib/qpidd/.qpidd/qls/jrnl/<something> (Errno::ENOTDIR)
Product:	Red Hat Satellite	Reporter:	Evgeni Golov <egolov>
Component:	Installation	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Ales Dujicek <adujicek>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2.12	CC:	adujicek, bbuckingham, mmccune, rbeyel
Target Milestone:	6.4.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-16 19:07:55 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 Evgeni Golov 2017-10-10 11:34:05 UTC

Description of problem:
When there are files (not directories) in /var/lib/qpidd/.qpidd/qls/jrnl/, the upgrade fails when migrating the qpidd dirs, as it tries to chdir to a non-directory (file, symlink, whatever).

I understand that having non-directories is not really expected in the jrnl folder, but I still think the upgrade should cope with that.

Version-Release number of selected component (if applicable):
Satellite 6.2.12

How reproducible:
100%

Steps to Reproduce:
1. touch /var/lib/qpidd/.qpidd/qls/jrnl/test.txt
2. upgrade from 6.2.10 to 6.2.12

Actual results:
/usr/share/katello-installer-base/hooks/pre/30-upgrade.rb:124:in `open': Not a directory - /var/lib/qpidd/.qpidd/qls/jrnl/test.txt (Errno::ENOTDIR)

Expected results:
Upgrade succeeds

Additional info:
Workaround: remove all non-directories from the jrnl folder

Comment 1 Evgeni Golov 2017-10-10 11:36:18 UTC

Created redmine issue http://projects.theforeman.org/issues/21268 from this bug

Comment 3 Satellite Program 2017-10-10 18:04:20 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21268 has been resolved.

Comment 5 Mike McCune 2017-10-11 12:50:12 UTC

FYI, This is different from https://bugzilla.redhat.com/show_bug.cgi?id=1482539

Comment 9 Bryan Kearney 2018-10-16 19:07:55 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2927