Hide Forgot
Description of problem: I Configured a fresh RHUI setup. After providing the content cert at very first login, when I login with default admin user, the following waring message appeared in pulp.logs 2011-05-26 08:51:45,034 [WARNING][Dummy-2] schedule() @ task.py:289 - Task 4886d9b0-8747-11e0-b549-525400ff61a5: cull_history(, ) missed 1 scheduled runs Version-Release number of selected component (if applicable): pulp 0.181 rhui-tools:2.0.25 How reproducible: Steps to Reproduce: 1. Configured a fresh setup of RHUI 2. Got this "warning message" when login with deafult admin user Actual results: 2011-05-26 08:28:55,356 [INFO][asynctaskreplyqueue] connect() @ broker.py:102 - {dhcp193-79.pnq.redhat.com:5672} connected to AMQP 2011-05-26 08:51:44,643 [INFO][Dummy-2] initialize() @ connection.py:48 - Attempting Database connection with seeds = localhost 2011-05-26 08:51:44,657 [INFO][Dummy-2] initialize() @ connection.py:53 - Database connection established with: seeds = localhost, name = pulp_database 2011-05-26 08:51:45,034 [WARNING][Dummy-2] schedule() @ task.py:289 - Task 4886d9b0-8747-11e0-b549-525400ff61a5: cull_history(, ) missed 1 scheduled runs Expected results: Since this is very fresh setup and even no repo is added; then this warning message seems to be a misleading message. especially with keyword "missed 1 scheduled runs" Additional info: No repo is added on rhua server. Connected: dhcp193-79.pnq.redhat.com ------------------------------------------------------------------------------ rhui (repo) => l No repositories are currently managed by the RHUI ------------------------------------------------------------------------------ rhui (repo) =>
added to rhui-20 tracker
Punting to 2.1. I've asked jconnor about it and it doesn't sound like it's an easy fix, but it's also not hurting anything.
Have never seen this across the different RHUI's I've setup. Moving to MODIFIED for verification.
oh, just realized you said that was in the pulp logs. Will need to check to see if this is still happening.
Changed both auditing and consumer history culling to start in the future Fix pushed in 549079c4f5de7cfcb78d039045297fede33120a8
Verified with RHUI 2.0.2 iso (RHEL-6.2-RHUI-2.0.2-20120209.0-Server-x86_64-DVD1.iso). Th reported issue is no longer reproducible with the latest rhui2.0.2 iso. Never seen this warning message on freshly installed setups. Moving this to verified.
Released in RHUI 2.0.2