Project

General

Profile

Actions

Bug #31874

open

API uses cluster_id inconsistently

Added by Evgeni Golov over 3 years ago. Updated over 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Ohai,

when hitting /api/compute_resources/:id/available_clusters/:cluster_id/available_networks for different Compute Resources, cluster_id has different meanings, which makes writing a client harder than it should be.

On oVirt/RHV, it's the id from /api/compute_resources/:id/available_clusters, which seems logical.
On VMware, it's the name (or maybe full_path, on all cluster I have access to, those are identical), which is pretty off for my understanding of "ID" :)
On Google, the cluster id is completely ignored.

I only tested this on 2.1, but expect it to be present in other releases too.


Related issues 1 (1 open0 closed)

Related to Foreman - Tracker #27680: API bugs that need workarounds in foreman-ansible-modulesNew

Actions
Actions #1

Updated by Evgeni Golov over 3 years ago

  • Related to Tracker #27680: API bugs that need workarounds in foreman-ansible-modules added
Actions #2

Updated by Evgeni Golov over 3 years ago

  • Description updated (diff)
Actions

Also available in: Atom PDF