Project

General

Profile

Actions
Copy link

Bug #20351

closed

System technique migration fails on old server

Added by Alexis Mousset almost 3 years ago. Updated almost 3 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
Packaging
Target version:
7.0.0~rc2
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:

Description

[2021-12-01 13:13:48+0100] INFO  migration - Check if all Rudder 7.0 system technique are correctly loaded in technique library
[2021-12-01 13:13:50+0100] WARN  com.normation.cfclerk.xmlparsers.VariableSpecParser - Bad tag in variable 'Check interval': since Rudder 4.3, a variable can not be marked as 'UNIQUEVARIABLE' anymore and that attribute will be ignored. In place, you should use a Rudder parameter to denote an unique value, or a Node Property for a value unique for a given node. To denote an action unique to all directive derived from the same technique, you should use pre- or post-agent-run hooks
[2021-12-01 13:13:50+0100] WARN  com.normation.cfclerk.xmlparsers.VariableSpecParser - Bad tag in variable 'Check interval': since Rudder 4.3, a variable can not be marked as 'UNIQUEVARIABLE' anymore and that attribute will be ignored. In place, you should use a Rudder parameter to denote an unique value, or a Node Property for a value unique for a given node. To denote an action unique to all directive derived from the same technique, you should use pre- or post-agent-run hooks
[2021-12-01 13:13:50+0100] WARN  com.normation.cfclerk.xmlparsers.VariableSpecParser - Bad tag in variable 'Check interval': since Rudder 4.3, a variable can not be marked as 'UNIQUEVARIABLE' anymore and that attribute will be ignored. In place, you should use a Rudder parameter to denote an unique value, or a Node Property for a value unique for a given node. To denote an action unique to all directive derived from the same technique, you should use pre- or post-agent-run hooks
[2021-12-01 13:13:50+0100] WARN  com.normation.cfclerk.xmlparsers.VariableSpecParser - Bad tag in variable 'Check interval': since Rudder 4.3, a variable can not be marked as 'UNIQUEVARIABLE' anymore and that attribute will be ignored. In place, you should use a Rudder parameter to denote an unique value, or a Node Property for a value unique for a given node. To denote an action unique to all directive derived from the same technique, you should use pre- or post-agent-run hooks
[2021-12-01 13:13:50+0100] WARN  com.normation.cfclerk.xmlparsers.VariableSpecParser - Bad tag in variable 'Check interval': since Rudder 4.3, a variable can not be marked as 'UNIQUEVARIABLE' anymore and that attribute will be ignored. In place, you should use a Rudder parameter to denote an unique value, or a Node Property for a value unique for a given node. To denote an action unique to all directive derived from the same technique, you should use pre- or post-agent-run hooks
[2021-12-01 13:13:50+0100] WARN  com.normation.cfclerk.xmlparsers.VariableSpecParser - Bad tag in variable 'Check interval': since Rudder 4.3, a variable can not be marked as 'UNIQUEVARIABLE' anymore and that attribute will be ignored. In place, you should use a Rudder parameter to denote an unique value, or a Node Property for a value unique for a given node. To denote an action unique to all directive derived from the same technique, you should use pre- or post-agent-run hooks
[2021-12-01 13:13:50+0100] WARN  com.normation.cfclerk.xmlparsers.VariableSpecParser - Bad tag in variable 'Check interval': since Rudder 4.3, a variable can not be marked as 'UNIQUEVARIABLE' anymore and that attribute will be ignored. In place, you should use a Rudder parameter to denote an unique value, or a Node Property for a value unique for a given node. To denote an action unique to all directive derived from the same technique, you should use pre- or post-agent-run hooks
[2021-12-01 13:13:51+0100] ERROR techniques.reader - Error with technique at path: '/ncf_techniques/1.0/metadata.xml', it will be ignored. Error: Parsing: Not a policy xml, missing 'name' attribute: <TECHNIQUE name="">
  <POLICYGENERATION>separated-with-parameters</POLICYGENERATION>
  <MULTIINSTANCE>true</MULTIINSTANCE>
  <DESCRIPTION/>
  <USEMETHODREPORTING>true</USEMETHODREPORTING>
  <AGENT type="cfengine-community,cfengine-nova">
    <BUNDLES>
      <NAME/>
    </BUNDLES>
    <FILES>
      <FILE name="RUDDER_CONFIGURATION_REPOSITORY/techniques/ncf_techniques//1.0/technique.cf">
        <INCLUDED>true</INCLUDED>
      </FILE>
      <FILE name="RUDDER_CONFIGURATION_REPOSITORY/techniques/ncf_techniques//1.0/resources/dsfgdsg/brightness_290_512.icc">
        <INCLUDED>false</INCLUDED>
        <OUTPATH>/1.0/resources/dsfgdsg/brightness_290_512.icc</OUTPATH>
      </FILE>
    </FILES>
  </AGENT>
  <AGENT type="dsc">
    <BUNDLES>
      <NAME/>
    </BUNDLES>
    <FILES>
      <FILE name="RUDDER_CONFIGURATION_REPOSITORY/techniques/ncf_techniques//1.0/technique.ps1">
        <INCLUDED>true</INCLUDED>
      </FILE>
      <FILE name="RUDDER_CONFIGURATION_REPOSITORY/techniques/ncf_techniques//1.0/resources/dsfgdsg/brightness_290_512.icc">
        <INCLUDED>false</INCLUDED>
        <OUTPATH>/1.0/resources/dsfgdsg/brightness_290_512.icc</OUTPATH>
      </FILE>
    </FILES>
  </AGENT>
  <SECTIONS>
    <SECTION name="File absent" multivalued="true" component="true">
      <REPORTKEYS>
        <VALUE>/tmp/invalid</VALUE>
      </REPORTKEYS>
    </SECTION>
    <SECTION name="Technique parameters">
      <INPUT>
        <NAME>7FF43A76-6DDA-4D3B-BE61-E95D816FEF86</NAME>
        <DESCRIPTION>ttest</DESCRIPTION>
        <LONGDESCRIPTION/>
        <CONSTRAINT>
          <TYPE>textarea</TYPE>
          <MAYBEEMPTY>false</MAYBEEMPTY>
        </CONSTRAINT>
      </INPUT>
    </SECTION>
  </SECTIONS>
