Bug #31986
closed
Update puppet port param without override
Added by Ondřej Pražák about 4 years ago.
Updated almost 4 years ago.
Description
Steps to reproduce:
1) import puppet_foreman_scap_client
2) do not set up any policies or make sure port param has override: false
3) run migration that changes port param type from string to integer
4) observe migration failure
Apparently, there are cases where people either import the scap client puppet class without actually setting up any policies or they have a misconfiguration. In those cases, the migration (and upgrades) fail to finish successfully.
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman_openscap/pull/468 added
- Related to Bug #31423: puppet run fails with error parameter 'port' expects a Stdlib::Port = Integer[0, 65535] value, got String added
- Fixed in Releases foreman_openscap 4.2.0 added
- Bugzilla link set to 1935786
- Status changed from Ready For Testing to Closed
- Pull request https://github.com/theforeman/foreman_openscap/pull/469 added
- Pull request https://github.com/theforeman/foreman_openscap/pull/470 added
- Pull request https://github.com/theforeman/foreman_openscap/pull/471 added
Also available in: Atom
PDF