Bug 1110371 - firebug raises 404 on sync completion for missing notifications
Summary: firebug raises 404 on sync completion for missing notifications
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Stephen Benjamin
QA Contact: sthirugn@redhat.com
URL: http://projects.theforeman.org/issues...
Whiteboard:
: 1105659 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-17 13:53 UTC by Sachin Ghai
Modified: 2019-09-26 18:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-11 12:23:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
firebug raises NetworkError (59.15 KB, image/png)
2014-06-17 13:53 UTC, Sachin Ghai
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 6512 0 None None None 2016-04-22 15:39:24 UTC

Description Sachin Ghai 2014-06-17 13:53:54 UTC
Created attachment 909593 [details]
firebug raises NetworkError

Description of problem:
I synced 2 large repos ( rhel65 and rhel64), sync was completed but at the end of sync completion firebug raised NetworkError 404 not found

"NetworkError: 404 Not Found - https://dhcp207-55.lab.eng.pnq.redhat.com/katello/notices/get_new"

production.log has following error:

AbstractController::ActionNotFound (The action 'get_new' could not be found for NoticesController):
  lib/middleware/catch_json_parse_errors.rb:9:in `call'

I'm assuming, its because of missing notification on sync status page.


Version-Release number of selected component (if applicable):
sat6 beta snap9 compose 2

How reproducible:
always

Steps to Reproduce:
1. sync repo from sync status page
2. check firebug console on sync completion
3.

Actual results:
firebug raised NetworkError 404 not found

"NetworkError: 404 Not Found - https://dhcp207-55.lab.eng.pnq.redhat.com/katello/notices/get_new"
Expected results:


Additional info:

Comment 2 Brad Buckingham 2014-07-01 18:49:57 UTC
I see this issue on the beta install; however, I do not see it upstream.  We should investigate difference.  It could have already been resolved upstream; however, it appears that the route and controller exist in both.

Comment 3 Stephen Benjamin 2014-07-07 13:58:41 UTC
Created redmine issue http://projects.theforeman.org/issues/6512 from this bug

Comment 4 Stephen Benjamin 2014-07-07 14:18:19 UTC
Upstream PR - https://github.com/Katello/katello/pull/4393

Comment 5 Bryan Kearney 2014-07-14 14:03:10 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/6512 has been closed
-------------
Stephen Benjamin
PR https://github.com/Katello/katello/pull/4393
-------------
Anonymous
Applied in changeset commit:katello|ebdae5d2092c044e1e1add8fc2f5d0769c226f5d.

Comment 7 Brad Buckingham 2014-07-16 18:38:33 UTC
*** Bug 1105659 has been marked as a duplicate of this bug. ***

Comment 8 sthirugn@redhat.com 2014-09-03 19:52:30 UTC
Verified.

Version Tested:
GA Snap 7 - Satellite-6.0.4-RHEL-6-20140829.0

* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.23-1.el6_5.noarch
* candlepin-common-1.0.1-1.el6_5.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.9.23-1.el6_5.noarch
* candlepin-tomcat6-0.9.23-1.el6_5.noarch
* elasticsearch-0.90.10-6.el6sat.noarch
* foreman-1.6.0.42-1.el6sat.noarch
* foreman-compute-1.6.0.42-1.el6sat.noarch
* foreman-gce-1.6.0.42-1.el6sat.noarch
* foreman-libvirt-1.6.0.42-1.el6sat.noarch
* foreman-ovirt-1.6.0.42-1.el6sat.noarch
* foreman-postgresql-1.6.0.42-1.el6sat.noarch
* foreman-proxy-1.6.0.30-1.el6sat.noarch
* foreman-selinux-1.6.0.14-1.el6sat.noarch
* foreman-vmware-1.6.0.42-1.el6sat.noarch
* katello-1.5.0-30.el6sat.noarch
* katello-ca-1.0-1.noarch
* katello-certs-tools-1.5.6-1.el6sat.noarch
* katello-installer-0.0.62-1.el6sat.noarch
* openldap-2.4.23-34.el6_5.1.x86_64
* openldap-devel-2.4.23-34.el6_5.1.x86_64
* pulp-katello-0.3-4.el6sat.noarch
* pulp-nodes-common-2.4.1-0.5.rc1.el6sat.noarch
* pulp-nodes-parent-2.4.1-0.5.rc1.el6sat.noarch
* pulp-puppet-plugins-2.4.1-0.5.rc1.el6sat.noarch
* pulp-puppet-tools-2.4.1-0.5.rc1.el6sat.noarch
* pulp-rpm-plugins-2.4.1-0.5.rc1.el6sat.noarch
* pulp-selinux-2.4.1-0.5.rc1.el6sat.noarch
* pulp-server-2.4.1-0.5.rc1.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
* ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch

Comment 9 Bryan Kearney 2014-09-11 12:23:19 UTC
This was delivered with Satellite 6.0 which was released on 10 September 2014.


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