## # @StorageDomainType: # # An enumeration of Storage Domain types. # # @UNKNOWN: The type is not known # # @NFS: The Storage Domain uses Network File System based storage # # @FCP: The Storage Domain uses FibreChannel based storage # # @ISCSI: The Storage Domain uses iSCSI based storage # # @LOCALFS: The Storage Domain uses storage on the local file system # # @CIFS: The Storage Domain uses CIFS/SMB based storage # # @SHAREDFS: The Storage Domain uses storage from a Linux VFS file system # # Since: 4.10.0 # XXX: Need to specify explicit int values for the enum ## {'enum': 'StorageDomainType', 'data': ['UNKNOWN', 'NFS', 'FCP', 'ISCSI', 'LOCALFS', 'CIFS', 'SHAREDFS']} This is missing GLUSTERFS which is referenced in the code with an int constant of value 7, so it should be enumerated after SHAREDFS.
Fred, as you're the QA contact, please work with Nir on this issue.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high
Sandro, what is the impact of this issue on HE on gluster?
(In reply to Yaniv Dary from comment #4) > Sandro, what is the impact of this issue on HE on gluster? If I've understood correctly, this API schema affects JSON-RPC only. Hosted Engine is using XML-RPC since no JSON-RPC client is available so 3.6 shouldn't be affected by this.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
Hi Sandro, Where can I find the info you mentioned in the description?
Patch was not backported to 4.1 on time and did not make it to beta
It was in ./vdsm/rpc/vdsmapi-schema.json but the file doesn't exist anymore on master branch since 2 years passed before fixing this issue. You can still see that file in 3.6 branch.