Description of problem: Error running spacewalk-setup --disconnected --upgrade Version-Release number of selected component (if applicable): Spacewalk v1.3 nightly How reproducible: always Steps to Reproduce: 1. sudo spacewalk-setup --disconnected --upgrade Actual results: [coec@sw-pg downloads]$ sudo spacewalk-setup --disconnected --upgrade ** Database: Setting up database connection for PostgreSQL backend. Hostname (leave empty for local)? localhost Port [5432]? Database? spaceschema Username? spaceuser Password? ** Database: Populating database. ** Database: Skipping database population. * Setting up users and groups. ** GPG: Initializing GPG and importing key. * Performing initial configuration. Error chowning dir [/var/satellite/redhat] to [apache]: Read-only file system * Activating Spacewalk. ** Certificate not activated. ** Upgrade process requires the certificate to be activated after the schema is upgraded. * Enabling Monitoring. DBD::Pg::db do failed: ERROR: column "sysdate" does not exist LINE 5: last_update_date = sysdate ^ at /usr/share/perl5/Spacewalk/Setup.pm line 1572. Issuing rollback() due to DESTROY without explicit disconnect() of DBD::Pg::db handle dbname=spaceschema;host=localhost;port=5432 at /usr/share/perl5/Spacewalk/Setup.pm line 1572. [coec@sw-pg downloads]$ Expected results: Should complete without errors Additional info:
author Colin Coe <colin.coe> Sun, 26 Dec 2010 05:47:29 +0000 (13:47 +0800) committer Colin Coe <colin.coe> Sun, 26 Dec 2010 05:47:29 +0000 (13:47 +0800) commit dfe456c5bdb4f46decb6004fb256f4d6aaf457ba tree b1c905ea9b5b12a6f90c75fa3a9acbce682fd72f tree parent 64e901bc48027e73e644d2fa4a0dbc06e6ab5c67 commit | diff I've tested this with both a PG and Oracle setup and both appear to work fine.
Marking as MODIFIED, tagged and built as spacewalk-setup-1.3.4-1. Colin, note however that the main problem is actually the schema upgrade on PostgreSQL. I still haven't finished this.
Moving ON_QA ...
This bug has been fixed in Spacewalk 1.3.