Project

General

Profile

Actions
Copy link

Bug #23050

closed

new katello-agent 3.5 is flood with the following error

Added by Mario Gamboa about 6 years ago. Updated 8 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Client/Agent
Target version:
Katello Backlog
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Mar 28 17:19:49 control01 goferd: [INFO][worker-0] gofer.messaging.adapter.proton.connection:92 - opened: proton+amqps://katelloproxy01.loc:5647
Mar 28 17:19:49 control01 goferd: [INFO][worker-0] gofer.messaging.adapter.connect:30 - connected: proton+amqps://katelloproxy01.loc:5647
Mar 28 17:19:49 control01 goferd: [ERROR][worker-0] gofer.messaging.adapter.proton.reliability:47 - receiver e8eab152-0e38-41bb-9366-2c3ebbdd8780 from None closed due to: Condition('qd:no-route-to-dest', 'No route to the destination node')

Actions
Copy link
 #1

Updated by Anonymous about 6 years ago

  • Priority changed from High to Normal
  • translation missing: en.field_release deleted (351)

!!! MARIO, STOP SETTING THE RELEASE FIELD WHEN OPENING ISSUES !!!

Actions
Copy link
 #2

Updated by John Mitsch about 6 years ago

  • Category set to Client/Agent
  • translation missing: en.field_release set to 114
Actions
Copy link
 #3

Updated by Ewoud Kohl van Wijngaarden 8 months ago

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

katello-agent is going away.

Actions
Copy link

Also available in: Atom PDF