Bug 928452 - Issues with rhnreg_ks when a package is already installedk
Summary: Issues with rhnreg_ks when a package is already installedk
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Proxy Server
Version: 1.8
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jan Pazdziora
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space27
TreeView+ depends on / blocked
 
Reported: 2013-03-27 16:44 UTC by njfsmallet
Modified: 2017-09-28 18:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-28 17:25:26 UTC
Embargoed:


Attachments (Terms of Use)

Description njfsmallet 2013-03-27 16:44:37 UTC
Description of problem:

A problem occurs when registering with an activation key which try to install an already installed package though the spacewalk proxy. Then, the deployment of configuration files failed.


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


How reproducible:


Steps to Reproduce:
1. Create an activation key associated with packages
2. Install manually theses packages
3. Register the system
  
Actual results:

Package Install scheduled by (none)
Client execution returned "Error while executing packages action: empty transaction [[6]]" (code -1)

Then :

Schedule a config deploy for activation key scheduled by (none)
This action requires the successful completion of a prior action before it can be rescheduled



Expected results:


Additional info:

Comment 1 Jan Pazdziora 2013-03-28 14:08:04 UTC
What client packages do you use? More specifically, what does

rpm -qa | grep rhn | sort

return on that client machine?

Comment 2 njfsmallet 2013-03-28 14:57:41 UTC
(In reply to comment #1)
> What client packages do you use? More specifically, what does
> 
> rpm -qa | grep rhn | sort
> 
> return on that client machine?

rhncfg-5.10.24-2.fc17 
rhncfg-actions-5.10.24-2.fc17
hncfg-client-5.10.24-2.fc17
rhncfg-management-5.10.24-2.fc17
rhn-check-1.6.47-1.fc16
rhn-client-tools-1.6.47-1.fc16
rhn-custom-info-5.4.13-2.fc17
rhnlib-2.5.49-2.fc17
rhnmd-5.3.10-2.fc17
rhnsd-4.9.14-2.fc17
rhn-setup-1.6.47-1.fc16 
yum-rhn-plugin-1.6.16-2.fc17

Comment 3 Jan Pazdziora 2013-03-28 15:10:14 UTC
I'd recommend upgrading your client packages to the one in Spacewalk 1.9 client repos on your Fedora 17.

Comment 4 njfsmallet 2013-03-28 16:00:37 UTC
(In reply to comment #3)
> I'd recommend upgrading your client packages to the one in Spacewalk 1.9
> client repos on your Fedora 17.

Thx, now it's working with theses packages :

osad-5.11.10-1.fc17.noarch
rhncfg-5.10.36-1.fc17.noarch
rhncfg-actions-5.10.36-1.fc17.noarch
rhncfg-client-5.10.36-1.fc17.noarch
rhncfg-management-5.10.36-1.fc17.noarch
rhn-check-1.8.26-1.fc17.noarch
rhn-client-tools-1.8.26-1.fc17.noarch
rhn-custom-info-5.4.14-1.fc17.noarch
rhnlib-2.5.55-1.fc17.noarch
rhnmd-5.3.11-1.fc17.noarch
rhnsd-4.9.14-2.fc17.i686
rhn-setup-1.8.26-1.fc17.noarch
yum-rhn-plugin-1.8.8-1.fc17.noarch

Comment 5 Jan Pazdziora 2013-03-28 17:25:26 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > I'd recommend upgrading your client packages to the one in Spacewalk 1.9
> > client repos on your Fedora 17.
> 
> Thx, now it's working with theses packages :
> 
> osad-5.11.10-1.fc17.noarch
> rhncfg-5.10.36-1.fc17.noarch
> rhncfg-actions-5.10.36-1.fc17.noarch
> rhncfg-client-5.10.36-1.fc17.noarch
> rhncfg-management-5.10.36-1.fc17.noarch
> rhn-check-1.8.26-1.fc17.noarch
> rhn-client-tools-1.8.26-1.fc17.noarch

Thank you for the confirmation. I'm going to close this bugzilla now.

Comment 6 Eric Herget 2017-09-28 18:07:30 UTC
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.


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