Description of problem: When trying to install a large amount of errata (35) to a host through content host -> errata -> (select) -> apply selected via remote execution, Satellite throws an error: "Oops, we're sorry but something went wrong ERROR: value too long for type character varying(255)" Version-Release number of selected component (if applicable): SNAP 7.1 How reproducible: Steps to Reproduce: 1. Make sure a host has lots of outstanding errata 2. Go to content host -> errata -> (select the errata) -> apply selected via REX 3. Actual results: Satellite throws the above error Expected results: Errata get installed w/o problems. Additional info: Installing through Katello agent doesn't throw this error
Moving 6.2 bugs out to sat-backlog.
Upstream bug component is Remote Execution
Upstream bug assigned to inecas
Created attachment 1208026 [details] wget http:/tfm-rubygem-foreman_remote_execution-0.3.0.12-2.hotfix.1325935.el7sat.noarch.rpm
HOTFIX INSTRUCTIONS I've produced hotfix packages for the customer's installed version of Satellite (6.2.2 on el7) and tested on a similar Satellite. Rex is working with this hotfix applied. Install instructions: 1) Download the rpm attached to this Bugzilla to your satellite server. 2) Install packages yum localinstall tfm-rubygem-foreman_remote_execution-0.3.0.12-2.hotfix.1325935.el7sat.noarch.rpm 3) Run Database Migration foreman-rake db:migrate 3) Restart services katello-service restart 4) Restart Smart Proxy Dynflow Core systemctl restart smart_proxy_dynflow_core 5) Restart Foreman Proxy systemctl restart foreman-proxy
Been fighting the other CDN / Errata Issues, so I just now finally got a working content view I could test against. But I have validated that I was able to install a large amount of errata against a host using REX # Helper function that exits with a particular message and code. # # Usage: # exit_with_message "Could not do a thing" 2 # function exit_with_message() { echo "${1}, exiting..." exit $2 } # Action yum -y update --advisories=RHSA-2016:2047,RHEA-2016:1982,RHSA-2016:1940,RHBA-2016:1848,RHBA-2016:1834,RHSA-2016:1944,RHSA-2016:1847,RHBA-2016:1835,RHBA-2016:1863,RHBA-2016:1832,RHBA-2016:1833,RHSA-2016:1633,RHSA-2016:1626,RHBA-2016:1503,RHSA-2016:1602,RHBA-2016:0183,RHBA-2016:0206,RHBA-2016:1029,RHSA-2016:0176,RHSA-2016:0532,RHSA-2016:0370,RHBA-2016:1527,RHSA-2016:0428,RHSA-2016:0043,RHSA-2016:1539,RHBA-2016:1522,RHBA-2016:0529,RHSA-2016:0301,RHBA-2016:0526,RHSA-2015:2550,RHSA-2016:1141,RHSA-2015:2617,RHBA-2015:1967,RHSA-2016:0008,RHSA-2016:0064,RHBA-2016:0199,RHSA-2016:0722,RHBA-2016:1444,RHBA-2016:0548,RHSA-2016:1025,RHBA-2016:0002,RHSA-2016:0465,RHSA-2016:1292,RHBA-2016:0178,RHBA-2016:1449,RHBA-2016:1283,RHBA-2015:2543,RHBA-2016:0177,RHSA-2016:0007,RHSA-2016:0612 RETVAL=$? [ $RETVAL -eq 0 ] || exit_with_message "Package action failed" $RETVAL Results: ... Complete! Exit status: 0
zach, can you take the testing comments to upstream so that we can get this merged?
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/15311 has been resolved.
Closing this as a dupe. Even though the other is newer, that one has better release processes on it. *** This bug has been marked as a duplicate of bug 1367606 ***
Created attachment 1229087 [details] hotfix for 6.2.4 I rebuilt the hotfix for 6.2.4, the installation instructions are the same as for the previous version.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days