Bug #14898
Failure when running rake config
Description
rake -- config --key max_trend --value 31 #... rake aborted! NameError: undefined local variable or method `value' for #<ForemanConfig:0x0000001009aac8> /home/vagrant/foreman/lib/tasks/config.rake:160:in `parse_and_set_string' /home/vagrant/foreman/lib/tasks/config.rake:108:in `block in run_key_values' /home/vagrant/foreman/lib/tasks/config.rake:100:in `each' /home/vagrant/foreman/lib/tasks/config.rake:100:in `run_key_values' /home/vagrant/foreman/lib/tasks/config.rake:77:in `run' /home/vagrant/foreman/lib/tasks/config.rake:167:in `block in <top (required)>' /home/vagrant/.rvm/gems/ruby-2.2.4/bin/ruby_executable_hooks:15:in `eval' /home/vagrant/.rvm/gems/ruby-2.2.4/bin/ruby_executable_hooks:15:in `<main>'
Related issues
Associated revisions
History
#1
Updated by The Foreman Bot about 6 years ago
Updated by - Status changed from New to Ready For Testing
- Assignee set to Ondřej Pražák
- Pull request https://github.com/theforeman/foreman/pull/3486 added
#2
Updated by Dominic Cleal about 6 years ago
Updated by - Category set to Settings
- Legacy Backlogs Release (now unused) set to 136
#3
Updated by Dominic Cleal about 6 years ago
- Related to Bug #14843: foreman-rake config should print errors when providing an invalid value added
#4
Updated by Ondřej Pražák about 6 years ago
Updated by - Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 24859f2829d4eb69609291c990833c8178dde74d.
Fixes #14898 - Fix for config task
Removing undefined variable took care of it.