Bug 563245 - Upgrading from 0.6 overwrites jabber password in rhn.conf
Summary: Upgrading from 0.6 overwrites jabber password in rhn.conf
Keywords:
Status: CLOSED DUPLICATE of bug 679335
Alias: None
Product: Spacewalk
Classification: Community
Component: Installation
Version: 0.7
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Milan Zázrivec
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space16
TreeView+ depends on / blocked
 
Reported: 2010-02-09 16:30 UTC by Justin Sherrill
Modified: 2011-08-05 14:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-05 14:42:19 UTC
Embargoed:

Attachments (Terms of Use)

Description Justin Sherrill 2010-02-09 16:30:41 UTC 
Description of problem:


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


How reproducible:
Upgrade from 0.6 to 0.7

  
Actual results:
Osa will not talk to jabberd because it is using a different password than before.  Clearing the jabberd auth db will resolve the issue.

Expected results:
Osa-dispatcher should talk to jabberd just fine.

Additional info:
Comment 1 Jan Pazdziora 2010-02-10 08:48:33 UTC 
Milan, care to look at this upgrade related report?
Comment 2 Jan Pazdziora 2010-11-19 16:04:57 UTC 
Mass-moving to space13.
Comment 3 Miroslav Suchý 2011-04-11 07:33:39 UTC 
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.
Comment 4 Miroslav Suchý 2011-04-11 07:37:14 UTC 
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.
Comment 5 Jan Pazdziora 2011-07-20 11:51:56 UTC 
Aligning under space16.
Comment 6 Clifford Perry 2011-08-05 12:53:27 UTC 
Since 0.6 is not supported - can we close this out? Does it happen in current 1.3 -> 1.4 upgrades?

Cliff
Comment 7 Milan Zázrivec 2011-08-05 14:42:19 UTC 
Unfortunately yes, this still is an issue during current Spacewalk upgrades.

When we run spacewalk-setup --upgrade, we do create new password for
osa-dispatcher (and in turn need to tear down jabber's authreg.db).

True fix for this problem is in fact described in bug #679335, so I'm
gonna close this one as a duplicate of this bug.

*** This bug has been marked as a duplicate of bug 679335 ***
Note You need to log in before you can comment on or make changes to this bug.