Bug 61469

Summary:	rhnreg_ks return codes
Product:	Red Hat Satellite 5	Reporter:	Isaiah Weiner <iweiner>
Component:	Registration	Assignee:	Cristian Gafton <gafton>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	alikins, mihai.ibanescu, pjones, taw
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-06-26 19:04:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Isaiah Weiner 2002-03-20 04:33:52 UTC

Description of problem:
At Cisco we have a wrapper shell script to execute rhnreg_ks and if successful 
(returning 0), removes a symbolic link in the system's /etc/cron.daily/ 
directory.  We're encountering cases when it appears to have succeeded in 
registration but it didn't return the right error code, so the symlink wasn't 
removed.  Then later, we get a legit error because the machine is already 
registered under those credentials.

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


How reproducible:
Always

Steps to Reproduce:
1. rhnreg_ks

Additional info:

Comment 1 Adrian Likins 2002-03-20 04:47:44 UTC

what are the cases where it returns the wrong error code, and what
error code does it return?

Comment 2 Isaiah Weiner 2002-03-20 05:06:31 UTC

We were hoping you could tell us that.  There is no stderr when it successfully 
registers and doesn't return the right error code, so cron reports nothing.  
It's happening about 1 out of 20 times.

Comment 3 Cristian Gafton 2002-04-11 09:33:01 UTC

can you please run that script through some sort of enhanced set -x so we know
what is going on - you're asking us to shoot in the dark here, with nothing more
than "sometimes there is an error" to start with.

Comment 4 Josef Komenda 2002-06-20 17:19:44 UTC

Any updates on this? Have you been able do duplicate the problem, or set up some
kind of capture script?

Comment 5 Isaiah Weiner 2002-06-26 19:04:39 UTC

Sorry for the lateness; I was out of town for a few weeks.

As I stated earlier, it's sporadic at best.  The only time I see the problem is 
after it happens, on the *next* day's cron output, which I get from every 
single Linux box at Cisco.  I'm not going to run all of them through -x for 
something that happens so sporadically.  If I see it happening more frequently 
I'll consider it more seriously.

Comment 6 Josef Komenda 2002-08-14 19:17:54 UTC

No action for 6+ weeks, unable to isolate or duplicate, so closing.