Bug 1325935

Summary: Installing large amount of errata through REX throws error
Product: Red Hat Satellite Reporter: Maxim Burgerhout <mburgerh>
Component: Remote ExecutionAssignee: Ivan Necas <inecas>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.2.0CC: bkearney, daniele, inecas, mmccune, oprazak, pierre-yves.goubet, skielek, will_darton, zhunting
Target Milestone: UnspecifiedKeywords: PrioBumpField, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-21 17:40:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
wget http:/tfm-rubygem-foreman_remote_execution-0.3.0.12-2.hotfix.1325935.el7sat.noarch.rpm
none
hotfix for 6.2.4 none

Description Maxim Burgerhout 2016-04-11 12:53:31 UTC 
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
Comment 1 Bryan Kearney 2016-07-26 18:59:48 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 3 Bryan Kearney 2016-09-23 14:16:34 UTC 
Upstream bug component is Remote Execution
Comment 4 Bryan Kearney 2016-09-26 22:14:38 UTC 
Upstream bug assigned to inecas
Comment 5 Bryan Kearney 2016-09-26 22:14:41 UTC 
Upstream bug assigned to inecas
Comment 6 Zach Huntington-Meath 2016-10-06 19:28:19 UTC 
Created attachment 1208026 [details]
wget http:/tfm-rubygem-foreman_remote_execution-0.3.0.12-2.hotfix.1325935.el7sat.noarch.rpm
Comment 7 Zach Huntington-Meath 2016-10-06 19:29:43 UTC 
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
Comment 8 Will D 2016-10-14 18:52:43 UTC 
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
Comment 9 Bryan Kearney 2016-11-16 21:58:38 UTC 
zach, can you take the testing comments to upstream so that we can get this merged?
Comment 10 Bryan Kearney 2016-11-18 13:09:19 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/15311 has been resolved.
Comment 11 Bryan Kearney 2016-11-21 17:40:31 UTC 
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 ***
Comment 12 Ondřej Pražák 2016-12-07 15:03:09 UTC 
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.
Comment 13 Red Hat Bugzilla 2023-09-14 03:20:55 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days