User story #5684
closed
Generic method to raise a reinventory
Description
- make a group of hosts containing the package to be updated
- use it in a rule that defines the version to update to / runs the update
A problem is that the rule is generated from the existing inventory info.
This it will take up to 8 hours for the rule to reflect which hosts are already patched.
For cases like this it would be helpful to trigger a -Dforce_inventory on the next run, or only the actual inventory run and upload at the end of the current run.
So, instead of one directive- update package to version X
you would have two: - update package to version X
- push inventory update ifvarclass update_package_to_version_X_repaired
Updated by Matthieu CERDA over 9 years ago
- Status changed from New to 8
- Assignee set to Jonathan CLARKE
- Priority changed from N/A to 5
- Target version set to Ideas (not version specific)
That is a good idea, thanks Florian :)
Giving to JCL for evaluation.
Updated by François ARMAND over 9 years ago
I really like it, to.
On a side note, I was wondering if we could automate the fact that if something related to inventory change due to the application of a rule, we can send back (optionnaly, and I don't know where the option would be configured - globally ? By node ?) an inventory. But it suppose that we know what is worth sending back an inventory (software, env vars, hostname, ip... and certainly, and what rule can change that (install soft, edit file, and a bunch of other). So after that little trip, I think the solution where one can just trigger an inventory when one NEED is more flexible and cover more cases.
Updated by Benoît PECCATTE about 9 years ago
- Project changed from 24 to Rudder
- Category set to Techniques
Updated by Benoît PECCATTE almost 9 years ago
- Assignee deleted (
Jonathan CLARKE)
Updated by Jonathan CLARKE over 8 years ago
- Related to User story #7620: rudder-agent should trigger a new inventory after upgrade added
Updated by Jonathan CLARKE over 8 years ago
This is vaguely related to #7620, which has just been implemented: now after an upgrade rudder-agent will run an inventory. This allows to see the updated agent versions in Rudder's web interface as they are upgraded.
Updated by Alexis Mousset about 8 years ago
Creating /opt/rudder/etc/force_inventory will trigger an inventory at the next run, but a dedicated generic method provided by Rudder could be a good idea.
Updated by Alexis Mousset about 2 years ago
- Subject changed from Technique to raise a reinventory to Generic method to raise a reinventory
- Category changed from Techniques to Generic methods
Updated by Alexis Mousset about 2 years ago
- Target version changed from Ideas (not version specific) to 7.1.0~beta1
Updated by Alexis Mousset about 2 years ago
- Status changed from New to In progress
- Assignee set to Alexis Mousset
Updated by Alexis Mousset about 2 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Félix DALLIDET
- Pull Request set to https://github.com/Normation/ncf/pull/1330
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 7.1.0~beta1 to 7.1.0~beta2
Updated by Alexis Mousset about 2 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset ncf|d966ba836e36910ee982c2518ccfdb99327399c4.
Updated by Vincent MEMBRÉ about 2 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.1.0~beta2 which was released today.