by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Francois Armand
    @fanf
    if so, can you try to run /opt/rudder/bin/rudder-upgrade ? Something may have forbidden upgrade to finish correctly
    (on root server)
    if you still get errors after rudder-upgrade execution, can you try to run the workaround in issue description ?
    Francois Armand
    @fanf
    image.png
    special note for @necarnot -^
    necarnot
    @necarnot
    @fanf Hi François and al. I'm very glad to see you released the 6.1.2 today, and kind of sad to see it 2 hours before going on holidays (3 weeks away from you, wonderful team). So I'm not testing it now, but I'm still grateful for your commitment and support. See you in 3 weeks guys.
    marson
    @ismenia_gitlab

    if you still get errors after rudder-upgrade execution, can you try to run the workaround in issue description ?

    Hi @fanf it's not an upgrade but a fresh install with data restauration,

    ok I can try the issue workaround
    Francois Armand
    @fanf
    hum, perhaps the ldap index need to be manually redone after a data restore. We will need to update doc on that
    marson
    @ismenia_gitlab
    hi @fanf the error is fixed after the workaround, thank you
    Alexis Mousset
    @amousset
    :warning: We just found a bug that appeared in Rudder 6.1.2 and breaks technique resources in new techniques or when saving changes to an existing one (the displayed number of resources is always zero and when there are several resources, only one is copied on the target nodes).
    :arrow_right: We are working on a fix that will be released in a 6.1.3 very soon. In the meantime, you should not upgrade to 6.1.2 if you use technique resources.
    Francois Armand
    @fanf
    Bug is now corrected (https://issues.rudder.io/issues/18085), release is building and 6.1.3 should be available tomorrow
    Alexis Mousset
    @amousset
    :arrow_up: Rudder 6.1.3 is now available, with the fixes for the resources bug.
    _ChezW@m_
    @JrmChP_twitter
    Hey guys, can you tell why the latest apt repo stays in 6.0 and not in 6.1 ? https://repository.rudder.io/apt/latest/pool/main/r/rudder-server-root/ Thanks!
    Alexis Mousset
    @amousset
    Hi @JrmChP_twitter very likely a mistake (we usually wait a little bit after .0 release to switch the "lastest" link but 6.1 is ready now!)
    Alexis Mousset
    @amousset
    It's updated to 6.1 now, thanks for reporting!
    _ChezW@m_
    @JrmChP_twitter
    good! thanks!
    AlexanderT
    @ati_ito_twitter
    Hi, how can I check, if a varibale from command is changed and generates a "repaired" state ?
    Alexis Mousset
    @amousset
    Hi @ati_ito_twitter, you mean changed compared to previous agent runs?
    AlexanderT
    @ati_ito_twitter
    yes exactly
    Alexis Mousset
    @amousset
    we have nothing built-in for this, as the agent only applies the provided policy without "memory" of what happened previously. You will need to store the result in a file, and to compare the content of the file with the output of the command at each run
    AlexanderT
    @ati_ito_twitter
    okay, thank you for the information :-)
    AlexanderT
    @ati_ito_twitter
    @amousset I'm trying to compare a Variable from command with the content of a file, and if the contents don't match, I want to write the value stored in the variable to the file. This updated file should be sent somewhere, only if the content in the file got updated by the variable. Is there any way to implement this via rudder?
    Alexis Mousset
    @amousset
    Yes it's possible! What you can do is enforce the content of the file based on the output of the command, and if the repqired condition is defined, trigger file copy
    realitygaps
    @realitygaps
    after adding a new users ssh key and choosing to flush other keys, the ssh key deploys fine but the compliance report says 'missing' on 'flush ssh file' for each user including those that already existed. Is this related to https://issues.rudder.io/issues/16516 ?
    (or is there something I can try to repair this)
    realitygaps
    @realitygaps
    hmm it seems to have fixed itself on some already :)
    so might just resolve on its own
    Fdall
    @Fdall
    Hi @realitygaps you're right, it looks like it is not fixed yet. The issue state that it does not impact the authorized_keys files but only the first reporting when a flush is done.
    realitygaps
    @realitygaps
    ah ok thanks for the info!
    Росен Александров
    @sandikata
    Hello.
    Is rudder-vagrant usable on dedicated server, or just on hypervisor providers ?
    Alexis Mousset
    @amousset
    Hello @sandikata, the agent runs on any server (physical or VM) with one of the compatible OS
    Росен Александров
    @sandikata
    i tried from server installed on proxmox, and it says not compatible provider, use virtualbox, vmware or hyperv
    Alexis Mousset
    @amousset
    where do you see proxmox is not compatible?
    Росен Александров
    @sandikata
    vagrant up
    https://bpa.st/WZWQ
    Alexis Mousset
    @amousset
    oh it's a message from vagrant, which is a way to install a demo platform in VMs, but not linked to agent installation
    If you want to install rudder agent or server on prox;ox you can follow the debian install doc
    Росен Александров
    @sandikata
    can you give me a link for it ?
    Alexis Mousset
    @amousset
    https://docs.rudder.io/reference/6.1/installation/server/debian.html
    _ChezW@m_
    @JrmChP_twitter
    hello, on rudder server / Agent 6.1.3 try to install latest version of zabbix-agent package, but it doesn't work. It keeps the first installed version. I've tried to fully remove package, but my technique is always compliant, without the package installed. 
    E| compliant     Zabbix_agentV5            Package present           zabbix-agent       Presence of package zabbix-agent in latest available version was correct
    i've tried to force apt update , apt-cache policy find my 5.0 version, but 3.4 is always here, or not installed when purged. Any idea to debug that ?
    _ChezW@m_
    @JrmChP_twitter
    alt
    Alexis Mousset
    @amousset
    by default there is a 2 hours cache for available upgrades
    _ChezW@m_
    @JrmChP_twitter
    any way to force it ?
    Alexis Mousset
    @amousset
    you can either change it (by overriding the global rudder property) or clean it manually by removing /var/rudder/cfengine-community/state/packages_*
    a rudder agent resetalso removes this cache
    _ChezW@m_
    @JrmChP_twitter
    ok it works. thanks :)
    Alexis Mousset
    @amousset
    :+1: