Bug 1406458

Summary: [Azure] Add ability to lock Azure virtual machine to RHEL major version
Product: Red Hat Update Infrastructure for Cloud Providers Reporter: David Mulford <dmulford>
Component: OperationsAssignee: Todd Sanders <tsanders>
Status: CLOSED CURRENTRELEASE QA Contact: Vratislav Hutsky <vhutsky>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.0.0CC: ajoseph, amdas, dkinkead, dwhatley, lwilliam, mminar, pcreech, rbiba
Target Milestone: ---   
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: 2019-04-02 10:53:59 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 David Mulford 2016-12-20 15:24:35 UTC 
Description of problem:
Azure customer attempted to keep RHEL version to 7.2, but found the yum option --releasever doesn't work as expected.

sudo yum --releasever=7.2 update
sample error output:
https://rhui-1.microsoft.com/pulp/repos//content/dist/rhel/rhui/server/7/7.2/x86_64/debug/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found

Azure Marketplace virtual machines use the Red Hat Update Infrastructure (RHUI) for package updates, and provides only "7Server" which doesn't distinguish between RHEL 7.2 and 7.3.

The end result is that a RHEL 7.2 machine will be updated to RHEL 7.3, even if the customer doesn't intend for this to happen.

Version-Release number of selected component (if applicable):


How reproducible:
Always


Steps to Reproduce:
1. Create a RHEL 7.2 virtual machine from the Azure Marketplace
2. Run `yum update`

Actual results:
The machine is updated to RHEL 7.3


Expected results:
The machine should stay on RHEL 7.2