User story #3850
closed
Upgrading rudder-agent from the server
Added by Dennis Cabooter over 11 years ago.
Updated 7 months ago.
Category:
Web - Compliance & node report
Description
For now I upgrade all the rudder-agent manually. However, there's no easy way to see which are already done and which aren't. And even if I could search for a list of nodes that have rudder-agent x.y.z, instead of looking in the software list of each node, the inventory is only uploaded once a day (if not forced).
Proposal:
- It would be nice if there's an option under rudder/secure/utilities to upgrade rudder-agent on the nodes.
it would be nice if there's an option under rudder/secure/utilities to force the nodes to send an inventory.It would be nice if there's an option under rudder/secure/nodeManager/searchNode to search nodes based on a certain version of certain software
- Priority changed from N/A to 4
That would be a nice addition indeed.
Note that you can do a search to see which machines have a specific version of the agent, searching for software - name = rudder-agent AND software - version = 2.6.1-squeeze0 (or whichever version you want to check).
Can't you use the "package management for RHEL / CentOS / SuSE / RPM systems" (or DPKG equivalent) feature by setting the package name to rudder-agent and version to 2.7.1.release-1.EL.6 or similar? (Apologies if this won't work, I'm new to Rudder)
We're still thinking about this and would like to find a reliable way to perform all agent upgrades.
My understanding is that there's two scenarios:
- Upgrade rudder-agent before upgrading rudder-server (example: upgrade to CFengine 3.5 in Rudder 2.8)
- Upgrade rudder-agent after upgrading rudder-server
I found related task #2153 regarding a locally hosted yum/apt repo on the Rudder server which could be used as part of this, but we would still need a tool to actually install the updates.
Do you think it's feasible to release these features sometime in the near future?
Are there any recommended methods for installing updates currently? I assume everyone's doing it in a slightly different way - some automated via cron (after pushing the new repo into yum.repos.d via Rudder), some manually, some in other ways.
To be honest, i use rudder to update itself to the latest repo version - i manage my local repo - and it goes pretty well most of the time.
- Category set to Web - Compliance & node report
- Target version set to Ideas (not version specific)
- Description updated (diff)
- First point is not handled yet.
- Second point: and upgrade of rudder agent automatically sends a new inventory
- Third point: this is currently possible
- Description updated (diff)
- Subject changed from Upgrading rudder-agent to Upgrading rudder-agent from the server
- Status changed from New to Resolved
- Regression set to No
I'm closing it, that story is now well covered with update campaign and other dedicated techniques.
The last part ("update rudder-agent") is not done, but we won't do it in the forseable future (or based on sponsoring).
Also available in: Atom
PDF
Updated by Matthieu CERDA 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by