Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixes #19164 - create feature even if on older rex #251

Merged
merged 1 commit into from Apr 5, 2017

Conversation

stbenjam
Copy link
Member

@stbenjam stbenjam commented Apr 4, 2017

The template references the feature, so it always needs to exist.



if Gem::Version.new(ForemanRemoteExecution::VERSION) >= Gem::Version.new('1.2.3')
options.merge!(:host_action_button => true)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use options[:host_action_button] = true instead of options.merge!(:host_action_button => true).

@stbenjam stbenjam changed the title fixes #19164 - seed feature even if on older rex fixes #19164 - create feature even if on older rex Apr 4, 2017
@ares
Copy link
Member

ares commented Apr 5, 2017

note for myself: we'll need to cherry pick this to 0.6 branch for 1.14

@ares
Copy link
Member

ares commented Apr 5, 2017

Thanks @stbenjam, tested with older version of REX and it works just fine. After updating, the host_action_button is correctly set to true after re-seeding the db. Merging and will do the releases for both 1.14 and 1.15.

@ares ares merged commit ff844e8 into theforeman:master Apr 5, 2017
@stbenjam stbenjam deleted the rex branch April 5, 2017 13:31
@stbenjam
Copy link
Member Author

stbenjam commented Apr 6, 2017

Thanks much! I also found another problem when testing on older Foreman, the smart proxy has a 1.8.7 incompatibility, there's a PR over there theforeman/smart_proxy_openscap#48

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants