You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2023. It is now read-only.
[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.
The text was updated successfully, but these errors were encountered:
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...
[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.
The text was updated successfully, but these errors were encountered: