Bug 1208678
| Summary: | 414 Request URI too long when attempting to perform an incremental update on a large amount of errata | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Walden Raines <walden> | ||||
| Component: | Content Management | Assignee: | Walden Raines <walden> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Tazim Kolhar <tkolhar> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | Nightly | CC: | bkearney, cwelton, tkolhar | ||||
| Target Milestone: | Unspecified | ||||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://projects.theforeman.org/issues/10011 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-08-12 13:58:02 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1217828 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Walden Raines
2015-04-02 20:12:47 UTC
Created from redmine issue http://projects.theforeman.org/issues/10011 Upstream bug assigned to walden Moving to POST since upstream bug http://projects.theforeman.org/issues/10011 has been closed ------------- Walden Raines Applied in changeset commit:katello|9b270778a439882b07ade7c9ba55de211295f648. 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 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 Created attachment 1024197 [details]
errata apply
(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. 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 This bug is slated to be released with Satellite 6.1. This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015. |