Users lose all history and error reporting for synchronization results when httpd is restarted. Would be ideal if we could get this history stored and persisted in the database so we have a running record over time that doesn't go away if the server gets restarted.
This has been addressed with the implementation of the task history collection and webservices api
build: 0.188
[root@preethi ~]# rpm -q pulp pulp-0.0.200-1.fc14.noarch [root@preethi ~]# pulp-admin repo status --id=f14 +------------------------------------------+ Status for f14 +------------------------------------------+ Repository: f14 Number of Packages: 2766 Last Sync: 2011-07-06 13:56:14-04:00 Currently syncing: 100% done (2773 of 2773 packages downloaded) [root@preethi ~]# [root@preethi ~]# [root@preethi ~]# [root@preethi ~]# service pulp-server restart Stopping httpd: [ OK ] Stopping Qpid AMQP daemon: [ OK ] Stopping mongod: [ OK ] Starting mongod: [ OK ] Starting Qpid AMQP daemon: [ OK ] Starting httpd: [ OK ] [root@preethi ~]# pulp-admin repo status --id=f14 +------------------------------------------+ Status for f14 +------------------------------------------+ Repository: f14 Number of Packages: 2766 Last Sync: 2011-07-06 13:56:14-04:00 Currently syncing: progress unknown [root@preethi ~]# pulp-admin consumer history --consumerid=pulp-client Usage: pulp-admin <options> consumer history <options> pulp-admin: error: no such option: --consumerid [root@preethi ~]# pulp-admin consumer history --id=pulp-client +------------------------------------------+ Consumer History +------------------------------------------+ Event Type Repo Bound Timestamp 2011-07-05 10:57:45-04:00 Originator admin Repo ID f14 Event Type Consumer Created Timestamp 2011-07-05 09:06:52-04:00 Originator admin
Closing with Community Release 15 pulp-0.0.223-4.