Bug 1221362

Summary: fusor-installer `sort': comparison of Symbol with String failed (ArgumentError)
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: InstallationAssignee: Martin Bacovsky <mbacovsk>
Status: CLOSED CURRENTRELEASE QA Contact: Tazim Kolhar <tkolhar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.4CC: bkearney, cwelton, jkim, jmatthew, mbacovsk, tkolhar
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/10500
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-12 13:56:03 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:    
Bug Blocks: 1212602    

Description Mike McCune 2015-05-13 20:46:23 UTC
Running fusor-installer fails with the following trace.

We are seeing an issue with kafo from the change introduced with http://projects.theforeman.org/issues/10390

Error seen is:

Starting networking setup
Networking setup has finished
/usr/share/gems/gems/kafo-0.6.5.6/lib/kafo/hooking.rb:47:in `sort': comparison of Symbol with String failed (ArgumentError)
        from /usr/share/gems/gems/kafo-0.6.5.6/lib/kafo/hooking.rb:47:in `execute'
        from /usr/share/gems/gems/kafo-0.6.5.6/lib/kafo/kafo_configure.rb:301:in `run_installation'
        from /usr/share/gems/gems/kafo-0.6.5.6/lib/kafo/kafo_configure.rb:109:in `execute'
        from /usr/share/gems/gems/clamp-0.6.2/lib/clamp/command.rb:67:in `run'
        from /usr/share/gems/gems/clamp-0.6.2/lib/clamp/command.rb:125:in `run'
        from /usr/share/gems/gems/kafo-0.6.5.6/lib/kafo/kafo_configure.rb:116:in `run'
        from /usr/sbin/fusor-installer:55:in `<main>'

Comment 1 Mike McCune 2015-05-13 20:46:24 UTC
Created from redmine issue http://projects.theforeman.org/issues/10500

Comment 5 Bryan Kearney 2015-05-18 08:06:03 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/10500 has been closed

Comment 8 Tazim Kolhar 2015-05-22 05:19:44 UTC
hi

please provide verification steps

thanks

Comment 9 Martin Bacovsky 2015-05-25 08:25:51 UTC
The error occurred only when the names of registered hooks mixed strings and symbols. Hook name as a symbol can get in only with manual hook registration.

To reproduce add 

Kafo::KafoConfigure.hooking.register_boot(:reset_db) do
end

before line with 

Kafo::KafoConfigure.run

in sat6 installer and run the installer. With With Kafo 0.6.8 it should fail with the error above while with the Kafo 0.6.9 it should succeed.

Let me know if you need more details.

Comment 10 Tazim Kolhar 2015-05-26 10:40:33 UTC
VERIFIED:
# rpm -qa  |grep foreman
foreman-1.7.2.24-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.5-1.el7sat.noarch
foreman-libvirt-1.7.2.24-1.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch
hp-sl2x170zg6-02.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch
hp-sl2x170zg6-02.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch
foreman-gce-1.7.2.24-1.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.11-1.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
foreman-ovirt-1.7.2.24-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch
foreman-postgresql-1.7.2.24-1.el7sat.noarch
foreman-debug-1.7.2.24-1.el7sat.noarch
foreman-vmware-1.7.2.24-1.el7sat.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch
rubygem-hammer_cli_foreman_docker-0.0.3.6-1.el7sat.noarch
foreman-proxy-1.7.2.4-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch
hp-sl2x170zg6-02.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch
ruby193-rubygem-foreman_docker-1.2.0.14-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch
foreman-compute-1.7.2.24-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.14-1.el7sat.noarch

steps:
add
Kafo::KafoConfigure.hooking.register_boot(:reset_db) do
end
Kafo::KafoConfigure.run
in sat6 installer and run the installer
installer runs fine

Comment 11 Bryan Kearney 2015-08-11 13:29:49 UTC
This bug is slated to be released with Satellite 6.1.

Comment 12 Bryan Kearney 2015-08-12 13:56:03 UTC
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.