Bug 1376451

Summary:	Azure provider subscription expiration limitations
Product:	Red Hat CloudForms Management Engine	Reporter:	Leo Khomenko <lkhomenk>
Component:	Providers	Assignee:	Daniel Berger <dberger>
Status:	CLOSED NOTABUG	QA Contact:	Jeff Teehan <jteehan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.6.0	CC:	dajohnso, jfrey, jhardy, jteehan, obarenbo
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	provider:azure
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1376524 (view as bug list)		Environment:
Last Closed:	2016-09-15 23:03:15 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:
Bug Depends On:
Bug Blocks:	1376524

Description Leo Khomenko 2016-09-15 13:01:57 UTC

Description of problem:After Azure subscription is expired and it's in Readonly state it's impossible to update provider info:
"The subscription '9ee63d8e-aee7-4121-861c-d67a5b8d231e' is disabled and therefore marked as read only. You cannot perform any write actions on this subscription until it is re-enabled." Do we assume Refresh provider's relationships and power states as Write operation?


Version-Release number of selected component (if applicable): 5.6.1.2 / 5.6.2.0 /5.7


How reproducible:Always


Steps to Reproduce:
1.Set up Azure with expired/disabled subscription
2.
3.

Actual results:Provider won't be updated


Expected results:Get provider objects info - Instances/states/etc


Additional info:

Comment 1 Greg Blomquist 2016-09-15 14:13:28 UTC

Dan, 

I think the best the application can do is report a nice error message here.

Can you work with Leo (from QE) to look into his environment?

Comment 2 Daniel Berger 2016-09-15 15:10:51 UTC

Greg, at the moment the best we can do is a warning. Perhaps when they click the "validate" button. I'll talk to the UI folks about that.

In theory we could disable certain portions of the UI if the subscription is in readonly mode, but that might be too provider specific. If other providers have a "readonly" mode, perhaps we could imitate them.

Comment 4 Jeff Teehan 2016-09-15 23:03:15 UTC

This is not a bug, unless you want a better error message.  In fact, the subscription had been disabled due to expiration of credits.  You can't get in if you don't pay regardless of the error message or how much you really want to get in.

In my opinion, the error message was consistent with the error.  And, when we reactivated the subscription and refreshed, it went back to success.