User story #2221: Check which packages are installed frequency - Rudder - Issue Tracker

Custom queries

8.1 beta
Bugs triage
My TR
Need technical review
Open bugs (all)
Open bugs (UI - UX)
Open UX defects (all)
Opened by users

Actions

Copy link

User story #2221

closed

Check which packages are installed frequency

Added by Jean Remond over 12 years ago. Updated almost 5 years ago.

Status:

Rejected

Priority:

Assignee:

Category:

Techniques

Target version:

Ideas (not version specific)

Pull Request:

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

Fix check:

Regression:

Description

In the case of package installation, 30 minutes is not always the best option.
Is that option easy to be managed through web interface ?

The best solution would be to have one value per package, but first choosing the general value will be a great amelioration.

Related issues 2 (0 open — 2 closed)

	Related to Rudder - User story #8230: Package management issues in Rudder/ncf	Rejected	Alexis Mousset				Actions
	Is duplicate of Rudder - User story #9110: Make the package_module bodies configurable	Released	Nicolas CHARLES				Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Jonathan CLARKE over 12 years ago

Assignee set to Jonathan CLARKE
Priority changed from N/A to 2
Target version set to 2.3.7

Sure, that's easy to add. But I'm not sure why we'd want to set it per package...

The apt_pkg_timeout option in Rudder's PTs is used by the CFEngine option package_list_update_ifelapsed. This controls how often to run "aptitude update" (ie, refresh the lists of packages from apt sources). I don't understand why you would want to set this per package - do you have some packages that are updated on an internal repo very often or something similar?

When you say 30 minutes is not the best option, do you mean you encounter problems while installing some packages? Is this because they take longer than 30 minutes to install? (!)

Just as soon as I know what to do, I'll patch this ASAP ;)

Actions

Copy link

Updated by Jean Remond over 12 years ago

I made a mistake for the role of this value.
I thought it was for verifying/repairing the installed packages and not just to refresh the list of packages.
This question may be closed without further information :-)

The question behind was "how often do you verify if the packages are properly installed ?"
I assume once a day or every 4 hours at most is enough and I do not know how to tell Rudder that (I think it should be another issue).

Actions

Copy link

Updated by Jonathan CLARKE about 12 years ago

Subject changed from Can you let the user choose apt_pkg_timeout ? to Check packages are installed frequency

Jean Remond wrote:

I made a mistake for the role of this value.
I thought it was for verifying/repairing the installed packages and not just to refresh the list of packages.
This question may be closed without further information :-)

The question behind was "how often do you verify if the packages are properly installed ?"
I assume once a day or every 4 hours at most is enough and I do not know how to tell Rudder that (I think it should be another issue).

Whoops, looks like this question got lost... sorry about that.

Currently, we check the installed packages on every CFEngine run, ie every 5 minutes. This is a very fast and efficient process, since CFEngine reads the list of installed packages from dpkg/rpm once, and then just checks all the packages that should be installed in this list.

I guess we could make this configurable quite easily via the web interface.

Actions

Copy link