Bug 1253197 - API timeout (http error 503) for taskomatic.reinitializeAllSchedulesFromNow
API timeout (http error 503) for taskomatic.reinitializeAllSchedulesFromNow
Status: CLOSED DEFERRED
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Taskomatic (Show other bugs)
570
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Tomas Lestach
Red Hat Satellite QA List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-13 04:22 EDT by Pavel Studeník
Modified: 2018-04-09 10:46 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-09 10:46:12 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Pavel Studeník 2015-08-13 04:22:16 EDT
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 10:46:12 EDT
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.