Project

General

Profile

Actions

Bug #17690

open

When creating a user technique with restore archive, policy are not correctly regenerated

Added by François ARMAND about 4 years ago. Updated 15 days ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Techniques
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No

Description

I imported an archive composed of a user technique, a corresponding directive and rule. For that, I put files in /var/configuration-repository/, commited them and in rudder utility tab used restore from last git commit.

It worked as expected: my user technique was restored, directive and rule created. But generation was broken ("missing technique for directive XXX") and in directive tree, technique was marked as missing.

Forcing regeneration, reloading technique and clearing cache didn't solved the problem.

Doing a modification in user technique (but not in description, that wasn't enought) make things work again.

=> restoring an archive should force user technique regeneration;
=> reloading technique should do it, too.


Files

import_user_tech.tar.gz (3.02 KB) import_user_tech.tar.gz François ARMAND, 2020-06-17 08:57

Related issues 2 (1 open1 closed)

Related to Rudder - Bug #17862: error when importing techniques and running reload-techniques in 6.1RejectedActions
Related to Rudder - Bug #20520: Error while importing ncf techniques using the restore from latest commit featureNewActions
Actions #1

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.1.0~rc4 to 6.1.0
Actions #2

Updated by Vincent MEMBRÉ about 4 years ago

  • Target version changed from 6.1.0 to 6.1.1
Actions #4

Updated by François ARMAND almost 4 years ago

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

Updated by François ARMAND almost 4 years ago

  • Assignee deleted (François ARMAND)
Actions #6

Updated by François ARMAND almost 4 years ago

Adding the technique/rule/directive that I imported.
Archive contains:

% tar xzf import_user_tech.tar.gz # create configuration-repository
% tree configuration-repository                                                                       [20-06-17 8:58:54]
configuration-repository
├── directives
│   └── ncf_techniques
│       └── Upgrade_rudder_agent
│           ├── a45a7221-9ec1-4e52-9a52-208594db891f.xml
│           └── activeTechniqueSettings.xml
├── rules
│   └── e76a5902-60a9-4eec-8944-3d25dbba56bd.xml
└── techniques
    └── ncf_techniques
        └── Upgrade_rudder_agent
            └── 1.0
                ├── metadata.xml
                ├── rudder_reporting.cf
                ├── technique.cf
                ├── technique.json
                └── technique.ps1
Actions #7

Updated by François ARMAND almost 4 years ago

  • Subject changed from When restoring and archive with user technique, they are not correctly regenerated to When creating a user technique with restore archive, policy are not correctly regenerated
Actions #8

Updated by François ARMAND almost 4 years ago

  • Status changed from In progress to New
Actions #10

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.1.1 to 6.1.2
Actions #11

Updated by Nicolas CHARLES almost 4 years ago

  • Related to Bug #17862: error when importing techniques and running reload-techniques in 6.1 added
Actions #12

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.1.2 to 6.1.3
Actions #13

Updated by François ARMAND almost 4 years ago

  • Target version changed from 6.1.3 to 6.1.4
Actions #14

Updated by Vincent MEMBRÉ almost 4 years ago

  • Target version changed from 6.1.4 to 6.1.5
Actions #15

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.5 to 6.1.6
  • Priority changed from 32 to 31
Actions #16

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.6 to 6.1.7
Actions #17

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.7 to 6.1.8
  • Priority changed from 31 to 30
Actions #18

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.8 to 6.1.9
  • Priority changed from 30 to 29
Actions #19

Updated by Vincent MEMBRÉ over 3 years ago

  • Target version changed from 6.1.9 to 6.1.10
Actions #20

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.10 to 6.1.11
  • Priority changed from 29 to 28
Actions #21

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.11 to 6.1.12
Actions #22

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.12 to 6.1.13
Actions #23

Updated by Vincent MEMBRÉ about 3 years ago

  • Target version changed from 6.1.13 to 6.1.14
  • Priority changed from 28 to 27
Actions #24

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.14 to 6.1.15
Actions #25

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.15 to 6.1.16
Actions #26

Updated by Vincent MEMBRÉ almost 3 years ago

  • Target version changed from 6.1.16 to 6.1.17
Actions #27

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.17 to 6.1.18
Actions #28

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.1.18 to 6.1.19
Actions #29

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.19 to 6.1.20
Actions #30

Updated by Vincent MEMBRÉ about 2 years ago

  • Target version changed from 6.1.20 to 6.1.21
Actions #31

Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions #32

Updated by François ARMAND 7 months ago

  • Target version changed from old 6.1 issues to relocate to 8.0.4
  • Priority changed from 27 to 0
  • Regression set to No

As of 8.0, the situation is at the same time better and worse:

- I tried to import the provided archive as explained,
- I didn't got any error (generation, etc). But the technique is not available at all, the technique editor refuse to display it, and the technique was no translated into a YAML technique

So we have the same root problem I think - technique are not regenerated, so no migration for the json.
But now, we don't even see the technique in editor, so no workaround anymore.
But at least now, generation doesn't break (and I can even delete directive and technique marked as being in error)

Actions #33

Updated by François ARMAND 7 months ago

  • Related to Bug #20520: Error while importing ncf techniques using the restore from latest commit feature added
Actions #34

Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 8.0.4 to 8.0.5
Actions #35

Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 8.0.5 to 8.0.6
Actions #36

Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 8.0.6 to 8.0.7
Actions #37

Updated by Vincent MEMBRÉ 2 months ago

  • Target version changed from 8.0.7 to 8.0.8
Actions #38

Updated by Vincent MEMBRÉ about 2 months ago

  • Target version changed from 8.0.8 to 8.0.9
Actions #39

Updated by Vincent MEMBRÉ 15 days ago

  • Target version changed from 8.0.9 to 8.0.10
Actions

Also available in: Atom PDF