Project

General

Profile

Actions
Copy link

Architecture #3930

closed

Rudder-agent cron file now use check-rudder-agent script (/opt/rudder/bin/check-rudder-agent)

Added by Nicolas PERRON over 11 years ago. Updated about 11 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Matthieu CERDA
Category:
System techniques
Target version:
2.8.0~rc1
Pull Request:
Effort required:
Name check:
Fix check:
Regression:

Description

Since #3925 the rudder-agent cron file should use /opt/rudder/bin/check-rudder-agent instead of having the code directly in the cron file.

The bug #3925 concerned Rudder 2.4 so I guess this ticket should be in 2.4 too.

Subtasks 1 (0 open — 1 closed)

Architecture #3931: Modify the cron file to use /opt/rudder/bin/check-rudder-agentReleasedJonathan CLARKE2013-09-17Actions

Related issues 4 (0 open — 4 closed)

Related to Rudder - User story #3939: Remove temporary rudder-agent-uuid cron fileRejectedJonathan CLARKE2013-09-19Actions
Related to Rudder - User story #3938: Since #3925 the temporary rudder-agent-uuid cron file must be removed by the System TechniquesRejectedNicolas PERRON2013-09-19Actions
Related to Rudder - Bug #9858: When upgrading Rudder, we get mails from cron saying "ok: Rudder agent check ran without errors."ReleasedAlexis MoussetActions
Blocked by Rudder - Bug #3925: /opt/rudder/etc/uuid.hive is removed if the package rudder-agent is upgrade from 2.4.8, 2.6.4, 2.6.5, 2.7.1 or 2.7.2 on SuSE or RHEL/CentOSReleasedNicolas PERRON2013-09-11Actions
Actions
Copy link
 #1

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.4.9 to 2.7.3

Nicolas PERRON wrote:

Since #3925 the rudder-agent cron file should use /opt/rudder/bin/check-rudder-agent instead of having the code directly in the cron file.

The bug #3925 concerned Rudder 2.4 so I guess this ticket should be in 2.4 too.

The rudder-agent cron file exists since 2.6, not 2.4. And it does not seems really necessary, it is more a feature than a bug so it seems logic to be included in 2.7

Actions
Copy link
 #2

Updated by Nicolas PERRON over 11 years ago

  • Status changed from New to 14
Actions
Copy link
 #3

Updated by Jonathan CLARKE over 11 years ago

  • Project changed from 24 to Rudder
  • Category set to System techniques
Actions
Copy link
 #4

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.7.3 to 2.7.4
Actions
Copy link
 #5

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.7.4 to 2.8.0~beta1
Actions
Copy link
 #6

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.8.0~beta1 to 2.8.0~rc1
Actions
Copy link
 #7

Updated by Matthieu CERDA about 11 years ago

  • Status changed from 14 to 12
  • Assignee changed from Nicolas PERRON to Matthieu CERDA
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ about 11 years ago

  • Subject changed from Since #3925 the rudder-agent cron file should be change to use check-rudder-agent script to Rudder-agent cron file now use check-rudder-agent script (/opt/rudder/bin/check-rudder-agent)
Actions
Copy link
 #9

Updated by Matthieu CERDA about 11 years ago

  • Status changed from 12 to Pending release
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ about 11 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.8.0~rc1, which was released on Friday 25/10/2013.
Check out:

Actions
Copy link
 #11

Updated by Nicolas CHARLES almost 8 years ago

  • Related to Bug #9858: When upgrading Rudder, we get mails from cron saying "ok: Rudder agent check ran without errors." added
Actions
Copy link

Also available in: Atom PDF