Bug 556460 - spacewalk-repo-syn does not work on Fedora12 - Exception "common.rhnException.rhnFault'
Summary: spacewalk-repo-syn does not work on Fedora12 - Exception "common.rhnException...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 0.7
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space08
TreeView+ depends on / blocked
 
Reported: 2010-01-18 14:14 UTC by a.oehler
Modified: 2010-02-16 12:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-16 12:56:26 UTC
Embargoed:


Attachments (Terms of Use)
This is patch for spacewalk 0.7 (1.58 KB, text/plain)
2010-01-23 10:58 UTC, Michael Mráka
no flags Details

Description a.oehler 2010-01-18 14:14:20 UTC
Description of problem:


original Post from Greg Kuchyt on Maillist
I have a clean Spacewalk setup installed on F12 (x86_64) using Oracle (Enterprise edition) 10.2.0.1.0 (64-bit) as the backend. I've created a channel and when I attempt to add packages via reposync or rhnpush I get the below error for every package attempted to be added. This is in a clean database, on a clean Spacewalk install. I've had Spacewalk working perfectly before, so I have to believe that I'm doing something wrong. Anyone have any ideas as to what is/could be going on here? Thanks in advance for any light anyone can be shed on this.

45/19122 : perl-Time-Duration-1.06-6.fc12-0.noarch
ERRORException reported from xxxxxxxx.potsdam.edu
Time: Mon Jan  4 15:45:20 2010
Exception type <class 'common.rhnException.rhnFault'>

Exception Handler Information
Traceback (most recent call last):

File "/usr/share/rhn/satellite_tools/reposync.py", line 145, in import_packages

    self.upload_package(pack, path)

File "/usr/share/rhn/satellite_tools/reposync.py", line 170, in upload_package

    org_id=self.channel['org_id'])

File "/usr/share/rhn/server/rhnPackageUpload.py", line 168, in push_package

    importer.run()
  File "/usr/share/rhn/server/importlib/importLib.py", line 628, in run
    self.submit()

File "/usr/share/rhn/server/importlib/packageImport.py", line 308, in submit

    transactional=self.transactional)

File "/usr/share/rhn/server/importlib/backend.py", line 742, in processPackages

    transactional=transactional)

File "/usr/share/rhn/server/importlib/backend.py", line 1601, in __processObjectCollection__

    return self.__doDML(dml)
  File "/usr/share/rhn/server/importlib/backend.py", line 1709, in __doDML
    self.__doInsert(dml.insert, dml.tables)

File "/usr/share/rhn/server/importlib/backend.py", line 1718, in __doInsert

    raise rhnFault(54, str(e[1]), explain=0)

rhnFault: (54, 'ORA-01861: literal does not match format string\n', '\n Package Upload Failed due to uniqueness constraint violation.\n Make sure the package does not have any duplicate dependencies or\n does not already exists on the server\n ') 

Version-Release number of selected component (if applicable):
spacewalk-backend-tools-0.7.18-1.fc12.noarch

How reproducible:
every time i start spacewalk-repo-sync

Expected results:
fix or patch

Comment 1 Michael Mráka 2010-01-19 16:45:54 UTC
Bug summary: In Fedora 12 time values from rpm are interpreted as long (not int) which causes they aren't been transofmed into oracle's datetime format.

Comment 2 Michael Mráka 2010-01-19 16:47:04 UTC
Fixed in 
commit ba25dcbb0ba53a0104f1738e60d15cf437835b4f
    Automatic commit of package [spacewalk-backend] release [0.8.32-1].
commit 74b827fecaa4178bf98ead2df5938859fef5c522
    556460 - time values are <long> on F12

and included into spacewalk-backend-0.8.32-1 package.

Comment 3 Erik Logtenberg 2010-01-21 22:16:55 UTC
Running into the same issue here, nice to see that it's already fixed! When will the updated package be available in the updates repository? Or is it already available elsewhere?

Comment 4 Michael Mráka 2010-01-22 11:06:35 UTC
(In reply to comment #3)
> Running into the same issue here, nice to see that it's already fixed! When
> will the updated package be available in the updates repository? Or is it
> already available elsewhere?    

There is a fixed package released in nightly repo.
Unfortunately we do not currently plan any update release for 0.7 so please apply manually fix from the commit 74b827fecaa4178bf98ead2df5938859fef5c522 above.

Comment 5 Erik Logtenberg 2010-01-22 20:29:23 UTC
I tried to apply the fix manually. This only partially works, because this specific file is already changed to some degree since the version in release 0.7, so the patch doesn't fully apply.
Nevertheless, I was able to apply three of the four changes (the fourth change is in a piece of code that doesn't seem to exist yet in 0.7, if I'm not mistaking).

However I keep getting the same results. First I simply scheduled a new sync, which gave the same errors. Then I thought, maybe the error is already in the database, so I deleted the channel and re-created it; but even then reposync gave the same errors.

On a side note, I notice that I cannot stop reposync through the spacewalk webinterface, right? I especially noticed that spacewalk also doesn't stop a running reposync when its channel gets deleted...

Anyway, I would really like to run spacewalk with a Fedora 12 repository, what is the best way to do this, upgrade to the nightly builds?

Comment 6 Michael Mráka 2010-01-23 10:58:27 UTC
Created attachment 386316 [details]
This is patch for spacewalk 0.7

Hi Erik,

here is a patch backport for spacewalk 0.7.
Apply with
cd /usr/share/rhn/
patch -p2 <sw7.patch

Comment 7 Michael Mráka 2010-02-16 12:59:50 UTC
Spacewalk 0.8 has been released


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