Red Hat Bugzilla – Bug 1267741
changing websockets values in settings.yaml file does not seem to work
Last modified: 2017-08-01 16:02:28 EDT
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.
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):
Steps to Reproduce:
Unable to disable vm-console encryption via /etc/foreman/settings.yaml file and is only possible via Administer->Settings.
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.
b) make it work :)
In the web UI Administer->Settings we could not change the settings, pop-up says they are set in the settings.yaml file and they are read-only in the GUI.
But upon commenting the websocket settings in settings.yaml and restarting 'katello-service restart', we could update via the GUI.
The idea is to track this issue here and have a straightforward method of enabling and disabling webscoket encryption for the vm's console rather than trying multiple things to achieve it.
Per 6.3 planning, moving out non acked bugs to the backlog
Created redmine issue http://projects.theforeman.org/issues/15878 from this bug
Upstream was not able to re-produce. Moving to ON_QA for verification.
The fix to this bug will be delivered with release 6.3 of Satellite.