Bug 1312259

Summary: yum-plugin-versionlock possible to add an package twice.
Product: Red Hat Enterprise Linux 6 Reporter: Frank Büttner <bugzilla>
Component: yumAssignee: Valentina Mukhamedzhanova <vmukhame>
Status: CLOSED WONTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.7CC: james.antill
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 11:12:07 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Frank Büttner 2016-02-26 09:11:59 UTC
Description of problem:
It is possible to add an lock twice.

Version-Release number of selected component (if applicable):
yum-plugin-versionlock.noarch 0:1.1.30-30

How reproducible:
every time

Steps to Reproduce:
1. yum versionlock add java-1.8.0-openjdk-headless
2. yum versionlock add java-1.8.0-openjdk-headless

Actual results:
LANG=C yum versionlock list
Loaded plugins: fastestmirror, presto, versionlock
1:java-1.8.0-openjdk-headless-1.8.0.45-35.b13.el6.*
1:java-1.8.0-openjdk-headless-1.8.0.45-35.b13.el6.*
versionlock list done


Expected results:
That the second try is rejected.

Comment 3 Jan Kurik 2017-12-06 11:12:07 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/