</TECHNIQUE>
[2021-12-01 13:13:53+0100] WARN  com.normation.cfclerk.xmlparsers.VariableSpecParser - Bad tag in variable 'Check interval': since Rudder 4.3, a variable can not be marked as 'UNIQUEVARIABLE' anymore and that attribute will be ignored. In place, you should use a Rudder parameter to denote an unique value, or a Node Property for a value unique for a given node. To denote an action unique to all directive derived from the same technique, you should use pre- or post-agent-run hooks
[2021-12-01 13:13:53+0100] WARN  com.normation.cfclerk.xmlparsers.VariableSpecParser - Bad tag in variable 'Check interval': since Rudder 4.3, a variable can not be marked as 'UNIQUEVARIABLE' anymore and that attribute will be ignored. In place, you should use a Rudder parameter to denote an unique value, or a Node Property for a value unique for a given node. To denote an action unique to all directive derived from the same technique, you should use pre- or post-agent-run hooks
[2021-12-01 13:13:53+0100] WARN  com.normation.cfclerk.xmlparsers.VariableSpecParser - Bad tag in variable 'Check interval': since Rudder 4.3, a variable can not be marked as 'UNIQUEVARIABLE' anymore and that attribute will be ignored. In place, you should use a Rudder parameter to denote an unique value, or a Node Property for a value unique for a given node. To denote an action unique to all directive derived from the same technique, you should use pre- or post-agent-run hooks
[2021-12-01 13:13:53+0100] WARN  com.normation.cfclerk.xmlparsers.VariableSpecParser - Bad tag in variable 'Check interval': since Rudder 4.3, a variable can not be marked as 'UNIQUEVARIABLE' anymore and that attribute will be ignored. In place, you should use a Rudder parameter to denote an unique value, or a Node Property for a value unique for a given node. To denote an action unique to all directive derived from the same technique, you should use pre- or post-agent-run hooks
[2021-12-01 13:13:53+0100] WARN  com.normation.cfclerk.xmlparsers.VariableSpecParser - Bad tag in variable 'Check interval': since Rudder 4.3, a variable can not be marked as 'UNIQUEVARIABLE' anymore and that attribute will be ignored. In place, you should use a Rudder parameter to denote an unique value, or a Node Property for a value unique for a given node. To denote an action unique to all directive derived from the same technique, you should use pre- or post-agent-run hooks
[2021-12-01 13:13:53+0100] WARN  com.normation.cfclerk.xmlparsers.VariableSpecParser - Bad tag in variable 'Check interval': since Rudder 4.3, a variable can not be marked as 'UNIQUEVARIABLE' anymore and that attribute will be ignored. In place, you should use a Rudder parameter to denote an unique value, or a Node Property for a value unique for a given node. To denote an action unique to all directive derived from the same technique, you should use pre- or post-agent-run hooks
[2021-12-01 13:13:53+0100] WARN  com.normation.cfclerk.xmlparsers.VariableSpecParser - Bad tag in variable 'Check interval': since Rudder 4.3, a variable can not be marked as 'UNIQUEVARIABLE' anymore and that attribute will be ignored. In place, you should use a Rudder parameter to denote an unique value, or a Node Property for a value unique for a given node. To denote an action unique to all directive derived from the same technique, you should use pre- or post-agent-run hooks
[2021-12-01 13:13:53+0100] ERROR techniques.reader - Error with technique at path: '/ncf_techniques/1.0/metadata.xml', it will be ignored. Error: Parsing: Not a policy xml, missing 'name' attribute: <TECHNIQUE name="">
  <POLICYGENERATION>separated-with-parameters</POLICYGENERATION>
  <MULTIINSTANCE>true</MULTIINSTANCE>
  <DESCRIPTION/>
  <USEMETHODREPORTING>true</USEMETHODREPORTING>
  <AGENT type="cfengine-community,cfengine-nova">
    <BUNDLES>
      <NAME/>
    </BUNDLES>
    <FILES>
      <FILE name="RUDDER_CONFIGURATION_REPOSITORY/techniques/ncf_techniques//1.0/technique.cf">
        <INCLUDED>true</INCLUDED>
      </FILE>
      <FILE name="RUDDER_CONFIGURATION_REPOSITORY/techniques/ncf_techniques//1.0/resources/dsfgdsg/brightness_290_512.icc">
        <INCLUDED>false</INCLUDED>
        <OUTPATH>/1.0/resources/dsfgdsg/brightness_290_512.icc</OUTPATH>
      </FILE>
    </FILES>
  </AGENT>
  <AGENT type="dsc">
    <BUNDLES>
      <NAME/>
    </BUNDLES>
    <FILES>
      <FILE name="RUDDER_CONFIGURATION_REPOSITORY/techniques/ncf_techniques//1.0/technique.ps1">
        <INCLUDED>true</INCLUDED>
      </FILE>
      <FILE name="RUDDER_CONFIGURATION_REPOSITORY/techniques/ncf_techniques//1.0/resources/dsfgdsg/brightness_290_512.icc">
        <INCLUDED>false</INCLUDED>
        <OUTPATH>/1.0/resources/dsfgdsg/brightness_290_512.icc</OUTPATH>
      </FILE>
    </FILES>
  </AGENT>
  <SECTIONS>
    <SECTION name="File absent" multivalued="true" component="true">
      <REPORTKEYS>
        <VALUE>/tmp/invalid</VALUE>
      </REPORTKEYS>
    </SECTION>
    <SECTION name="Technique parameters">
      <INPUT>
        <NAME>7FF43A76-6DDA-4D3B-BE61-E95D816FEF86</NAME>
        <DESCRIPTION>ttest</DESCRIPTION>
        <LONGDESCRIPTION/>
        <CONSTRAINT>
          <TYPE>textarea</TYPE>
          <MAYBEEMPTY>false</MAYBEEMPTY>
        </CONSTRAINT>
      </INPUT>
    </SECTION>
  </SECTIONS>
