Bug 725676 - Channels missing after upgrade to 1.5
Summary: Channels missing after upgrade to 1.5
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Spacewalk
Classification: Community
Component: WebUI
Version: 1.5
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space16
TreeView+ depends on / blocked
 
Reported: 2011-07-26 09:17 UTC by Frederic
Modified: 2012-03-06 09:17 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-07-26 13:24:55 UTC
Embargoed:


Attachments (Terms of Use)
catalina.out containing errors when trying to recreate channels. (18.50 KB, application/octet-stream)
2011-07-26 09:17 UTC, Frederic
no flags Details
all spacewalk schema upgrades (122.18 KB, application/x-gzip)
2011-07-27 07:23 UTC, Frederic
no flags Details

Description Frederic 2011-07-26 09:17:53 UTC
Created attachment 515224 [details]
catalina.out containing errors when trying to recreate channels.

Description of problem:

I did create and did synchronize CentOS 6 x86_64 channels into Spacewalk 1.4, the day after I did upgrade Spacewalk to 1.5 (following procedure).  Big surprise, CentOS 6 channels has disappear but packages are still there.  When I try to recreate channels, I got "The server experienced a problem which prevented your request from being filled out. It may not be possible to execute this action at this time.  Please help us correct this problem by contacting us with details of how you received this message."

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

1.5

How reproducible:

Steps to Reproduce:
1. create and sync new channel
2. upgrade from 1.4 to 1.5
  
Actual results:

channels missing

Expected results:

channels available

Additional info:
I attach catalina.out containing errors when trying to recreate channels.

Comment 1 Tomas Lestach 2011-07-26 11:45:55 UTC
What is the output of command
$ rhn-schema-version
?

Comment 2 Frederic 2011-07-26 12:00:41 UTC
this is the output:

1.1.31-1.el5

Comment 3 Frederic 2011-07-26 12:53:55 UTC
quite strange because I'm so sure that I did upgrade the schema, log file (/var/log/spacewalk/schema-upgrade/20110722-120205-to-spacewalk-schema-1.5.log) is present to tell the truth

Comment 4 Tomas Lestach 2011-07-26 13:24:55 UTC
Frederic, spacewalk-schema-1.1.31-1.el5.noarch.rpm was included in Spacewalk 1.1.
So, your schema upgrade had to fail already when you upgraded from Spacewalk 1.1.

schema-upgrade logs since that time may include failures.


Closing the BZ as NOTABUG.

Comment 5 Frederic 2011-07-26 14:20:30 UTC
You're so quick to close a bug.  I've all logs of schema upgrade (from 1.1 to 1.5).  Are you so sure your software is bugless?

Comment 6 Jan Pazdziora (Red Hat) 2011-07-26 15:37:43 UTC
(In reply to comment #5)
> You're so quick to close a bug.  I've all logs of schema upgrade (from 1.1 to
> 1.5).

Can you attach the logs?

Comment 7 Frederic 2011-07-27 07:23:18 UTC
Created attachment 515427 [details]
all spacewalk schema upgrades

Comment 8 Frederic 2011-07-27 07:24:23 UTC
log files attached as tar.gz file

Comment 9 Jan Pazdziora (Red Hat) 2011-07-27 11:06:15 UTC
(In reply to comment #8)
> log files attached as tar.gz file

Your schema upgrade logs look good. Then however I don't understand why the schema version as reported by rhn-schema-version would be 1.1.31-1.el5, unless your /etc/rhn/rhn.conf now points to completely different database which still has the 1.1 schema in it.

When you run spacewalk-schema-upgrade -- what does it say? Does it suggest to upgrade from 1.1 to 1.5, or does it say that the schema is fully up-to-date?

Comment 10 Frederic 2011-07-27 11:42:26 UTC
as I did run spacewalk-schema-upgrade command yesterday, the output is:

Schema upgrade: [spacewalk-schema-1.5.6-1.el5] -> [spacewalk-schema-1.5.6-1.el5]
Your database schema already matches the schema package version [spacewalk-schema-1.5.6-1].

Comment 11 Jan Pazdziora (Red Hat) 2011-07-27 15:07:11 UTC
And yet,

$ rhn-schema-version

prints

1.1.31-1.el5

?

Comment 12 Frederic 2011-07-27 15:18:59 UTC
now it prints

1.5.6-1.el5

I cannot explain what was wrong but after the migration to 1.5 the schema version vas 1.1.31-1.el5 and latest channels were missing.  Now, schema version is ok and I'm re running spacewalk-repo-sync to populate (once again) CentOS 6 channels.

Comment 13 Frederic 2011-07-29 07:21:00 UTC
I guess you have no answer to the problem I had.

Comment 14 Jan Pazdziora (Red Hat) 2011-07-29 11:08:59 UTC
(In reply to comment #13)
> I guess you have no answer to the problem I had.

Indeed.


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