Bug 710086 - No such file or directory /var/log/spacewalk/schema-upgrade
No such file or directory /var/log/spacewalk/schema-upgrade
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Upgrades (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Milan Zazrivec
Šimon Lukašík
Depends On:
Blocks: sat541-triage
  Show dependency treegraph
Reported: 2011-06-02 08:37 EDT by Šimon Lukašík
Modified: 2012-03-08 04:06 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-02 08:58:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Šimon Lukašík 2011-06-02 08:37:09 EDT
Description of problem:
The upgrade procedure from RHN Satellite 5.2.1 to RHN Satellite 5.4.1
on RHEL5 ends up with 

  No such file or directory


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

How reproducible:

Steps to Reproduce:
1. Follow instruction from rhn-upgrade
2. /usr/bin/spacewalk-schema-upgrade
Actual results:
Schema upgrade: [rhn-satellite-schema-5.2.0-8] -> [satellite-schema-]
Searching for upgrade path: [rhn-satellite-schema-5.2.0-8] -> [satellite-schema-]
Searching for upgrade path: [rhn-satellite-schema-5.2.0] -> [satellite-schema-]
Searching for upgrade path: [rhn-satellite-schema-5.2] -> [satellite-schema-5.4.0]
Searching for upgrade path: [rhn-satellite-schema-5.2] -> [satellite-schema-5.4]
The path: [rhn-satellite-schema-5.2] -> [satellite-schema-5.3] -> [satellite-schema-5.4]
Failed to create log directory [/var/log/spacewalk/schema-upgrade]: No such file or directory

Expected results:

The directory should be either created implicitly or user should be advised  create it.

Additional info:
Comment 2 Šimon Lukašík 2011-06-02 08:58:24 EDT
This is NOTABUG. I have run the script as oracle user. Which is my failure.

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