Re: [onap-discuss] [aai]: Error in Beijing OOM installation for aai-sparky-be

2018-07-20 Thread Arul Nambi
Hi,
Are you using the windriver labs for your deployment?
We have it deployed in AAI windriver lab and it is working fine. Some time the 
crashloopbackoff state will resolve on its own. So try bringing up spraky again.
Also you will be needing this patch as well
https://gerrit.onap.org/r/gitweb?p=oom.git;a=commit;h=01a80afbf5e04b9c05b3f590d643c81b16088b3b
If you want to see data coming trough AAI-ui. Try to apply this patch and 
re-deploy.
Regards
Arul

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Chandra
Sent: Friday, July 20, 2018 8:56 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [aai]: Error in Beijing OOM installation for 
aai-sparky-be

Hi,

We have successfully installed Beijing 2.0.0_ONAP using OOM.  All the pods were 
up and running after installation. As a part of sanity test, we were able to 
login to Portal, SDC but AAI portal was unreachable. We found out that the 
patch is available to resolve the AAI portal issue with following Jira reference
https://gerrit.onap.org/r/#/c/55139

We have applied the patch but aai-sparkey-be was in CrashLoopBackOff state. 
When we tried to describe the pod, we have got following output.

describe pod beijing-aai-sparky-be
Events:
  Type Reason  Age   FromMessage
   --    ---
  Warning  BackOff 41m (x3794 over 20h)  kubelet, node2  Back-off 
restarting failed container
  Normal   Pulling 26m (x357 over 21h)   kubelet, node2  pulling image 
"nexus3.onap.org:10001/onap/sparky-be:1.2.1"
  Warning  Unhealthy   11m (x1797 over 21h)  kubelet, node2  Readiness probe 
failed: dial tcp 10.42.47.134:8000: getsockopt: connection refused
  Warning  FailedSync  1m (x3917 over 20h)   kubelet, node2  Error syncing pod

We got the following error in logs

