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
    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!

    pablo-qb
    @pablo-qb
    Hello, is there any way to do not force UNIX users shell. (Only on account creation) on built-in directive "Users"?
    Fdall
    @Fdall
    @pablo-qb Hi, I do not think it is possible with the current "User" directive
    pablo-qb
    @pablo-qb
    @Fdall Ok, thanks for your reply anyway :)
    Fdall
    @Fdall
    @pablo-qb You should still $be able to mimick the expected behaviour in the technique editor by using a "user_present" generic method followed by a "user_shell" one with a condition like based on the repaired case of the "user_present" one.
    pablo-qb
    @pablo-qb
    That's a good idea @Fdall, I'll try it then, thank you
    Marek Haluska
    @mhaluska
    hey guys, I just updated rudder root server to 5.0.14 (CentOS 7) and now I've "cosmetic" issue. root server is reporting "Unexpected" check for "Check PostgreSQL configuration", anyway I'm running db on different server.
    this is from technical logs:
    2019-10-18 08:45:49 result_na Rudder system policy: Server roles Server Roles Check PostgreSQL configuration - Checking PostgreSQL configuration is unnecessary on this machine, skipping.
    before on 5.0.13 was fine, upgrade process went without issue.
    some idea where to have a look?
    Vincent Membré
    @VinceMacBuche
    Hello Marek! We remove this check in 5.0.14 (https://issues.rudder.io/issues/14296) so you should not have any reporting anymore on this component
    Marek Haluska
    @mhaluska
    Hi Vincent, but it's still visible in GUI reports and still reported by agent
    Vincent Membré
    @VinceMacBuche
    Yes ! I'm looking for a way to have more insight on this
    Marek Haluska
    @mhaluska
    Thank you, anyway as I said, it's only "cosmetic" issue ;-)
    Vincent Membré
    @VinceMacBuche
    Yes not a big issue, but sad to have some red in your compliance for nothing, but what is bothering me is that you should not have this message anymore !! :)
    Marek Haluska
    @mhaluska
    Yeh, maybe remove it from here?
    $ grep -l -R 'Check PostgreSQL configuration' /opt/rudder/
    /opt/rudder/share/techniques/system/server-roles/1.0/component-check.st
    /opt/rudder/share/initial-promises/server-roles/1.0/component-check.cf
    Vincent Membré
    @VinceMacBuche
    Ok was going to ask you to find that file ;)
    Marek Haluska
    @mhaluska
    :-)
    Vincent Membré
    @VinceMacBuche
    We missed some reporting that was one in your case (db on different server)
    I can provide you a fix :)
    Marek Haluska
    @mhaluska
    it would be great, removal from those two files didn't help me
    pablo-qb
    @pablo-qb
    Hey, which client have I to install on a Fedora laptop? The RHEL one?
    Vincent Membré
    @VinceMacBuche
    You still need the files :) just some lines here that needs to be removed
    Marek Haluska
    @mhaluska
    Yeh, I just realized is not good idea leave bck files in same dir... :-)
    Full green now, thanks for hint ;-)
    Vincent Membré
    @VinceMacBuche
    Ok :) faster than I, (but i did not have my coffee yet!!)
    Marek Haluska
    @mhaluska
    I understand, same for me, not usable without morning coffee :-)
    Edzilla2000
    @Edzilla2000
    Hello, I am trying to migrate from a server to another, following this documentation: https://docs.rudder.io/reference/5.0/administration/procedures.html#_migration_backups_and_restores
    except rudder-jetty just won't start, with this error:
    error: Can't stat file '/var/rudder/cfengine-community/inputs/server-roles/1.0/postgres-check.cf' for parsing. (stat: No such file or directory)
    Nicolas Charles
    @ncharles
    Hi
    this is a strange error for rudder-jetty
    isn't it an error from the agent during the generation