Highlighted
Trusted Contributor.
Trusted Contributor.
130 views

SMAX 2020-02 : Error while deploying tenant

Jump to solution

Hi,

I'm installing SMAx 2020.02 and I've got an issue when deploying the first tenant (sorry it's in french):

gsisteron_0-1589953192942.png

 


The error is: 

API Call failed for tenant creation

General Error Occurs!500 ; response:null

 

I've been searching in logs files, but I can't find details that can help.

In itom-bo-ats logs :

2020-05-13 08:07:13.127 ebdf7277-aa8c-4aaf-beee-25b520c26ea3 INFO 705 --- [http-nio-31027-exec-8] com.hpe.itsma.bo.ats.agent.BaseAgent     : rest call with :{Url: http://itom-bo-login-svc:31024/bo/token}

2020-05-13 08:07:13.182 ebdf7277-aa8c-4aaf-beee-25b520c26ea3 INFO 705 --- [http-nio-31027-exec-8] com.hpe.itsma.bo.ats.agent.BaseAgent     : Url: http://itom-bo-login-svc:31024, execution duration 55 ms.

2020-05-13 08:07:13.183 ebdf7277-aa8c-4aaf-beee-25b520c26ea3 INFO 705 --- [http-nio-31027-exec-8] c.h.itsma.bo.common.advice.LoggerAdvice  : ***********Service{class com.hpe.itsma.bo.ats.agent.APIAgent} End***********

2020-05-13 08:07:13.183 ebdf7277-aa8c-4aaf-beee-25b520c26ea3 INFO 705 --- [http-nio-31027-exec-8] c.hpe.itsma.bo.ats.util.APIHeadersUtil   : X-CORRELATION_ID_HEADER:ebdf7277-aa8c-4aaf-beee-25b520c26ea3

2020-05-13 08:07:17.070 ebdf7277-aa8c-4aaf-beee-25b520c26ea3ERROR 705 --- [http-nio-31027-exec-8] com.hpe.itsma.bo.ats.agent.BaseAgent     : 500

 

In itom-bo-login logs :

2020-05-13 08:07:13.130 b83aba32-5629-44d9-9f20-d51c9ba025e3 INFO 687 --- [http-nio-31024-exec-5] c.h.i.b.g.controller.TokenController     : Tokan API: get LWSSO for idm orgs: AuthContext{mainOrg='sysbo', secondaryOrgs=[], accountId='10000', tenantLoginType='null', authGroup='null', singleOrg=false, customDomain=null, returnUrl=null}

2020-05-13 08:07:13.179 b83aba32-5629-44d9-9f20-d51c9ba025e3 INFO 687 --- [http-nio-31024-exec-5] c.h.i.b.g.controller.TokenController     : Tokan API: get LWSSO from IDM OK.

2020-05-13 08:07:13.181 b83aba32-5629-44d9-9f20-d51c9ba025e3 INFO 687 --- [http-nio-31024-exec-5] c.h.i.b.g.controller.TokenController     : Token API: The user **PERSONAL INFORMATION REMOVED** is an integration user for SAW, will not query BO user

 

Have you got an idea, of what can go wrong ?

Thanks for your help !

0 Likes
1 Solution

Accepted Solutions
Highlighted
Trusted Contributor.
Trusted Contributor.

I finally uninstalled the suite itsma, and then reinstalled it. This time, it works : the tenant has deployed correctly

https://docs.microfocus.com/itom/SMAX:2020.02/UninstallCDFAndSuite

 

 

View solution in original post

0 Likes
5 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

I think there are some other logs to check.

Also please make sure all the pods are running, it might be are source related issue  as long as you have all the pre-reqs for the tenant deployment.

https://docs.microfocus.com/itom/SMAX:2020.02/CreateTenant

There are some known issues in 2020.02 without patches so also look under the troubleshooting section in documentation.

0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Hi,

 

Check if the db user used in SMAX has the correct rights in the db.

 

BR,

Alex

Highlighted
Trusted Contributor.
Trusted Contributor.
Hi Alex,



Do you know which user I should check ? (all the user have been created automatically during install, I've only created manually 'cdfapiserver')





postgres=# \du

List of roles

Role name | Attributes | Member of

--------------+------------------------------------------------------------+-----------------------------------------------

autopass | Create DB | {}

bo_db_user | | {}

cdfapiserver | | {}

cdfidm | | {}

idm | Create DB | {}

maas_admin | Create DB | {}

postgres | Superuser, Create role, Create DB, Replication, Bypass RLS | {cdfapiserver,autopass,bo_db_user,smarta,idm}

smarta | | {}




0 Likes
Highlighted
Super Contributor.. Super Contributor..
Super Contributor..

Hi gsisteron,

 

So you dont have separate DB, in this case, check if all pods are up and running.

kubectl get ns

 kubectl get pods --namespace itsma-namespace

 

BR,

Alex

0 Likes
Highlighted
Trusted Contributor.
Trusted Contributor.

I finally uninstalled the suite itsma, and then reinstalled it. This time, it works : the tenant has deployed correctly

https://docs.microfocus.com/itom/SMAX:2020.02/UninstallCDFAndSuite

 

 

View solution in original post

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.