Bug 786423 - "Update All" for updating all system packages should show some notification on UI before and after package updation completes
Summary: "Update All" for updating all system packages should show some notification o...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Justin Sherrill
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-01 11:59 UTC by Sachin Ghai
Modified: 2014-09-18 16:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-18 17:38:26 UTC
Target Upstream Version:


Attachments (Terms of Use)
agent.log from client when package update complete. (33.29 KB, application/octet-stream)
2012-02-01 12:01 UTC, Sachin Ghai
no flags Details

Description Sachin Ghai 2012-02-01 11:59:13 UTC
Description of problem:
I was trying to update all packages on newly registered node of rhel6.1. Packages were updated and system updated to rhel6.2 level.

However when I triggered "Update All" from UI, nothing happens on UI ( No notification and even no notification when package updation completes.

On otherside I got request timeout in pulp.log. I tried this two times and observed same behaviour.

Version-Release number of selected component (if applicable):
katello-0.1.206-1.el6.noarch
pulp-0.0.263-1.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. sync a rhel6.2 product on server
1. Register a rhel6.1 node using rhsm with katello server
2. Subscribe a rhel6.2 product
3. install katello-agent on client node
4. Trigger "Update All" from systems
  
Actual results:
All Packages updated successfully on client node, however no notification generated on UI. And a request time out error in pulp.log

Expected results:
There should be no error in logs and there should be some notification on UI for end user when the update completes.

Additional info:

pulp.log says:
================

[root@dhcp201-102 ~]# tail -f /var/log/pulp/pulp.log 
2012-02-01 16:15:28,746 28254:140557584148224: gofer.rmi.policy:INFO: policy:139 sent (25b0621a-ae35-47e6-ba3f-d746863471d6):
{
  "classname": "Packages", 
  "kws": {}, 
  "args": [
    null
  ], 
  "method": "update", 
  "cntr": null
}

2012-02-01 16:25:29,442 28254:140557584148224: pulp.server.tasking.task:ERROR: task:474 Task failed: Task da4ea9c0-4cc1-11e1-a271-52540079a8d0: ConsumerApi.__updatepackages(25b0621a-ae35-47e6-ba3f-d746863471d6, None, )
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/pulp/server/tasking/task.py", line 420, in run
    result = self.callable(*self.args, **self.kwargs)
  File "/usr/lib/python2.6/site-packages/pulp/server/api/consumer.py", line 509, in __updatepackages
    return packages.update(names)
  File "/usr/lib/python2.6/site-packages/gofer/rmi/stub.py", line 72, in __call__
    return self.stub._send(request, opts)
  File "/usr/lib/python2.6/site-packages/gofer/rmi/stub.py", line 133, in _send
    return self.__send(request, options)
  File "/usr/lib/python2.6/site-packages/gofer/rmi/stub.py", line 164, in __send
    any=opts.any)
  File "/usr/lib/python2.6/site-packages/gofer/rmi/policy.py", line 144, in send
    return self.__getreply(sn, reader)
  File "/usr/lib/python2.6/site-packages/gofer/rmi/policy.py", line 183, in __getreply
    raise RequestTimeout(sn, 1)
RequestTimeout: ('0ddb9e16-5762-4c33-950c-684870a6a41e', 1)

Comment 1 Sachin Ghai 2012-02-01 12:01:35 UTC
Created attachment 558803 [details]
agent.log from client when package update complete.

Comment 2 Mike McCune 2012-02-09 01:09:29 UTC
agreed we need this but bumping to 1.1

Comment 3 Mike McCune 2013-08-16 17:59:08 UTC
getting rid of 6.0.0 version since that doesn't exist

Comment 4 Mike McCune 2014-03-18 17:38:26 UTC
This bug was closed because of a lack of activity.  If you feel this bug should be reconsidered for attention please feel free to re-open the bug with a comment stating why it should be reconsidered.


Note You need to log in before you can comment on or make changes to this bug.