Bug 1642480 - rhnKickstartableTree schema upgrade fails on Oracle
Summary: rhnKickstartableTree schema upgrade fails on Oracle
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 2.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space210
TreeView+ depends on / blocked
 
Reported: 2018-10-24 13:43 UTC by Ales Dujicek
Modified: 2020-03-19 12:16 UTC (History)
1 user (show)

Fixed In Version: spacewalk-schema-2.10.2-1
Clone Of:
Environment:
Last Closed: 2020-03-19 12:16:49 UTC
Embargoed:


Attachments (Terms of Use)

Description Ales Dujicek 2018-10-24 13:43:59 UTC
Description of problem:

# spacewalk-schema-upgrade -y
...
Schema upgrade: [spacewalk-schema-2.8.25-1.fc28] -> [spacewalk-schema-2.9.7-1.el7]
Searching for upgrade path: [spacewalk-schema-2.8.25-1] -> [spacewalk-schema-2.9.7-1]
Searching for upgrade path: [spacewalk-schema-2.8.25] -> [spacewalk-schema-2.9.7]
Searching for upgrade path: [spacewalk-schema-2.8] -> [spacewalk-schema-2.9]
The path: [spacewalk-schema-2.8] -> [spacewalk-schema-2.9]
Executing spacewalk-sql, the log is in [/var/log/spacewalk/schema-upgrade/20181023-233424-to-spacewalk-schema-2.9.log].
Upgrade failed, please see log [/var/log/spacewalk/schema-upgrade/20181023-233424-to-spacewalk-schema-2.9.log].



spacewalk-schema-2.8-to-spacewalk-schema-2.9/002-rhnKickstartableTree-kernelOptions.sql.oracle

    ADD COLUMN kernel_options	    VARCHAR2(256),
        *
ERROR at line 2:
ORA-00904: : invalid identifier


Version-Release number of selected component (if applicable):
spacewalk-schema-2.9.7-1.el7.noarch

Comment 1 Michael Mráka 2020-03-09 13:22:21 UTC
Fixed in spacewalk git by
commit b4dec482edc9795a301e3c6e2dbac528e6a12d2a
    fixed failed upgrade on oracle

Comment 2 Michael Mráka 2020-03-19 12:16:49 UTC
Spacewalk 2.10 has been released.
https://github.com/spacewalkproject/spacewalk/wiki/ReleaseNotes210


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