Bug 1802036

Summary:	Migration to fix casing to AzureRm
Product:	Red Hat Satellite	Reporter:	Aditi Puntambekar <apuntamb>
Component:	Compute Resources - Azure	Assignee:	Aditi Puntambekar <apuntamb>
Status:	CLOSED ERRATA	QA Contact:	vijsingh
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.7.0	CC:	egolov, zhunting
Target Milestone:	6.7.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_azure_rm-2.0.7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-14 13:28:43 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 Aditi Puntambekar 2020-02-12 08:54:35 UTC

Description of problem:
Once the server starts, it says uninitialized constant ForemanAzureRM::AzureRM. This may happen for existing/older Azure compute resource, but casing was changed to AzureRm recently in the plugin. Hence, for users to smoothly continue using the compute resource, they should run the migration added.

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


How reproducible:


Steps to Reproduce:
1.Upon starting server, it says uninitialized constant ForemanAzureRM::AzureRM.
2.
3.

Actual results:
uninitialized constant ForemanAzureRM::AzureRM

Expected results:
Should run the migration and continue with compute resource as expected.


Additional info:

Comment 4 vijsingh 2020-02-24 13:50:00 UTC

Verified

@Satellite 6.7.0 snap 13.0

 - API Automation tests passed on upgraded Satellite.

Comment 7 errata-xmlrpc 2020-04-14 13:28:43 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1454