Description of problem: Install RHEVM with kikstart or with a configuration file, in RHEVM GUI under cluster edit options "Enable Virt Service" & "Enable Gluster Service" are not available. Version-Release number of selected component (if applicable): Red Hat Enterprise Virtualization 3.4 How reproducible: always Steps to Reproduce: 1. Install RHEVM with answer-file # engine-setup --generate-answer=/tmp/answer_file after changing options: # engine-setup --config-append=/tmp/answer_file 2. Go to clusters --> edit cluster Actual results: "Enable Virt Service" & "Enable Gluster Service" not available. Expected results: 3. "Enable Virt Service" & "Enable Gluster Service" should be shown. Additional info: What could be the answer file setting or options to tweak the options in GUI? Tried following but didn't worked: 1_ In answer file: Virt Engine Configuration: Select Gluster, Virt, or Both: Application mode (Both, Virt, Gluster) [Both]: OVESETUP_CONFIG/applicationMode=str:(virt/Gluster/Both) <<===== 2_ From rhevm-shell: [RHEVM shell (connected)]# update cluster Default --virt_service false --gluster_service true [RHEVM shell (connected)]# update cluster Default --virt_service true --gluster_service false both can't be true at the same time. Also it does not show GUI option instead enables that service only.So the second option could be a workaround.
'AllowClusterWithVirtGlusterEnabled' is used to decide whether the user is allowed to create a hybrid(virt+gluster) cluster or not. There is backend validation which checks for this. In this UI, if this option is true 'checkbox' will be shown else 'radiobutton' will be shown. But this doesn't hide the options itself. - ApplicationMode is virt then, both the options will be hidden but assumed virt=true and gluster=false while creating a cluster. - Application mode is gluster then, both the options will be hidden but assumed virt=false and gluster=true while creating a new cluster. - Application mode is Both then, both the options are visible, user can select whatever required while creating a new cluster.
'ApplicationMode' value in the configuration database needs to be changed to 255. This will enable both Virt and Gluster features.
Is there anything to do on gluster side? This seems to be an issue with the value stored for 'ApplicationMode' in vdc_options on upgrade.
Any update on the info requested?
Tal? Sandro? Can you please address comment #9?
Allon, not sure about what happens there. we'll try to reproduce.
Can you please investigate this?
This one is integration.
Simone, please check if setting OVESETUP_CONFIG/applicationMode=str:(virt/Gluster/Both) <<===== reproduce the issue. Looks like an error in the configuration file. Maybe we're missing a validation on this.
It was treating any invalid string like '(virt/Gluster/Both)' as 'virt' without reporting any explicit error or exception. Calling select fn_db_update_config_value('ApplicationMode', '255', 'general') directly on the DB and restarting the engine should be enough to recover a broken deployment.
hi Ulhas, can you provide solution from comment #16 to the customer? On the engine host: . /etc/ovirt-engine/engine.conf.d/10-setup-database.conf PGPASSWORD="${ENGINE_DB_PASSWORD}" psql \ -U ${ENGINE_DB_USER} \ -h "${ENGINE_DB_HOST}" \ -p "${ENGINE_DB_PORT}" \ -d "${ENGINE_DB_DATABASE}" -c "select fn_db_update_config_value('ApplicationMode', '255', 'general')" should solve the issue. On the code side the fix will be available in 3.5.3
Verified with: ovirt-engine-3.6.0-0.0.master.20150412172306.git55ba764.el6.noarch Both options "Enable Virt Service" & "Enable Gluster Service" are available after re-running engine-setup with the already generated answer_file.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0376.html