Open lilyLuLiu opened 4 months ago
@lilyLuLiu hi, can you please share the mapt
command you ran, please also make sure you have the AWS_DEFAULT_REGION
env variable set
Hi, the error happened in new cluster's pipeline with running https://github.com/redhat-developer/mapt/blob/main/tkn/infra-aws-rhel.yaml task. The most like problem is some address needs to be added into egress. But I can't find any clue in the log.
yeah, we are having issues while connecting to the AWS API due to some egress rules policies on the cluster; so basically here, an according to this use case:
In case of an error on that connection this should exit properly (maybe this is related on how spot price history is picked (not sure if with Pulumi or direct call to the AWS API, in any case the connection error should exist properly)
Beyond the error it seems some data aggregation is panic ing due to some empty array (it seems like), probably if first error exit the execution this panic will not occur, but in any case we have a missing check for a value somewhere on the spot price module
After debug, I found the address 169.254.169.254
is connected during the provision process.
After add this address into egress, the issue is solved.
ACK
I will keep this one open, as we still need to add some checks to ensure a proper error is shown in case of wrong connectivity when login against the cloud provider
I failed to provision with mapt. The error log is as follow: