Project

General

Profile

Actions

Enhancement #19803

closed

VM type is missing in group criteria

Added by Alexis Mousset almost 3 years ago. Updated about 1 year ago.

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
UX impact:
It bothers me each time
Suggestion strength:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Name check:
To do
Fix check:
To do
Regression:
No

Description

We display a "VM type" in the interface, but it is not accessible elsewhere. It is useful by groups by VM types for example.

Part of the problem is the naming consistency:

- in API, it is named provider under the machine field:

        "machine": {
          "id": "63a9f0ea-7bb9-8050-796b-649e85481845",
          "type": "Virtual",
          "provider": "qemu",
          "manufacturer": "QEMU" 
        },

- but in group, we only have manufacturer, not VM Type at all.


Files

clipboard-202305111544-wiuxp.png (7.73 KB) clipboard-202305111544-wiuxp.png François ARMAND, 2023-05-11 15:44
Actions #1

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.2.10 to 6.2.11
Actions #2

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.2.11 to 6.2.12
Actions #3

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.2.12 to 6.2.13
Actions #4

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.2.13 to 6.2.14
Actions #5

Updated by Alexis Mousset about 2 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • UX impact set to I bothers me each time
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 28
Actions #6

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.2.14 to 6.2.15
Actions #7

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.2.15 to 6.2.16
Actions #8

Updated by Alexis Mousset almost 2 years ago

  • Target version changed from 6.2.16 to 6.2.17
  • Priority changed from 28 to 27
Actions #9

Updated by Nicolas CHARLES almost 2 years ago

  • UX impact changed from I bothers me each time to It bothers me each time
  • Priority changed from 27 to 37
  • Regression set to No
Actions #10

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.2.17 to 997
Actions #11

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 997 to 6.2.18
Actions #12

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.2.18 to 6.2.19
Actions #13

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.2.19 to 6.2.20
Actions #14

Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 6.2.20 to old 6.2 issues to relocate
Actions #15

Updated by François ARMAND about 1 year ago

  • Tracker changed from Bug to Enhancement
  • Target version changed from old 6.2 issues to relocate to 7.2.7
  • Severity deleted (Minor - inconvenience | misleading | easy workaround)
  • Priority deleted (37)
Actions #16

Updated by François ARMAND about 1 year ago

Actions #17

Updated by François ARMAND about 1 year ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #18

Updated by François ARMAND about 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/4792
Actions #19

Updated by Anonymous about 1 year ago

  • Status changed from Pending technical review to Pending release
Actions #20

Updated by Vincent MEMBRÉ about 1 year ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 7.2.7 and 7.3.2 which were released today.

Actions

Also available in: Atom PDF