Reminder: #dcae team meeting (UTC) When: Wednesday, 12 August 2020, 2:30pm to 3:30pm, (GMT+00:00) UTC Where:https://zoom.us/j/98967242523 View Event Organizer: Vijay Venkatesh Kumar vv770d@... Des

#dcaegen2 #cal-reminder

Reminder: #dcae team meeting (UTC) When: Wednesday, 5 August 2020, 2:30pm to 3:30pm, (GMT+00:00) UTC Where:https://zoom.us/j/98967242523 View Event Organizer: Vijay Venkatesh Kumar vv770d@... Desc

#dcaegen2 #cal-reminder

I didn't encounter your issue in our frankfurt lab.Try to redeloy consul again. Once Consul pods are running all remaining DCAE pods will run. Thanks, Kamel

#frankfurt #dcaegen2

Hi Kamel, My both consul pods go into CLBO. Hence, the dcae pods continue to remain in “Init” state. When checking consul pod logs, shows below. Any help /direction will be greatly appreciated.Thanks.

#frankfurt #dcaegen2

Hello, @Mike Elliott – Please can you provide some inputs on this. Maybe it is know issue on Frankfurt or any workaround for same would be helpful a lot. Regards, Nimesh From: Nimesh K Hindocha Sent:

#aai #dcaegen2 #sdc

Hello, Facing problem with aaf authorization for dmaap-bc / message-router topic subscription. Issue from logs – 2020-07-27 06:21:58.764 INFO 10 --- [pool-2-thread-6] com.att.nsa.apiClient.http.HttpCl

#aai #dcaegen2 #sdc

Cancelled: #dcae team meeting (UTC) This event has been cancelled. When: Wednesday, 29 July 2020 2:30pm to 3:30pm (UTC+00:00) UTC Where: https://zoom.us/j/98967242523 Organizer: Vijay Venkatesh Kumar

#dcaegen2 #cal-cancelled

Hello, I am trying to understand following while working on DCAE micro service On-Boarding. While defining the blueprint want to understand what key value pairs needed for mounting a volume through bl

#dcaegen2

Reminder: #dcae team meeting (UTC) When: Wednesday, 22 July 2020, 2:30pm to 3:30pm, (GMT+00:00) UTC Where:https://zoom.us/j/98967242523 View Event Organizer: Vijay Venkatesh Kumar vv770d@... Descr

#dcaegen2 #cal-reminder

Reminder: #dcae team meeting (UTC) When: Wednesday, 15 July 2020, 2:30pm to 3:30pm, (GMT+00:00) UTC Where:https://zoom.us/j/98967242523 View Event Organizer: Vijay Venkatesh Kumar vv770d@... Descr

#dcaegen2 #cal-reminder

The bootstrap log shows that we did not have the “500 error” that has happened sometimes in the gating environment. Instead, the log shows that the bootstrap process successfully requested the Kuberne

#clamp #dcaegen2

Hi Venkat, Please make sure you deployed consul in your lab as dcae-bootstrap, dcae-deployment-handler pods have dependency on consul-server pod in order they can come up. Thanks, /Kamel

#frankfurt #dcaegen2

Hi Vijay, The log file shared was after the redeployment. Regards, Naveen

#clamp #dcaegen2

Hi Naveen, That’s good. Btw, logs you shared was it before or after the redeployment (couldn’t say from the timestamp)? Based on the log file provided, TCA deployment was successful and healthcheck sh

#clamp #dcaegen2

Hi Vijay, Thanks for the response. Now dcae-tca-analysis pod came up, after executing the commands you provided and DCAE healthcheck is passing now. PFA of tca_pod_describe_podlogs.txt . Regards, Nave

#clamp #dcaegen2

Sylvain - The cfy 500 error is noticed only on gating (something specific to that environment causing random failure). This issue here appears different – deployment through bootstrap/cloudify made th

#clamp #dcaegen2

Hi JACK, The issue is dep-dcae-tca-analytics pod is failed to appear after dcae successful deployment. PFA of results and dcae_bootstrap_logs.txt. Please provide your inputs for the same. Regards, Nav

#clamp #dcaegen2

Well let's wait for Jack thoughts because when the pod fails to appear, it's usually a 500 error on our side :/ I hope he'll be able to find something! De : Naveen S. Sankad [naveen.sankad@...] E

#clamp #dcaegen2

Hi sylvain, From dcae bootstrap pod logs there is no "Error 500" in dcae-tca-analysis deployment. dcae-tca-analysis deployment is success in log. Please refer the attached dcae_bootstrap_logs.txt . Bu

#clamp #dcaegen2

Thanks i was able to get aaf pod running. But i still see DCAE pods sitting intit state. NAME READY STATUS RESTARTS dev-dcae-bootstrap-86c7469b6c-tqfwc 0/1 Init:1/3 0 dev-dcae-config-binding-service-7

#frankfurt #dcaegen2