Bug 1253197 - API timeout (http error 503) for taskomatic.reinitializeAllSchedulesFromNow
Summary: API timeout (http error 503) for taskomatic.reinitializeAllSchedulesFromNow
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Taskomatic
Version: 570
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-13 08:22 UTC by Pavel Studeník
Modified: 2018-04-09 14:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-09 14:46:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pavel Studeník 2015-08-13 08:22:16 UTC
Description of problem:
After the system's clock was changed and I call reinitialize all taskomatic's schedules by API I got "503 Service Temporarily Unavailable". 

It happens only sometimes in own script.

Version-Release number of selected component (if applicable):
spacewalk-java-2.3.8-108.el6sat.noarch


How reproducible:
only sometimes

Steps to Reproduce:
1. ntpd -gxq && hwclock --systohc"
2. python client.taskomatic.reinitializeAllSchedulesFromNow(key)

Expected results:
without traceback

Actual results:
  File "/mnt/tests/CoreOS/RHN-Satellite/Helper/quartz_reinitialize.py", line 17, in quartz_reinitialize
    client.taskomatic.reinitializeAllSchedulesFromNow(key)
  File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request
    verbose=self.__verbose
  File "/usr/lib64/python2.6/xmlrpclib.py", line 1243, in request
    headers
xmlrpclib.ProtocolError: <ProtocolError for smqa-x3550m3-02-vm01.lab.eng.brq.redhat.com/rpc/api: 503 Service Temporarily Unavailable>

Comment 2 Tomas Lestach 2018-04-09 14:46:12 UTC
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. 

Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.


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