Skip to content
This repository has been archived by the owner on Jan 12, 2023. It is now read-only.

a aws instance is running, but the supstcribtion status is pending #103

Open
elfriedegoetz opened this issue Jun 21, 2018 · 2 comments
Open
Assignees
Labels
bug P3 Priority 3 QA

Comments

@elfriedegoetz
Copy link

elfriedegoetz commented Jun 21, 2018

[Build]
docker 17.7 2018/06/11

[Steps to reproduce]
login as Technical Provider "TP1"
import a TechnicalService_AWS
define a marketable service "AWS" and publish on marketplace
subcribe to service "AWS"

[Expected result]
instance will be created and subscription will be show status "ready"

[Observed result]
instance is running on aws!!, but a mail is send
"Notification of Catalog Manager about the provisioning process for subscription 'AWS' failed."
and the status of subscription "AWS" is pending

[Details]
The error occurs if the technical provider organisation owning the technical service does not match the organization configured for the controller.

@GoebelL
Copy link
Member

GoebelL commented Jun 22, 2018

In fact the technical provider of the AWS service must match the organization for ess.aws configured in APP. However the error handling is weak at this point. Better the provisioning service should somehow check the proper assignment in before hand in order to avoid that administrators can run into this trap after setting up such integration. Well, we'll need to think it some further...

@GoebelL GoebelL added this to the 18.0 milestone Jul 4, 2018
@GoebelL GoebelL self-assigned this Jul 5, 2018
@GoebelL GoebelL added the P3 Priority 3 label Jul 5, 2018
@elfriedegoetz
Copy link
Author

the same for vmware

@kowalczyka kowalczyka removed the major label Mar 1, 2019
@GoebelL GoebelL removed this from the 18.0 milestone May 17, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug P3 Priority 3 QA
Projects
None yet
Development

No branches or pull requests

3 participants