Description of problem: There is no 'name' attribute under scheduling policy object, when trying to add cluster, only scheduling-policy-policy, which is not compatible with other APIs Version-Release number of selected component (if applicable): rhevm-cli-3.5.0.6-1.el6ev.noarch rhevm-cli-3.6.0.0-1.el6ev.noarch (this bug should be cloned to 3.6 as well) How reproducible: 100% Steps to Reproduce: 1.Add cluster in CLI with auto-completion options 2. 3. Actual results: scheduling-policy-policy exists, but incompatible with other APIs Expected results: scheduling-policy-name should exist Additional info: existing options under cluster: 'comment', 'ha_reservation', 'scheduling_policy-thresholds-duration', 'memory_policy-overcommit-percent', 'version-minor', 'data_center-id', 'scheduling_policy-id', 'correlation_id', 'expect', 'parent-datacenter-name', 'scheduling_policy-properties-property', 'fencing_policy-enabled', 'version-major', 'scheduling_policy-policy', 'scheduling_policy-thresholds-high', 'ksm-enabled', 'fencing_policy-skip_if_connectivity_broken-enabled', 'fencing_policy-skip_if_sd_active-enabled', 'ballooning_enabled', 'tunnel_migration', 'management_network-id', 'data_center-name', 'threads_as_cores', 'description', 'memory_policy-transparent_hugepages-enabled', 'display-proxy', 'gluster_service', 'parent-datacenter-identifier', 'management_network-name', 'fencing_policy-skip_if_connectivity_broken-threshold', 'error_handling-on_error', 'scheduling_policy-thresholds-low', 'name', 'cpu-id', 'maintenance_reason_required', 'virt_service', 'cpu-architecture', 'trusted_service', 'ksm-merge_across_nodes'
Juan, is that infra or sla?
Initially it is infra. All CLI issues are infra as no other team takes care of the CLI. Note however that in this particular case this will probably be caused by an incorrect description of the cluster "add" operation in the RSDL metadata. In that case the fix will require a change in the engine, and then a regeneration of the Python SDK, as the CLI extracts this information from the Python SDK. This means that eventually this bug will be moved or cloned to the RestAPI component. That moved or cloned bug will then be "sla".
In order to fix this we need to change the RestAPI RSDL metadata. Then the Python SDK will need to be regenerated. The CLI doesn't need any change.
When can I expect to get a fix?
Verified with: ovirt-engine-cli-3.6.2.1-0.1.20160111.git696d8ea.el6.noarch ovirt-engine-sdk-python-3.6.3.1-0.1.20160211.git13845c8.el6.noarch [oVirt shell (connected)]# add cluster --scheduling_policy-name Autocomplete is now working for scheduling_policy-name