-
Notifications
You must be signed in to change notification settings - Fork 39
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
Refs #21873 - Switch warn to fail #189
Conversation
QE would like the installer to exit out upon trying to create a proxy with the same name as the Katello box. |
I looked at the output that failed verification and I did not see the warning appear in the output at all. Does this fail guarantee it appears? I tend to be hesitant to pull in a full hard stop fail when a warning was requested. Fails like this provide no way for a user to ever perform the action where they match (perhaps they have good reason?). This is not me nack-ing this, but rather wanting to step back and ask why the warning does not appear. |
An invisible warning that was ignored anyway was my worry in #186 (review) as well so hard failures do make sense to me. |
@ehelms before the fix it would not show it and let it run, the only time you would see the warning would be with the -v option like so: Before fix:
With fix
From how I have seen customers use the product in support I see this as a failsafe to prevent customers from creating issues for themselves down the road. Also if they want to create a capsule/foreman-proxy with the same name and change the sat/katello to a different name then they can use sat-clone and then create new certs correctly. Also if need be we can create a KCS article on how to bypass this if needed since changing this does not require puppet parser to be installed as I was able to see the changes just by editing the .pp file. |
manifests/foreman_proxy_content.pp
Outdated
@@ -24,7 +24,7 @@ | |||
validate_present($foreman_proxy_fqdn) | |||
|
|||
if $foreman_proxy_fqdn == $::fqdn { | |||
warning('The hostname is the same as the foreman-proxy') | |||
fail('The hostname is the same as the foreman-proxy') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd consider one slight modification to the wording -- The hostname is the same as the provided hostname for the foreman-proxy
@ehelms updated the wording |
No description provided.