Hide Forgot
Description of problem: Registered a fresh installed CDS (cds001) with rhui-manager and associate a repo with it. However When i tried to display the CDS sync status with "DC", got an error message: An unexpected error has occurred during the last operation. More information can be found in /root/.rhui/rhui.log. Version-Release number of selected component (if applicable): pulp 0.170 rhui tools 2.0.15 How reproducible: Always Steps to Reproduce: 1. Registered a CDS (cds001) using rhui-manager 2. associate a repo with CDS 3. Check sync status Actual results -= CDS Synchronization Status =- Last Refreshed: 18:13:16 (updated every 5 seconds, ctrl+c to exit) cds001 ...................................................... [ UP ] dhcp193-16.pnq.redhat.com ................................... [ UP ] Next Sync Last Sync Last Result ------------------------------------------------------------------------------ cds001 04-25-2011 19:12 Never scheduled dhcp193-16.pnq.redhat.com An unexpected error has occurred during the last operation. More information can be found in /root/.rhui/rhui.log. ------------------------------------------------------------------------------ -= Red Hat Update Infrastructure Management Tool =- -= Synchronization Status =- dr display repo synchronization schedules sr trigger an individual repository sync dc display CDS synchronization schedules sc trigger an individual CDS sync logout removes stored authentication credentials and exits < move to the previous screen ^, home move to the home screen /, clear clears the screen ?, help display help q, quit, exit exit Expected results: CDS sync status should be displayed without any error Additional info: [root@dhcp193-76 ~]# tail -f /root/.rhui/rhui.log Shell.listen(self) File "/usr/lib/python2.6/site-packages/rhui/common/shell.py", line 191, in listen item.func(*args, **item.kwargs) File "/usr/lib/python2.6/site-packages/rhui/tools/screens/sync.py", line 73, in cds_display self._sync_display('-= CDS Synchronization Status =-', self.pulp.cds_with_sync_status, True) File "/usr/lib/python2.6/site-packages/rhui/tools/screens/sync.py", line 234, in _sync_display self.prompt.write(SYNC_STATUS_LINE % (render.ghetto_format_date(data['next_scheduled_sync']), render.format_date(data['last_sync']), self._color_sync_state(data))) File "/usr/lib/python2.6/site-packages/rhui/tools/screens/sync.py", line 252, in _color_sync_state return self.prompt.color(data['sync_state'], STATE_COLORS[data['sync_state']]) KeyError: None ^C [root@dhcp193-29 yum.repos.d]# tail -f /var/log/pulp-cds/gofer.log Received initialize call ^C [root@dhcp193-29 yum.repos.d]# tail -f /var/log/gofer/agent.log "method": "set_repo_auth", "auth": { "secret": "68c4175f-61c9-432c-a108-70373edf09a1", "uuid": "cds-dhcp193-29.pnq.redhat.com" } } 2011-04-25 12:43:06,152 [INFO][worker-0] set_repo_auth() @ cdsplugin.py:125 - Setting repo auth credentials for repo [rhui-1.2-5Server-x86_64] 2011-04-25 12:43:06,153 [INFO][worker-0] _write_cert_bundle() @ repo_cert_utils.py:351 - Storing repo cert file [/etc/pki/content/rhui-1.2-5Server-x86_64/consumer-rhui-1.2-5Server-x86_64.ca] 2011-04-25 12:43:06,153 [INFO][worker-0] _write_cert_bundle() @ repo_cert_utils.py:351 - Storing repo cert file [/etc/pki/content/rhui-1.2-5Server-x86_64/consumer-rhui-1.2-5Server-x86_64.cert] 2011-04-25 12:43:06,154 [INFO][worker-0] _write_cert_bundle() @ repo_cert_utils.py:351 - Storing repo cert file [/etc/pki/content/rhui-1.2-5Server-x86_64/consumer-rhui-1.2-5Server-x86_64.key] ^C [root@dhcp193-29 yum.repos.d]#
The issue doesn't seem related to cds001; that displays fine. The issue is in the dhcp193 CDS. Was this created with an older version of RHUI Manager? What sorts of operations did you run on that CDS? Please run "pulp-admin cds list" and "pulp-admin cds status --hostname dhcp193-16.pnq.redhat.com" and paste in the results.
Correct, First I registered the dhcp193 CDS using pulp api's. and binded a rhel6 repo of feed type "yum". Then I tried to associate a new "rhui-1.2-5Server-x86_64" repo to dhcp193 using rhui-manager and got same error as mentioned above in "additional info" under rhui.log. then later I registered a new CDS 'cds001' using rhui-manager (2.0.15-1) and again associated a rhui-1.2-5Server-x86_64 repo to it. This time again I got the same error in rhui.log. here is the output of "cds list" : [root@dhcp193-25 ~]# pulp-admin -u admin -p admin cds list +------------------------------------------+ CDS Instances +------------------------------------------+ Name dhcp193-16.pnq.redhat.com Hostname dhcp193-16.pnq.redhat.com Description None Repos rhel6, rhui-1.2-5Server-x86_64 Last Sync 2011-04-25 06:15:11 Status: Responding No Last Heartbeat 2011-04-25 16:48:57 Name dhcp193-29.pnq.redhat.com Hostname cds001 Description None Repos rhui-1.2-5Server-x86_64 Last Sync 2011-04-25 16:42:00 Status: Responding No Last Heartbeat 2011-04-25 16:49:02 Note: as you can see in the 'cds list' heartbeat is not responding, so I restarted the 'pulp-server' service. All service were restarted successfully. [root@dhcp193-25 ~]# 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 ] but when I tried 'cds list' again, I got the "Internal server Error". I'll report this issue in other defect 698577.
Ya, don't do that. RHUI Manager does stuff during the CDS registration that the Pulp CLI doesn't. The Pulp CLI can be used to look up information in the RHUI but should never be used to create/register anything as RHUI Manager hides extra logic and calls from the user that it expects to occur to function correctly.