Known Issues
Known Issues
Learn issues and behavioral caveats while using Service Provider.
Service Provider is currently a
Tech Preview
to provide you with access to new features so that Kyndryl Modern Operations Applications hears your feedback and works on delivering features that meet your needs. On this page, you can find documented known issues and behavioral caveats in the Service Provider Administration portal. Kyndryl Modern Operations Applications works to resolve known issues and are actively monitored. The concepts of known issues, behavioral caveats, and bugs are defined as follows:
- Known issues:Conditions under which the console does not exhibit the expected behavior.
- Behavioral caveats:Intended behaviors that, for reasons beyond the control of the console technology, the console cannot successfully complete.
- Bugs:Errors, flaws or faults in program or system that causes it to produce an incorrect or unexpected result.
Kyndryl works to resolve Known issues as resources are available and according to priorities. This approach is different than the management of Behavioral caveats, which are actively monitored so that required changes can be synchronized with dependencies.
Known issues
Known issues |
|---|
Customer tenant status reflects incorrect status in the details page : After successful update of a customer tenant, the applications updated show a green checkmark icon meaning success; however, the Status column in the details page gets stuck showing an 'in progress' status. This should not affect the successful update of your customer tenant. |
Behavioral caveats
Behavioral caveats |
|---|
At the present time, while the platform is in a transition period toward a simple and unified authorization model, the platform works with three different Role Based Access Control (RBAC) models:
Some applications already adopted the new authorization model, and some are in the process of adoption. The applications that have adopted the new authorization model are Common Actions , Common Inventory , Shared Services and Common Discovery . Base and DevOps are still using the role binding construct; whereas the rest of the applications continue to use the existing legacy Core role and will be adopting this new model during the rest of the year.The top banner in the landing page displays only the Legacy role bindings and the legacy Core roles that the user has been assigned. The roles associated with the access policies assigned to the users are not reflected here. |
The "Data last updated" timestamp on Cost & Asset Management will get updated in customer tenant whenever there is a recommendation job completed on service provider tenant, irrespective of the resources shared with the customer. |
On Cost and Asset Management , the data last updated timestamp after remediation of the service provider tenant will not be updated in the customer tenant. |
On Cost and Asset Management , when the corporate currency is other than non USD in the service provider tenant, the cost in customer tenant for the managed accounts will be zero. To overcome this, the service provider must set the same currency conversion rate in both the service provider tenant and in the customer tenant. |
Changes made to the IdPs in the service provider tenant may take up to five (5) minutes before they get propagated to the customer tenant. |
Do you have two minutes for a quick survey?
Take Survey
