Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    marson
    @ismenia_gitlab
    I have a issue on rudder server, the status of the policies is going bad with many errors on /var/log/rudder/webapp/2019_10_03.stderrout.log
    the errors are:
    [2019-10-03 10:23:56] ERROR policy.generation - Policy update error for process '122311' at 2019-10-03 10:23:56: Cannot build target configuration node
    the health status is red
    Alexis Mousset
    @amousset
    Do you have more information when clicking on "Details" in the generation menu?
    marson
    @ismenia_gitlab
    I can't get the details now because the status still loading,
    Alexis Mousset
    @amousset
    Could you send us your full /var/log/rudder/webapp/2019_10_03.stderrout.log file? (in private or by email)
    marson
    @ismenia_gitlab
    Error
    Policy update process was stopped due to an error:
    ⇨ Policy update error for process '122314' at 2019-10-03 10:33:51
    ⇨ Cannot build target configuration node
    ⇨ Error while computing Node Configuration for nodes: Error with parameters expansion for node 'sst-p1305979fl.ads.local' (4ab56d2d-46a2-4505-96f6-0f630f64edef): Node sst-p1305979fl.ads.local '4ab56d2d-46a2-4505-96f6-0f630f64edef' get directives with incompatible different policy mode but technique 'servicesManagement/3.0' does not support multi-policy generation. Problematic rules/directives: cfcb4ab0-4990-4dca-a996-6e60b79b21cb / 105a251a-bc4e-455c-878b-081b5c8ac4b0 ; 8693f7cc-0827-4851-9a43-a5d4fcc18e7c / 85ee09df-ba13-41b2-8453-0d510dddbb15; Inconsistant policy mode: both audit and enforce applied ; Error with parameters expansion for node 'rmm-p1188644fl.ads.local' (ae1615c0-386b-422e-ab70-981cf2d542c4): Node rmm-p1188644fl.ads.local 'ae1615c0-386b-422e-ab70-981cf2d542c4' get directives with incompatible different policy mode but technique 'servicesManagement/3.0' does not support multi-policy generation. Problematic rules/directives: cfcb4ab0-4990-4dca-a996-6e60b79b21cb / 105a251a-bc4e-455c-878b-081b5c8ac4b0 ; 8693f7cc-0827-4851-9a43-a5d4fcc18e7c / 85ee09df-ba13-41b2-8453-0d510dddbb15; Inconsistant policy mode: both audit and enforce applied ; Error with parameters expansion for node 'sst-p1309380pl.ads.local' (07b67004-2c8d-413a-8b91-0a9157aefac8): Node sst-p1309380pl.ads.local '07b67004-2c8d-413a-8b91-0a9157aefac8' get directives with incompatible different policy mode but technique 'groupManagement/5.0' does not support multi-policy generation. Problematic rules/directives: cfcb4ab0-4990-4dca-a996-6e60b79b21cb / 7e744382-28a0-4ff9-aecb-481e54f34754 ; 497f862b-f4fd-44f6-93c1-e1b1c5df60a6 / d57337b8-78cd-47bc-90b0-d95c62da61c6; Inconsistant policy mode: both audit and enforce applied ; Error with parameters expansion for node 'sst-p1307285fl.ads.local' (331c0cce-b329-432b-a6aa-0893d8d444df): Node sst-p1307285fl.ads.local '331c0cce-b329-432b-a6aa-0893d8d444df' get directives with incompatible different policy mode but technique 'groupManagement/5.0' does not support multi-policy generation. Problematic rules/directives: cfcb4ab0-4990-4dca-a996-6e60b79b21cb / 7e744382-28a0-4ff9-aecb-481e54f34754 ; 497f862b-f4fd-44f6-93c1-e1b1c5df60a6 / d57337b8-78cd-47bc-90b0-d95c62da61c6; Inconsistant policy mode: both audit and enforce applied ; Error with parameters expansion for node 'rmm-p2000075fl.ads.local' (48c88552-406b-46c8-8c3c-a29a994776ef): Node rmm-p2000075fl.ads.local '48c88552-406b-46c8-8c3c-a29a994776ef' get directives with incompatible different policy mode but technique 'groupManagement/5.0' does not support multi-policy generation. Problematic rules/directives: cfcb4ab0-4990-4dca-a996-6e60b79b21cb / 7e744382-28a0-4ff9-aecb-481e54f34754 ; 497f862b-f4fd-44f6-93c1-e1b1c5df60a6 / d57337b8-78cd-47bc-90b0-d95c62da61c6; Inconsistant policy mode: both audit and enforce applied ; Error with parameters expansion for node 'shz-p0000316fl.ads.local' (c6a965ae-737d-4c8a-81fe-9e7bd1885a12): Node shz-p0000316fl.ads.local 'c6a965ae-737d-4c8a-81fe-9e7bd1885a12' get directives with incompatible different policy mode but technique 'groupManagement/5.0' does not support multi-policy generation. Problematic rules/directives: cfcb4ab0-4990-4dca-a996-6e60b79b21cb / 7e744382-28a0-4ff9-aecb-481e54f34754 ; 497f862b-f4fd-44f6-93c1-e1b1c5df60a6 / d57337b8-78cd-47bc-90b0-d95c62da61c6; Inconsistant policy mode: both audit and enforce applied ; Error with parameters expansion for node 'rmm-p2000143fl.ads.local' (588ee994-b993-4152-a38e-14231543f5a1): Node rmm-p2000143fl.ads.local '588ee994-b993-4152-a38e-14231543f5a1' get directives with incompatible different policy mode but technique 'servicesManagement/3.0' does not support multi-policy generation. Problematic rules/directives: cfcb4ab0-4990-4dca-a996-6e60b79b21cb / 105a251a-bc4e-455c-878b-081b5c8ac4b0 ; 8693f7cc-0827-4851-9a43-a5d4fcc18e7c / 85ee09df-ba13-41b2-8453-0d510dddbb15; Inconsistant policy mode: both audit and enfor
    there is the contains of details
    Alexis Mousset
    @amousset
    The is the different policy modes applied on the same directive to the same node. Older techniques versions do not support this, and all directives from the same technique on a node need to use the same policy mode.
    you can upgrade your group management directives to 5.1 which supports mixed policy modes.
    Alexis Mousset
    @amousset
    the service management technique has no new versions supporting mixed modes, but you could use the new "services technique" which is simpler and supports mixed policy modes.
    marson
    @ismenia_gitlab
    Why before it'working?
    Alexis Mousset
    @amousset
    because you didn't have mixed policy modes on the same node and directive. You probably switched the policy mode of two directives based on these techniques.
    marson
    @ismenia_gitlab
    my techniques are in version 1.0
    and there are all in enforce mode
    Alexis Mousset
    @amousset
    If you go in your directives tree, in "group management", you should have different policy modes on the directives
    techniques from the technique editor are indeed all 1.0, but built-in techniques have different versions.
    marson
    @ismenia_gitlab
    In Directive Tree I have only: Application management
    Distributing files
    File state configuration
    Job scheduling
    System settings
    User Techniques
    I don't have group management
    i'm on Rudder 5.0.12 version
    Alexis Mousset
    @amousset
    group management is in System settings, which is a technique category and not a technique itself
    marson
    @ismenia_gitlab
    I have in System Settings : the folder "User Management" and "groups"
    is that?
    Alexis Mousset
    @amousset
    Indeed, the technique is called "Groups"
    marson
    @ismenia_gitlab
    yes is that
    in groups technique, i have 2 directives in enforce and 1 in Audit
    But no mixed directives
    Alexis Mousset
    @amousset
    By mixed directives I meant several directives in different modes
    marson
    @ismenia_gitlab
    So I have to upgrade this 3 directives in 5.1?
    Alexis Mousset
    @amousset
    Yes (or set the same policy mode for all of them)
    marson
    @ismenia_gitlab
    after upgrading, the status is still red
    Vincent Membré
    @VinceMacBuche
    You still need to manage service technique too
    Alexis Mousset
    @amousset
    Yes, because you also have problems with the services technique
    marson
    @ismenia_gitlab
    I have no directives in "Services technique"
    Alexis Mousset
    @amousset
    But this case is a bit more complicated, since we do not provide a new version able to mix policy modes
    The problem is in the "Services" technique, and you would need to migrate to "Services technique" technique (very badly named, I'm opening a ticket to improve this)
    marson
    @ismenia_gitlab
    In "Service" i have 3 directives in Enforce and 1 in Audit
    and there are in version 3 (is the last version available)
    Vincent Membré
    @VinceMacBuche
    You need to recreate the 4 directive from "Services" in "Services technique"
    Alexis Mousset
    @amousset
    Yes, but we provide no compatible versions. If their content is simple (no process management and only standard service state, you should recreate them using the "Services technique" technique
    marson
    @ismenia_gitlab
    ok thank you, the issue is fixed now
    Alexis Mousset
    @amousset
    :+1:
    pablo-qb
    @pablo-qb
    What should I set on condition_prefix while creating a Condition from variable match?
    peckpeck
    @peckpeck
    anything you want
    this is a text that will be used as a prefix in the name of the condition
    for example if you put "mycondition" you will be able to use mycondition_true or mycondition_false as a condition of another generic method
    Rudder Chatbot
    @rudderbot
    mattronix woot back from IRC
    pablo-qb
    @pablo-qb
    Thanks for your reply @peckpeck :)
    Alexandre Brianceau (Rudder team)
    @abrianceau

    This is a message about Configuration Management Camp 2020, THE event about IT automation you can’t miss!!
    We need you!

    We would like so much that some of you submit a talk at this event. The idea is to talk about your experience and your use of RUDDER. If you’re interested, you will find all information via : https://www.rudder.io/en/blog/2019/10/10/call-participation-cfgmgmtcamp-2020/

    Do not hesitate to contact us if you need more information of help!