Project

General

Profile

Actions
Copy link

Bug #5070

closed

Issue with "Packet version match" in package management directive

Added by Olivier Chédru over 10 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
1 (highest)
Assignee:
Vincent MEMBRÉ
Category:
Web - Config management
Target version:
2.10.11
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When creating a directive "Package management for Debian / Ubuntu / APT systems", the web interface is not able to distinguish between ">= This version or any later one" and ">= This version or any earlier one" for "Packet version match".

If I switch the attribute between these two values and click "Save", I get "There are no modifications to save."

Maybe the selection is based on a truncated value?

Related issues 1 (0 open — 1 closed)

Is duplicate of Rudder - Bug #4754: Technique "Package management for Debian / Ubuntu / APT systems", typo in the option to install an earlier packageReleasedJonathan CLARKE2014-04-14Actions
Actions
Copy link
 #1

Updated by Matthieu CERDA over 10 years ago

  • Category set to Web - Config management
  • Status changed from New to 8
  • Assignee set to Vincent MEMBRÉ
  • Priority changed from N/A to 1 (highest)

Thanks for the report !

Vince, you know more about the webapp than me :) Do you know what's wrong in here ?

Actions
Copy link
 #2

Updated by Vincent MEMBRÉ over 9 years ago

  • Status changed from 8 to Rejected
  • Target version set to 2.10.11

I can't reproduce it anymore.

Is it still happening Olivier ?

I guess this was related to #4754, since you talk about the wrong params for earlier (>=)

Since the param was '>=' got both options Rudder said there was nothing to save.

I'm closing this a duplicate, but feel free to open it again if it is not fixed

Actions
Copy link

Also available in: Atom PDF