Project

General

Profile

Actions
Copy link

Bug #10845

closed

new content hosts which don't have the katello-agent running yet should not allow actions

Added by Tom Caspy almost 9 years ago. Updated almost 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Katello Recycle Bin
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

package install fails, obviously, but it shouldn't even allow the task to be queued IMHO (requires product manager to make decision)

Actions
Copy link
 #1

Updated by Eric Helms almost 9 years ago

  • Status changed from New to Rejected
  • Triaged changed from No to Yes

There are some ways in which the applications knowledge of the katello-agent status does not necessarily reflect the ability or inability to run package actions. This is unfortunately, in-exact science that should go away with the introduction of remote execution. Therefore I am setting this to rejected. If you feel this should remain open and tracked until said remote execution work is complete, please let us know.

Actions
Copy link
 #2

Updated by Eric Helms almost 8 years ago

  • translation missing: en.field_release set to 166
Actions
Copy link

Also available in: Atom PDF