OperationResult [result=null, requestedLink=null, 
failureCause={"requestError":{"policyException":{"messageId":"POL3300","text":"Unauthorized
 (msg=%1) (ec=%2)","variables":["Unauthorized","ERR.5.1.3300"]}}}, 
resultCode=403, numRetries=0, 
responseHeaders={Strict-Transport-Security=[max-age=1600; 
includeSubDomains; preload;], 
X-AAI-TXID=[2-aai-traversal-180719-14:06:04:798-35534], Content-Length=[143], 
Date=[Thu, 19 Jul 2018 14:06:04 GMT]}]

Do let us know if there is any resolution for this error. Please refer to 
attached logs.

Thanks
Chandrashekhar Thakare




Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at http://www.techmahindra.com/Disclaimer.html externally 
http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra.


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11313): https://lists.onap.org/g/onap-discuss/message/11313
Mute This Topic: https://lists.onap.org/mt/23753639/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



[onap-discuss] [aai]: Error in Beijing OOM installation for aai-sparky-be

2018-07-20 Thread Chandra
Hi,

We have successfully installed Beijing 2.0.0_ONAP using OOM.  All the pods were 
up and running after installation. As a part of sanity test, we were able to 
login to Portal, SDC but AAI portal was unreachable. We found out that the 
patch is available to resolve the AAI portal issue with following Jira reference
https://gerrit.onap.org/r/#/c/55139

We have applied the patch but aai-sparkey-be was in CrashLoopBackOff state. 
When we tried to describe the pod, we have got following output.

describe pod beijing-aai-sparky-be
Events:
  Type Reason  Age   FromMessage
   --    ---
  Warning  BackOff 41m (x3794 over 20h)  kubelet, node2  Back-off 
restarting failed container
  Normal   Pulling 26m (x357 over 21h)   kubelet, node2  pulling image 
"nexus3.onap.org:10001/onap/sparky-be:1.2.1"
  Warning  Unhealthy   11m (x1797 over 21h)  kubelet, node2  Readiness probe 
failed: dial tcp 10.42.47.134:8000: getsockopt: connection refused
  Warning  FailedSync  1m (x3917 over 20h)   kubelet, node2  Error syncing pod

We got the following error in logs

OperationResult [result=null, requestedLink=null, 
failureCause={"requestError":{"policyException":{"messageId":"POL3300","text":"Unauthorized
 (msg=%1) (ec=%2)","variables":["Unauthorized","ERR.5.1.3300"]}}}, 
resultCode=403, numRetries=0, 
responseHeaders={Strict-Transport-Security=[max-age=1600; 
includeSubDomains; preload;], 
X-AAI-TXID=[2-aai-traversal-180719-14:06:04:798-35534], Content-Length=[143], 
Date=[Thu, 19 Jul 2018 14:06:04 GMT]}]

Do let us know if there is any resolution for this error. Please refer to 
attached logs.

Thanks
Chandrashekhar Thakare





Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at http://www.techmahindra.com/Disclaimer.html 
 externally 
http://tim.techmahindra.com/tim/disclaimer.html 
 internally within 
TechMahindra.



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11309): https://lists.onap.org/g/onap-discuss/message/11309
Mute This Topic: https://lists.onap.org/mt/23753639/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

+ jar ufv /opt/app/sparky/lib/sparkybe-onap-application-1.2.1.jar -C 
/opt/app/sparky/appconfig/portal/ BOOT-INF/classes/portal.properties
adding: BOOT-INF/classes/portal.properties(in = 949) (out= 455)(deflated 52%)
+ java -Xms1024m -Xmx4096m -DAPP_HOME=/opt/app/sparky 
-DCONFIG_HOME=/opt/app/sparky/appconfig 
-Dlogging.config=/opt/app/sparky/appconfig/logging/logback.xml -jar 
/opt/app/sparky/lib/sparkybe-onap-application-1.2.1.jar
   _  _   __    _   _   
   _  
  / || |   |  _ \|  |_   / __ \| \ | |   /\ 
  |  __ \ 
 | (___  _ __   __ _ _ __| | ___   _ __| |_) | |__  (_) | |  | |  \| |  /  
\  | |__) |
  \___ \| '_ \ / _` | '__| |/ / | | |__|  _ <|  __| | |  | | . ` | / /\ 
\ |  ___/ 
  ) | |_) | (_| | |  |   <| |_| |  | |_) | | _  | |__| | |\  |/ 
 \| | 
 |_/| .__/ \__,_|_|  |_|\_\\__, |  |/|__(_)  \/|_| \_/_/
\_\_| 
| | __/ |   
  
|_||___/
  
OperationResult [result=null, requestedLink=null, 
failureCause={"requestError":{"policyException":{"messageId":"POL3300","text":"Unauthorized
 (msg=%1) (ec=%2)","variables":["Unauthorized","ERR.5.1.3300"]}}}, 
resultCode=403, numRetries=0, 
responseHeaders={Strict-Transport-Security=[max-age=1600; 
includeSubDomains; preload;], 
X-AAI-TXID=[2-aai-traversal-180719-14:06:04:798-35534], Content-Length=[143], 
Date=[Thu, 19 Jul 2018 14:06:04 GMT]}]
OperationResult [result=null, requestedLink=null, 
failureCause={"requestError":{"policyException":{"messageId":"POL3300","text":"Unauthorized
 (msg=%1) (ec=%2)","variables":["Unauthorized","ERR.5.1.3300"]}}}, 
resultCode=403, numRetries=0, 
responseHeaders={Strict-Transport-Security=[max-age=1600; 
includeSubDomains; preload;], 
X-AAI-TXID=[0-aai-traversal-180719-14:06:04:801-61427], Content-Length=[143], 
Date=[Thu, 19 Jul 2018 14:06:04 GMT]}]
OperationResult [result=null, requestedLink=null,