Project

General

Profile

Actions
Copy link

Bug #5057

closed

generated promises are wrong if a variable is not defined for all values

Added by Vincent MEMBRÉ almost 10 years ago. Updated about 7 years ago.

Status:
Rejected
Priority:
1
Assignee:
Vincent MEMBRÉ
Category:
Web - Config management
Target version:
3.1.19
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

userManagement 3.0 Technique pose a problem as there is some mupltiple variable that can be empty.

Generated promises are not correct

I want to configure 3 users (user1, user2, user3) with user1 and user 3 respectively in group1 and group3 and user2 with default group.

The resulting promises will ok for user1, but user2 will be in group3 and user3 will use default group.

bundle agent check_usergroup_user_parameters
{

  vars:

    "usergroup_user_login[1]" string => "user1";
    "usergroup_user_login[2]" string => "user2";
    "usergroup_user_login[3]" string => "user3";

    "usergroup_user_groupname[1]" string => "group1";
    "usergroup_user_groupname[2]" string => "group3";

It should generate for user3

    "usergroup_user_groupname[3]" string => "group3";

and nothing for user2

This was detected in 2.10 and may affect more than Technique.

Actions
Copy link
 #1

Updated by Jonathan CLARKE almost 10 years ago

  • Target version changed from 2.10.3 to 2.10.4
Actions
Copy link
 #2

Updated by Nicolas CHARLES over 9 years ago

I could reproduce it with the following step:
  1. have several directive based on the same technique applied
  2. change the NAME of the variable (in the metadata.xml)
  3. update technique

the generated promises may be invalid like here

Actions
Copy link
 #3

Updated by Nicolas PERRON over 9 years ago

  • Target version changed from 2.10.4 to 2.6.18
Actions
Copy link
 #4

Updated by Nicolas PERRON over 9 years ago

  • Target version changed from 2.6.18 to 2.10.5
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.5 to 2.10.6
Actions
Copy link
 #6

Updated by Matthieu CERDA over 9 years ago

  • Target version changed from 2.10.6 to 2.10.7
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.7 to 2.10.8
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 9 years ago

  • Target version changed from 2.10.8 to 2.10.9
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.9 to 2.10.10
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.10 to 2.10.11
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.11 to 2.10.12
Actions
Copy link
 #12

Updated by Benoît PECCATTE about 9 years ago

  • Category changed from 14 to Web - Config management
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.12 to 2.10.13
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ about 9 years ago

  • Target version changed from 2.10.13 to 2.10.14
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.14 to 2.10.15
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ almost 9 years ago

  • Target version changed from 2.10.15 to 2.10.16
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.16 to 2.10.17
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.17 to 2.10.18
Actions
Copy link
 #19

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.18 to 2.10.19
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.19 to 2.10.20
Actions
Copy link
 #21

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 2.10.20 to 277
Actions
Copy link
 #22

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 277 to 2.11.18
Actions
Copy link
 #23

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.18 to 2.11.19
Actions
Copy link
 #24

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.19 to 2.11.20
Actions
Copy link
 #25

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 2.11.20 to 2.11.21
Actions
Copy link
 #26

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.21 to 2.11.22
Actions
Copy link
 #27

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.22 to 2.11.23
Actions
Copy link
 #28

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.23 to 2.11.24
Actions
Copy link
 #29

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 2.11.24 to 308
Actions
Copy link
 #30

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 308 to 3.1.14
Actions
Copy link
 #31

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions
Copy link
 #32

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions
Copy link
 #33

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions
Copy link
 #34

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions
Copy link
 #35

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions
Copy link
 #36

Updated by François ARMAND about 7 years ago

  • Status changed from New to Rejected
  • Priority set to 0

This is not the case anymore in last user technique (7.1). Now, the numbers match and for default groups, we have lines like:

    "usergroup_user_groupname[2]" string => "";
Actions
Copy link

Also available in: Atom PDF