</TECHNIQUE>
[2021-12-01 13:13:54+0100] INFO  techniques.reader - Reloading technique library, found modified technique(s): ['rudder-service-postgresql': updated (1.0: added)], ['inventory': updated (1.0: updated)], ['server-roles': deleted (1.0)], ['server-common': updated (1.0: added)], ['dnsConfiguration': updated (3.0: updated)], ['rudder-service-relayd': updated (1.0: added)], ['rudder-service-webapp': updated (1.0: added)], ['fileTemplate': updated (1.0: updated)], ['distributePolicy': deleted (1.0)], ['rudder-service-slapd': updated (1.0: added)], ['userManagement': updated (9.0: updated)], ['common': deleted (1.0)], ['clockConfiguration': updated (3.2: updated)], ['downloadFile': updated (4.0: updated)], ['fstabConfiguration': updated (4.0: updated)], ['rudder-service-apache': updated (1.0: added)]
[2021-12-01 13:13:56+0100] INFO  com.normation.rudder.services.policies.TechniqueAcceptationUpdater - Automatically adding technique 'rudder-service-postgresql' in category 'Active techniques used by Rudder (Rudder Internal)' of active techniques library
[2021-12-01 13:13:56+0100] ERROR application - System technique 'server-roles' (1.0)' is deleted ingit base. This will likely cause grave problem. You should investigate.
[2021-12-01 13:13:56+0100] INFO  com.normation.rudder.services.policies.TechniqueAcceptationUpdater - Automatically adding technique 'server-common' in category 'Active techniques used by Rudder (Rudder Internal)' of active techniques library
[2021-12-01 13:13:57+0100] INFO  com.normation.rudder.services.policies.TechniqueAcceptationUpdater - Automatically adding technique 'rudder-service-relayd' in category 'Active techniques used by Rudder (Rudder Internal)' of active techniques library
[2021-12-01 13:13:57+0100] INFO  com.normation.rudder.services.policies.TechniqueAcceptationUpdater - Automatically adding technique 'rudder-service-webapp' in category 'Active techniques used by Rudder (Rudder Internal)' of active techniques library
[2021-12-01 13:13:59+0100] ERROR application - System technique 'distributePolicy' (1.0)' is deleted ingit base. This will likely cause grave problem. You should investigate.
[2021-12-01 13:13:59+0100] INFO  com.normation.rudder.services.policies.TechniqueAcceptationUpdater - Automatically adding technique 'rudder-service-slapd' in category 'Active techniques used by Rudder (Rudder Internal)' of active techniques library
[2021-12-01 13:13:59+0100] ERROR application - System technique 'common' (1.0)' is deleted ingit base. This will likely cause grave problem. You should investigate.
[2021-12-01 13:14:01+0100] INFO  com.normation.rudder.services.policies.TechniqueAcceptationUpdater - Automatically adding technique 'rudder-service-apache' in category 'Active techniques used by Rudder (Rudder Internal)' of active techniques library
[2021-12-01 13:14:02+0100] INFO  com.normation.rudder.services.policies.DeployOnTechniqueCallback - Reload Technique library to allows migration to 7.x system techniques
[2021-12-01 13:14:02+0100] ERROR migration - Error during migration of policy server system configuration to Rudder V7.0 data. It is likely that Rudder won't work as expected. Please check the log above. Error was: Inconsistency: Error when looking for technique with ID 'server-roles/1.0'. Check technique name and version; cause was: Inconsistency: Error when looking for technique with ID 'distributePolicy/1.0'. Check technique name and version; cause was: Inconsistency: Error when looking for technique with ID 'distributePolicy/1.0'. Check technique name and version; cause was: Unexpected: Inconsistency: Error when looking for technique with ID 'distributePolicy/1.0'. Check technique name and version
[2021-12-01 13:14:02+0100] INFO  bootchecks - Check mandatory DIT entries
[2021-12-01 13:14:02+0100] INFO  policy.generation - Start policy generation, checking updated rules
[2021-12-01 13:14:03+0100] ERROR bootchecks - Error when checking for mandatory entries for 'root' server in the DIT. <- Inconsistency: Missing required entry 'directiveId=common-hasPolicyServer-root,activeTechniqueId=common,techniqueCategoryId=Rudder Internal,techniqueCategoryId=Active Techniques,ou=Rudder,cn=rudder-configuration'. This is most likelly because Rudder was not initialized. Please run /opt/rudder/bin/rudder-init to set it up.
[2021-12-01T13:14:03.031+01:00] ERROR FATAL An error happen during Rudder boot. Rudder will stop now. Error: SystemError: An error occured; cause was: javax.servlet.UnavailableException: Error when checking for mandatory entries for 'root' server in the DIT. <- Inconsistency: Missing required entry 'directiveId=common-hasPolicyServer-root,activeTechniqueId=common,techniqueCategoryId=Rudder Internal,techniqueCategoryId=Active Techniques,ou=Rudder,cn=rudder-configuration'. This is most likelly because Rudder was not initialized. Please run /opt/rudder/bin/rudder-init to set it up.
 ->
