by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    necarnot
    @necarnot
    I have no 7.7 nodes left with an old 6.0.x agent. On a 7.6 node, the upgrade is not working (and the local ymu package command is not listing rudder)
    Alexis Mousset
    @amousset
    Ok, makes more sense. From which version are you trying to upgrade on 18.04?
    Could be because of the new dependencies, do you see new packages when upgrading manually?
    necarnot
    @necarnot
    6.0.6
    yes, I see tons of new packages
    Alexis Mousset
    @amousset
    Ok, passing the --with-new-pkgs option with the package_state_options method should make it work
    Francois Armand
    @fanf
    I would have never ever found that solution
    Alexis Mousset
    @amousset
    (by default apt refuses to upgrade a package if it has new dependencies, it requires a dist-upgrade or specific option)
    necarnot
    @necarnot
    Let me try that (for debian family nodes)
    Alexis Mousset
    @amousset
    You'll need to clear the caches to see the result immediately
    Francois Armand
    @fanf
    necarnot
    @necarnot
    OK. I tried to create a specific directive in which I'm using this option, but so far, even after a cache flush, nothing happened. Is using your patch the only way?
    Francois Armand
    @fanf
    @necarnot patch? You mean like in the screenshot in above PR ?
    image.png
    necarnot
    @necarnot
    No I wasn't using a custom technique, but i was trying to use the packageManagement directive
    Francois Armand
    @fanf
    perhaps the pythons files get resetted at each update, you need to change them on the server
    necarnot
    @necarnot
    I also created another custom technique just like in the screenshot, cleared the cache, and so far, nothing new. Maybe I have to wait the 240 minutes timeout?
    @fanf on the server, what is the location of those python files you're speaking about?
    Francois Armand
    @fanf
    @necarnot sorry, I never remember their place
    but if the custom technique doesn't work either, it seems to be unlikly to be the pb
    Francois Armand
    @fanf
    (i'm trying to reproduce)
    Francois Armand
    @fanf
    image.png
    OK, I reproduce: -^
    Francois Armand
    @fanf
    there must be a pb with the option. I will look to it this night, I need to go now @necarnot
    necarnot
    @necarnot
    @fanf François, you're working too late!
    Francois Armand
    @fanf
    @necarnot I found the problem, but correcting it will be above my expertise
    necarnot
    @necarnot
    According to what you pointed at in the issue tracker, you look very close
    Francois Armand
    @fanf
    yes, but I don't get why adding the option in the python script lead to an error "
    while it works in command line
    and apt+python is a bit too much for me
    necarnot
    @necarnot
    I don't know in what timezone you're living, but for myself, this is a very good track I'll be happy to follow tomorow
    Francois Armand
    @fanf
    :)
    bye, good night!
    Francois Armand
    @fanf
    @necarnot update: a master shell/python (@peckpeck) is starting to believe farming goats in Larzac is an appealing live style
    necarnot
    @necarnot
    @fanf I couldn't agree more
    Nicolas Charles
    @ncharles
    could be that you need a tty?
    the < /dev/null seems to indicate that
    Alexis Mousset
    @amousset
    A simple workaround is to install the new dependencies (jq for 6.0) as part of the Rudder upgrade policy
    necarnot
    @necarnot
    Ohh come on, yet another issue, when trying to add 'jq' in my custom rudder-upgrade dierctive :
    
    Policy update process was stopped due to an error:
    ⇨ Policy update error for process '3815' at 2020-07-09 13:03:45 
    ⇨  Cannot write nodes configuration 
    ⇨  Accumulated: Unexpected: Error when trying to open template 'TechniqueResourceIdByPath(List(techniques, ncf_techniques, sit___upgrade_rudder_agent__debian_like_, 1.0, resources, shared-files),sit-rudder)'. Check that the file exists with a .st extension and is correctly commited in Git, or that the metadata for the technique are corrects. ; Unexpected: Error when trying to open template 'TechniqueResourceIdByPath(List(techniques, ncf_techniques, sit___upgrade_rudder_agent__debian_like_, 1.0, resources, shared-files),sit-rudder)'. Check that the file exists with a .st extension and is correctly commited in Git, or that the metadata for the technique are corrects. ; Unexpected: Error when trying to open template 'TechniqueResourceIdByPath(List(techniques, ncf_techniques, sit___upgrade_rudder_agent__debian_like_, 1.0, resources, shared-files),sit-rudder)'. Check that the file exists with a .st extension and is correctly commited in Git, or that the metadata for the technique are corrects.
    Francois Armand
    @fanf
    that's strange, it seems to search for a resources in shared-files under the technique
    can you share the technique (screenshot ? or export it ?) cc @VinceMacBuche ?
    necarnot
    @necarnot
    last week, you advised me to store the hooks and files I wanted to share from the server into :
    myserver:/var/rudder/configuration-repository/shared-files/my_custom_folder
    This folder is itself a git clone.
    When upgrading, the upgrade script warned me about the fact that this content won't get included in the rudder's git management, that was perfectly correct to me.
    About the error above : when returning into the technique editor, I got a warning about an unsaved config (though there were none) and the 'my_custom_folder' mentioned above.
    I suddenly feel the urge to ask if this place really was the best choice, if it can cause troubles?
    necarnot
    @necarnot
    is there someplace I have to add shared-files/my_custom_folder in a .gitignore?
    Francois Armand
    @fanf
    in any case, I don't understand why the editor is looking for that in that place... We had a problem with (1) resources parth in categories and other about (2) the checks about unsaved/modified parameters in editor. It looks like it is in the same code domain
    I'm not sure how/why git share would impact that
    cc @VinceMacBuche who would perhaps know
    Vincent Membré
    @VinceMacBuche

    techniques resources are different from /var/rudder/configuration-repository/shared-files/my_custom_folder, and you cannot use a git repository as resource from a technique (but from shared files yes)

    Do you have files in /var/rudder/configuration-repository/techniques/ ncf_techniques/sit___upgrade_rudder_agent__debian_like_/1.0/resources/shared-files ?

    Do you have resources defined for technique sit___upgrade_rudder_agent__debian_like_ in the web interface ?