Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1208678 - 414 Request URI too long when attempting to perform an incremental update on a large amount of errata
Summary: 414 Request URI too long when attempting to perform an incremental update on ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Walden Raines
QA Contact: Tazim Kolhar
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On: 1217828
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-02 20:12 UTC by Walden Raines
Modified: 2017-02-23 20:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 13:58:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
errata apply (63.63 KB, image/png)
2015-05-11 11:24 UTC, Tazim Kolhar 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 10011 0 Normal Closed 414 Request URI too long when attempting to perform an incremental update on a large amount of errata 2020-09-14 22:29:41 UTC

Description Walden Raines 2015-04-02 20:12:47 UTC 
If you scroll down so you have > 20 errata and then attempt to select all and apply you will get a 414 when attempting to apply.

Steps to Reproduce

1. Ensure you have content hosts with applicable errata
2. Go to the errata page
3. Scroll down (I only needed to scroll down one set, i.e. 40 results with my hostname)
4. Click select all
5. Click apply
6. Note 414
Comment 1 Walden Raines 2015-04-02 20:12:48 UTC 
Created from redmine issue http://projects.theforeman.org/issues/10011
Comment 2 Walden Raines 2015-04-02 20:12:50 UTC 
Upstream bug assigned to walden
Comment 4 Walden Raines 2015-04-02 20:19:59 UTC 
PR: https://github.com/Katello/katello/pull/5165
Comment 5 Bryan Kearney 2015-04-07 16:05:57 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/10011 has been closed
-------------
Walden Raines
Applied in changeset commit:katello|9b270778a439882b07ade7c9ba55de211295f648.
Comment 7 Tazim Kolhar 2015-05-04 08:48:58 UTC 
Hi

Even after registering the content host 
we are unable to subscribe from satellite6 .
we are not able install any packages coming from satellite 6
hence,need to wait until the bz 1217828 is fixed 
thanks
Comment 8 Tazim Kolhar 2015-05-11 11:23:48 UTC 
FAILEDQA:
# rpm -qa | grep foreman
ruby193-rubygem-foreman_docker-1.2.0.11-1.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.11-1.el7sat.noarch
foreman-proxy-1.7.2.4-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch
foreman-1.7.2.19-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.13-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch
foreman-libvirt-1.7.2.19-1.el7sat.noarch
foreman-postgresql-1.7.2.19-1.el7sat.noarch
ibm-hs22-05.rhts.eng.brq.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-debug-1.7.2.19-1.el7sat.noarch
foreman-compute-1.7.2.19-1.el7sat.noarch
foreman-vmware-1.7.2.19-1.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch
foreman-ovirt-1.7.2.19-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.5-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.9-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
ibm-hs22-05.rhts.eng.brq.redhat.com-foreman-client-1.0-1.noarch
ibm-hs22-05.rhts.eng.brq.redhat.com-foreman-proxy-1.0-2.noarch
foreman-gce-1.7.2.19-1.el7sat.noarch


steps:
1. Ensure you have content hosts with applicable errata
2. Go to the errata page
3. Scroll down (I only needed to scroll down one set, i.e. 40 results with my hostname)
4. Click select all
5. Click apply
6. Note 414

After applying all errata the tasks goes to pending state
screenshot attached
Comment 9 Tazim Kolhar 2015-05-11 11:24:49 UTC 
Created attachment 1024197 [details]
errata apply
Comment 10 Walden Raines 2015-05-11 19:25:22 UTC 
(In reply to Tazim Kolhar from comment #8)
> After applying all errata the tasks goes to pending state
> screenshot attached

This is unrelated to this particular bug fix as this bug occurred the "select content hosts" page and not on the errata confirmation page or afterwards.  In fact you wouldn't be able to get to the page in the screenshot if this bug was not fixes.
Comment 11 Tazim Kolhar 2015-05-12 08:40:06 UTC 
VERIFIED :

# rpm -qa | grep foreman
ruby193-rubygem-foreman_docker-1.2.0.11-1.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.11-1.el7sat.noarch
foreman-1.7.2.19-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.13-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
ibm-x3655-02.ovirt.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch
foreman-debug-1.7.2.19-1.el7sat.noarch
foreman-compute-1.7.2.19-1.el7sat.noarch
foreman-vmware-1.7.2.19-1.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch
foreman-libvirt-1.7.2.19-1.el7sat.noarch
ibm-x3655-02.ovirt.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-ovirt-1.7.2.19-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.5-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.9-1.el7sat.noarch
foreman-postgresql-1.7.2.19-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
foreman-gce-1.7.2.19-1.el7sat.noarch
foreman-proxy-1.7.2.4-1.el7sat.noarch
ibm-x3655-02.ovirt.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch


steps
1. Ensure you have content hosts with applicable errata
2. Go to the errata page
3. Scroll down (I only needed to scroll down one set, i.e. 40 results with my hostname)
4. Click select all
5. Click apply
Comment 12 Bryan Kearney 2015-08-11 13:23:11 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 13 Bryan Kearney 2015-08-12 13:58:02 UTC 
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.
Note You need to log in before you can comment on or make changes to this bug.