Bug #15878
closedchanging websockets values in settings.yaml file does not seem to work
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1267741
Description of problem:
Changing or commenting out the below values from /etc/foreman/settings.yaml file does not seem to have any effect on the conole of the provisioned vm.
- Websockets
:websockets_encrypt: True
:websockets_ssl_key: /etc/pki/katello/private/katello-apache.key
:websockets_ssl_cert: /etc/pki/katello/certs/katello-apache.crt
Once encryption is enabled, it's not possible to disable it via
a) setting ':websockets_encrypt: False' and/or
b) commenting out ':websockets_ssl_key:' and ':websockets_ssl_cert:'
Disabling of vm console encryption seems to only work by changing it via the UI through the Administer->Settings.
Version-Release number of selected component (if applicable):
sat6.1.2
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Unable to disable vm-console encryption via /etc/foreman/settings.yaml file and is only possible via Administer->Settings.
Expected results:
To avoid confusion, we should either,
a) remove the #websockets section from the file /etc/foreman/settings.yaml
and recommend changing it via the Administer->Settings.
or
b) make it work :)
Additional info:
Updated by Dominic Cleal over 7 years ago
- Status changed from New to Need more information
- Assignee deleted (
Ohad Levy)
I can't reproduce this, settings.yaml seems to override it just fine. Please ensure you're using a current version of Foreman with #9603.
Updated by Ondřej Pražák over 7 years ago
Dominic Cleal wrote:
I can't reproduce this, settings.yaml seems to override it just fine. Please ensure you're using a current version of Foreman with #9603.
I can't reproduce either. There were additional comments in BZ, but they seem to be resolved as well. I think we can close this.
Updated by Dominic Cleal over 7 years ago
- Status changed from Need more information to Rejected