Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1279159

Summary:	No auto-completion option for scheduling policy name under cluster object
Product:	[oVirt] ovirt-engine	Reporter:	Nelly Credi <ncredi>
Component:	RestAPI	Assignee:	Roy Golan <rgolan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Gonza <grafuls>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	---	CC:	bugs, dfediuck, grafuls, juan.hernandez, mavital, mgoldboi, oourfali
Target Milestone:	ovirt-3.6.3	Keywords:	Automation
Target Release:	3.6.3.2	Flags:	rule-engine: ovirt-3.6.z+ mgoldboi: exception+ mgoldboi: planning_ack+ dfediuck: devel_ack+ mavital: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1279231 1279233 (view as bug list)		Environment:
Last Closed:	2016-03-11 07:24:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1279231, 1279233

Description Nelly Credi 2015-11-08 09:01:27 UTC

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'

Comment 1 Oved Ourfali 2015-11-08 09:08:49 UTC

Juan, is that infra or sla?

Comment 2 Juan Hernández 2015-11-08 18:41:31 UTC

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".

Comment 3 Juan Hernández 2015-11-08 18:58:18 UTC

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.

Comment 4 Nelly Credi 2015-12-28 13:43:25 UTC

When can I expect to get a fix?

Comment 5 Gonza 2016-02-25 10:06:24 UTC

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