Description of problem: Currently with 'hosted-engine --set-shared-config' the user could just edit broker related values. Due to other reasons (eg. decommissioning one of the initial gluster hosts, modifying the engine FQDN...), the user should be also able to change values from the initial answer file. Actual results: [root@c72he20170530h1 ~]# hosted-engine --set-shared-config --help Usage: /usr/sbin/hosted-engine --set-shared-config key value [--type=<type>] Set shared storage configuration. Valid types are: broker. Available only after deployment has completed.
Please note this bug is marked as blocker for a bug targeted to 4.1.4 when targeting this bug.
Available keys are: he_conf : ['bridge', 'domainType', 'connectionUUID', 'ca_subject', 'conf', 'vm_disk_id', 'gateway', 'console', 'metadata_image_UUID', 'storage', 'lockspace_volume_UUID', 'port', 'sdUUID', 'iqn', 'metadata_volume_UUID', 'vm_disk_vol_id', 'conf_image_UUID', 'ca_cert', 'conf_volume_UUID', 'portal', 'user', 'host_id', 'password', 'lockspace_image_UUID', 'vmid', 'fqdn', 'vdsm_use_ssl', 'mnt_options', 'spUUID'] broker : ['smtp-port', 'destination-emails', 'smtp-server', 'source-email', 'state_transition'] Getting and setting key values is working without errors, but also without key value verification, i.e. "gateway" key value might be provided with letters, while only numbers should be allowed. Details of test results available here: http://pastebin.test.redhat.com/509814. Tested on ovirt-hosted-engine-setup-2.1.3.6-1.el7ev.noarch, using rhvm-appliance-4.1.20170709.3-1.el7.noarch. I'm moving this bug to verified, while opening another bug on lack of verification for key values.