Project

General

Profile

Actions
Copy link

Bug #11164

closed

rudder agent run displays two versions

Added by Janos Mattyasovszky over 6 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Agent
Target version:
-
Pull Request:
Severity:
Trivial - no functional impact | cosmetic
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
15
Name check:
Fix check:
Regression:

Description

I know it's only cosmetic, but apparently when I failed to cleanly update rudder-agent, and two versions are installed parallel, the agent reports both:

# rudder agent run
Rudder agent 3.1.17.release4.1.5.release (CFEngine Core 3.10.0)
             ^^^^^^^^^^^^^+^^^^^^^^^^^^^

# rpm -q rudder-agent
rudder-agent-3.1.17.release-1.SLES.11
rudder-agent-4.1.5.release-1.SLES.11

Not sure this is something worth handling, but I'll let that up to you to decide.

Actions
Copy link
 #1

Updated by Benoît PECCATTE over 6 years ago

  • User visibility set to Infrequent - complex configurations | third party integrations
  • Priority changed from 0 to 18
Actions
Copy link
 #2

Updated by Benoît PECCATTE over 6 years ago

  • Priority changed from 18 to 17
Actions
Copy link
 #3

Updated by Félix DALLIDET about 6 years ago

  • Priority changed from 17 to 16

Had the same problem when trying to upgrade a 4.2 to a hand-made 4.3 package.
Note: the initial rudder version (4.2) was installed with yum and the upgrade made with rpm.

rudder agent version
Rudder agent 4.2.4.release4.3.0.rc2.git201803190212

Actions
Copy link
 #4

Updated by François ARMAND over 5 years ago

  • Status changed from New to Rejected
  • Priority changed from 16 to 15

I think we want to let that as it is because we really don't want to have two agent installed at the same time, and this is a way to find out that there's a problem.

So I propose to not correct it by choice :)

Actions
Copy link

Also available in: Atom PDF