Bug 1648963
| Summary: | Add an upgrade note for 6.4 about host params | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Lukas Zapletal <lzap> |
| Component: | Documentation | Assignee: | Melanie Corr <mcorr> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Sergei Petrosian <spetrosi> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4 | CC: | mcorr |
| Target Milestone: | Unspecified | ||
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-13 09:50:04 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: | |||
Thanks for raising this bug! These changes are now live on the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.4/html/upgrading_and_updating_red_hat_satellite/upgrading_red_hat_satellite#post_upgrade-updating-templates-parameters |
Hey, Satellite 6.4 upgrade process automatically tries to find macros which has been deprecated and convert them into new syntax for all templates, parameters and lookup keys and values. @host.params["parameter1"] -> host_param("parameter1") @host.param_true?("parameter1") -> host_param_true?("parameter1") @host.param_false?("parameter1") -> host_param_false?("parameter1") The process uses simple text replacement which will not work in all cases, e.g. when host is assigned to a variable: myhost = @host myhost.params["wont_work"] After upgrade to 6.4 please verify all templates, parameters and lookup keys and values for the old-syntax and replace manually. The error that can be thrown for old syntax is: undefined method '#params' for Host::Managed::Jail Changing provisioning template to the new syntax helps to avoid the error.