Bug 698395

Summary: cds status still shows the error from previous sync when the sync is actually running
Product: [Retired] Pulp Reporter: Preethi Thomas <pthomas>
Component: nodesAssignee: Jay Dobies <jason.dobies>
Status: CLOSED CURRENTRELEASE QA Contact: Preethi Thomas <pthomas>
Severity: low Docs Contact:
Priority: medium    
Version: unspecifiedCC: skarmark
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-24 20:14:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Preethi Thomas 2011-04-20 19:37:46 UTC
Description of problem:

[root@pulp-cds ~]# rpm -q pulp-cds
pulp-cds-0.0.168-1.fc14.noarch


I had a cds sync fail first. So CDS status gave me the error. 

But on a subsequent cds sync which is running, cds status still shows previous  error


[root@preethi ~]# pulp-admin cds status --hostname=pulp-cds.usersys.redhat.com 
+------------------------------------------+
                 CDS Status
+------------------------------------------+

Name                	pulp-cds.usersys.redhat.com
Hostname            	pulp-cds                 
Description         	PULP CDS                 
Repos               	f14-original             
Last Sync           	2011-04-20 19:28:55      
Status:
   Responding       	Yes                      
   Last Heartbeat   	2011-04-20 19:48:07      

+------------------------------------------+
           Most Recent Sync Tasks
+------------------------------------------+

State               	error                    
Start Time          	2011-04-20 19:28:55      
Finish Time         	2011-04-20 19:28:55      
Exception           	PulpException('Error on the CDS during sync; check the server log for more information',)
Traceback
    Traceback (most recent call last):
        File "/usr/lib/python2.7/site-packages/pulp/server/tasking/task.py", line 335, in run
    result = self.callable(*self.args, **self.kwargs)
        File "/usr/lib/python2.7/site-packages/pulp/server/api/cds.py", line 366, in cds_sync
    self.dispatcher.sync(cds, repos)
        File "/usr/lib/python2.7/site-packages/pulp/server/cds/dispatcher.py", line 161, in sync
    stub.sync(repo_base_url, repos)
        File "/usr/lib/python2.7/site-packages/gofer/messaging/stub.py", line 71, in __call__
    return self.stub._send(request, opts)
        File "/usr/lib/python2.7/site-packages/gofer/messaging/stub.py", line 142, in _send
    any=opts.any)
        File "/usr/lib/python2.7/site-packages/gofer/messaging/policy.py", line 126, in send
    return self.__getreply(sn)
        File "/usr/lib/python2.7/site-packages/gofer/messaging/policy.py", line 172, in __getreply
    return self.__onreply(envelope)
        File "/usr/lib/python2.7/site-packages/gofer/messaging/policy.py", line 188, in __onreply
    raise RemoteException.instance(reply)
      PulpException: 'Error on the CDS during sync; check the server log for more information'


[root@preethi ~]# 



But if I see in gofer.log of the cds I see that the cds sync is running


Received sync call
[{'name': 'f14-original', 'publish': True, 'relative_path': 'released/F-14/GOLD/Fedora/x86_64/os', 'source': {'url': 'http://download.devel.redhat.com/released/F-14/GOLD/Fedora/x86_64/os/', 'type': 'yum', 'supported_types': ['yum', 'local', 'rhn']}, '_id': 'f14-original', 'arch': 'x86_64', 'id': 'f14-original'}]
Synchronizing repo at [https://preethi.usersys.redhat.com//pulp/repos/released/F-14/GOLD/Fedora/x86_64/os]
Synchronizing repo [f14-original] from [https://preethi.usersys.redhat.com//pulp/repos/released/F-14/GOLD/Fedora/x86_64/os] to [/var/lib/pulp-cds/released/F-14/GOLD/Fedora/x86_64/os]





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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Sayli Karmarkar 2011-07-15 22:03:43 UTC
This should be fixed with task persistence. Please re-verify.

Comment 2 Preethi Thomas 2011-09-07 17:20:45 UTC
verified

[root@preethi ~]# pulp-admin cds sync  --hostname=pulp-cds.usersys.redhat.com
Sync for CDS [pulp-cds.usersys.redhat.com] started
Use "cds status" to check on the progress

[root@preethi ~]# pulp-admin cds status  --hostname=pulp-cds.usersys.redhat.com
+------------------------------------------+
                 CDS Status
+------------------------------------------+

Name                	pulp-cds.usersys.redhat.com
Hostname            	pulp-cds.usersys.redhat.com
Description         	None                     
Cluster             	None                     
Sync Schedule       	None                     
Repos               	None                     
Last Sync           	2011-09-07 13:29:25-04:00
Status:
   Responding       	Yes                      
   Last Heartbeat   	2011-09-07 17:29:29.416681+00:00

+------------------------------------------+
           Most Recent Sync Tasks
+------------------------------------------+

State               	Finished                 
Start Time          	2011-09-07 13:29:25-04:00
Finish Time         	2011-09-07 13:29:25-04:00

Comment 3 Preethi Thomas 2012-02-24 20:14:36 UTC
Pulp v1.0 is released
Closed Current Release.

Comment 4 Preethi Thomas 2012-02-24 20:19:26 UTC
Pulp v1.0 is released.