Bug 510723 - RFE : sat activation fail when rhn.webqa is slow, it should wait longer or try again
Summary: RFE : sat activation fail when rhn.webqa is slow, it should wait longer or tr...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Installer
Version: 530
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Devan Goodwin
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2009-07-10 13:06 UTC by Petr Sklenar
Modified: 2014-07-04 13:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-04 13:28:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Petr Sklenar 2009-07-10 13:06:22 UTC 
Description of problem:
when rhn.webqa is very slow then installation script fails after short time. It should try activation again.

Version-Release number of selected component (if applicable):
sat-5.3.0-RHEL5-re20090702-i386

How reproducible:
sometime 
(today always ..)

Steps to Reproduce:
1. rhn.webqa is very very slow
2. ./install.pl --answer-file=smth.conf 
# (rhn-parent = satellite.rhn.webqa.redhat.com)
3. during satellite activation it fails after +- 30 sec

  
Actual results:

There was a problem activating the satellite: Remote activation failure.

tail /var/log/rhn/rhn_server_satellite.log
2009/07/10 08:36:12 -04:00 Red Hat Network Satellite - live synchronization
2009/07/10 08:36:12 -04:00    url: https://satellite.rhn.webqa.redhat.com
2009/07/10 08:36:12 -04:00    debug/output level: 1
2009/07/10 08:38:12 -04:00 
2009/07/10 08:38:12 -04:00 
ERROR: there was a problem synchronizing the information.
       Error message: Timeout Exception


When I installed satellite in disconnected mode then I try activation via 'rhn-satellite-activate' - it passed. It seems that rhn-satellite-activate waits longer for rhn-parent.

Expected results:
it should wait bit longer or try activation again.

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