Project

General

Profile

Actions

Bug #11372

closed

Techniques tests are all failing

Added by Nicolas CHARLES about 7 years ago. Updated over 6 years ago.

Status:
Released
Priority:
N/A
Category:
Rudder tests
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
19
Name check:
Fix check:
Regression:

Description

I get following error when running every tests:

Initialise test
  Command "RUDDER_VERSION=4.1 /tmp/init_technique" 
    exit_status
      should eq 0
      time: 2.271178098s
    stdout
      should not match /error/i (FAILED - 1)
      time: 0.010764656s

Failures:

  1) Initialise test Command "RUDDER_VERSION=4.1 /tmp/init_technique" stdout should not match /error/i
     On host `centos7_agent1'
     Failure/Error: its(:stdout) { should_not match /error/i }
       expected "    info: Created file '/var/rudder/cfengine-community/state/rudder_expected_reports.25129.csv.tmp',...d, made a change: Insert content { \"key1\": \"test4\", \"key2\": \"is ok\"} into /tmp/json4.json\n" not to match /error/i
       Diff:
       @@ -1,2 +1,10 @@
       -/error/i
       +    info: Created file '/var/rudder/cfengine-community/state/rudder_expected_reports.25129.csv.tmp', mode 0600
       +   error: Unable to open template file '/var/rudder/cfengine-community/inputs/rudder_expected_reports.csv' to make '/var/rudder/cfengine-community/state/rudder_expected_reports.25129.csv.tmp'
       +    info: Method '_create_current_expected_reports_file' aborted in some repairs
       +    info: Method 'log_rudder' aborted in some repairs
       +    info: Method '_log' aborted in some repairs
       +    info: Method 'file_remove' aborted in some repairs
       +    info: Created file '/tmp/json4.json', mode 0600
       +    info: Edit file '/tmp/json4.json'
       +R: [INFO] Promise repaired, made a change: Insert content { "key1": "test4", "key2": "is ok"} into /tmp/json4.json

     # ./spec/tests/techniques/technique_init.rb:13:in `block (3 levels) in <top (required)>'

Finished in 2.28 seconds (files took 6.83 seconds to load)
2 examples, 1 failure

Failed examples:

rspec ./spec/tests/techniques/technique_init.rb:13 # Initialise test Command "RUDDER_VERSION=4.1 /tmp/init_technique" stdout should not match /error/i

EXECUTING TEST 1
[2017-09-15T11:08:49.433932] End of scenario
Test scenario 'technique' failed on platform 'centos7'

Symptoms:
  • broken policy generation (the path of the technique to test is invalid - it is directly /var/rudder/configuration-repository/techniques/1.0 - so missing mandatory technique name)
  • system techniques are empty (/var/rudder/configuration-repository/techniques/system/common is empty)
Actions #1

Updated by Benoît PECCATTE about 7 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • User visibility set to Infrequent - complex configurations | third party integrations
  • Priority changed from 0 to 22
Actions #2

Updated by Benoît PECCATTE about 7 years ago

  • Priority changed from 22 to 21
Actions #3

Updated by Félix DALLIDET over 6 years ago

  • Priority changed from 21 to 20

Technique scenario should be launch like this:

./rtf scenario technique <platform> techniques/fileDistribution/manageKeyValueFile

If you run it with
./rtf scenario technique <platform> techniques/fileDistribution/manageKeyValueFile --start=1
It will skip the "delete_all" scenario and only erase Rules/Directives with the same names as the ones being tested.

Actions #4

Updated by Félix DALLIDET over 6 years ago

  • Target version set to master
Actions #5

Updated by Félix DALLIDET over 6 years ago

  • Status changed from New to In progress
  • Assignee set to Félix DALLIDET
Actions #6

Updated by Félix DALLIDET over 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Félix DALLIDET to Benoît PECCATTE
  • Pull Request set to https://github.com/Normation/rudder-tests/pull/114
Actions #7

Updated by Félix DALLIDET over 6 years ago

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

Updated by Benoît PECCATTE over 6 years ago

  • Status changed from Pending release to Released
  • Priority changed from 20 to 19
Actions

Also available in: Atom PDF