Closed anesterova closed 2 years ago
@anesterova Thank you for reporting. Which command did you try to execute?
hey @nadjaheitmann that was regular hammer -h
@ofedoren Do you know if this is something fixed in hammer-cli-foreman-puppet 0.0.5? I didn't realize it was not packaged until I saw your packaging PR the other day.
@anesterova You could try installing https://yum.theforeman.org/plugins/nightly/el7/x86_64/tfm-rubygem-hammer_cli_foreman_puppet-0.0.5-1.fm3_3.el7.noarch.rpm and see if it fixes your issue.
@anesterova, @nadjaheitmann, I can't reproduce the issue on my setup, but it seems like a fresh installation problem I've already heard about and simple hammer --reload-cache
should fix it. Hopefully after https://github.com/theforeman/hammer-cli-foreman/pull/599 nobody will encounter this error again...
P.S. hammer-cli-foreman-puppet 0.0.5 fixed compatibility with hammer-cli-foreman-discovery plugin, nothing more.
hey @ofedoren i was able to fix by running these commands:
foreman-rake apipie:cache
foreman-rake apipie:cache:index
hammer -r
This issue can be closed, ty!
Fresh installation:
CentOS Linux release 7.9.2009 (Core)
Full stack trace:
Same error using latest gems. Please advise