javax.servlet.UnavailableException: Error when checking for mandatory entries for 'root' server in the DIT. <- Inconsistency: Missing required entry 'directiveId=common-hasPolicyServer-root,activeTechniqueId=common,techniqueCategoryId=Rudder Internal,techniqueCategoryId=Active Techniques,ou=Rudder,cn=rudder-configuration'. This is most likelly because Rudder was not initialized. Please run /opt/rudder/bin/rudder-init to set it up.
    at bootstrap.liftweb.checks.consistency.CheckDIT.FAIL$1(CheckDIT.scala:80)
    at bootstrap.liftweb.checks.consistency.CheckDIT.checks(CheckDIT.scala:165)
    at bootstrap.liftweb.SequentialImmediateBootStrapChecks.$anonfun$checks$1(BootstrapChecks.scala:99)
    at bootstrap.liftweb.SequentialImmediateBootStrapChecks.$anonfun$checks$1$adapted(BootstrapChecks.scala:91)
    at scala.collection.IterableOnceOps.foreach(IterableOnce.scala:563)
    at scala.collection.IterableOnceOps.foreach$(IterableOnce.scala:561)
    at scala.collection.AbstractIterable.foreach(Iterable.scala:919)
    at bootstrap.liftweb.SequentialImmediateBootStrapChecks.checks(BootstrapChecks.scala:91)
    at bootstrap.liftweb.RudderConfig$.$anonfun$init$1(RudderConfig.scala:1388)
    at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.scala:18)
    at zio.internal.FiberContext.evaluateNow(FiberContext.scala:490)

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #20359: techniques are seens as deleted even if there are there in Rudder 7.0ReleasedFrançois ARMANDActions
Actions
Copy link

Also available in: Atom PDF