Project

General

Profile

Actions
Copy link

Feature #18174

closed

Run katello-tracer-upload after reboot

Added by Sean O'Keeffe over 7 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Sean O'Keeffe
Category:
Client/Agent
Target version:
Katello 3.3.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/Katello/katello-agent/pull/41, https://github.com/Katello/katello-packaging/pull/361
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

We should add a cron to run katello-tracer-upload after a reboot as that will make any already reported Traces invalid

Actions
Copy link
 #1

Updated by The Foreman Bot over 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello-agent/pull/41 added
Actions
Copy link
 #2

Updated by Sean O'Keeffe over 7 years ago

  • Pull request https://github.com/Katello/katello-packaging/pull/361 added
Actions
Copy link
 #3

Updated by Anonymous over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Justin Sherrill over 7 years ago

  • translation missing: en.field_release set to 188
Actions
Copy link
 #5

Updated by Hesham Ahmed about 6 years ago

the cron job on reboot is running before the network comes up in some cases. Maybe a delay should be added to the job to allow for the network to come up. Output from boot log showing cron running before NetworkManager:

Mar 15 09:22:11 juana-egerer.example.org CROND747: (root) CMD (/sbin/katello-tracer-upload > /dev/null 2>&1)
Mar 15 09:22:11 juana-egerer.example.org NetworkManager745: <info> [1521105731.9416] NetworkManager (version 1.8.0-11.el7_4) is starting... (for the first time)

Actions
Copy link
 #6

Updated by Sean O'Keeffe about 6 years ago

Thanks @Hesham!! that's confirms my suspicions https://github.com/Katello/katello-host-tools/pull/50

Actions
Copy link

Also available in: Atom PDF