When i try to create a stack using cloudformation i get the following error;
PuppetMaster
CREATE_FAILED Received FAILURE signal with UniqueId i-instanceId
WSO2APIManagerSetup-XXXX
CREATE_FAILED
The following resource(s) failed to create: [PuppetMaster].
WSO2APIMPattern1
Status reason
The following resource(s) failed to create: [WSO2APIManagerSetup]
Where do i check what the actual error was for the PuppetMaster task. Is there any logs on either the PuppetMaster(instanceId), WSO2APIMPattern1 or WSO2APIManagerSetup instances that i can go check?
P.S
Nothing in the cloudtrail logs either
I was not able to track down the logs, however i found the issue.
I was populating the WUMUsername and since i don't have a subscription, this was failing. By leaving the WUMUsername and WUMPassword fields blank in the template, everything worked flawlessly.
I suppose i can backtrack to see where in the stack the error would have been thrown, but thats an exercise for another day.
Related
I am trying to deploy the .net CI/CD AWS pipeline with Quick Start: https://aws.amazon.com/quickstart/architecture/dotnet-core-cicd/
The problem is that when I try to execute it I keep getting the same error and don't know why:
Resource handler returned message: "Exceeded attempts to wait" (RequestToken: 5f97c7e0-970e-60fc-ac70-fe89ec301c41, HandlerErrorCode: NotStabilized)
I already tried using the following troubleshooting page (https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html), but without any further improvements/advancements.
I tried waiting a day and trying it again because I thought I maybe was trying to execute the template too often.
What could resolve my problem?
When I deploy new deployments or edit any settings, It returns following Error
Error creating: Internal error occurred: failed calling webhook
"mpod.elbv2.k8s.aws": Post
"https://aws-load-balancer-webhook-service.kube-system.svc:443/mutate-v1-pod?timeout=10s":
x509: certificate has expired or is not yet valid: current time
2022-01-28T02:05:13Z is after 2022-01-20T10:00:30Z
How can i fix it??
I think the reason is because your time and date are not right. As I can see in the log, your time is 8 days behind the current day.
Please sync your time in this server and try again.
You need to have new certificate for aws-load-balancer-webhook-service. We have issuer set up in the cluster and when we get similar error in OPA we do a rollout restart for opa.
I tried to create a Google Cloud Composer environment but in the page to set it up I get the following errors:
Service Error: Failed to load GKE machine types. Please leave the field
empty to apply default values or retry later.
Service Error: Failed to load regions. Please leave the field empty to
apply default values or retry later.
Service Error: Failed to load zones. Please leave the field empty to apply
default values or retry later.
Service Error: Failed to load service accounts. Please leave the field
empty to apply default values or retry later.
The only parameters GCP lets me change are the region and the number of nodes, but still lets me create the environment. After 30 minutes the environment crashes with the following error:
CREATE operation on this environment failed 1 day ago with the following error message:
Http error status code: 400
Http error message: BAD REQUEST
Errors in: [Web server]; Error messages:
Failed to deploy the Airflow web server. This might be a temporary issue. You can retry the operation later.
If the issue persists, it might be caused by problems with permissions or network configuration. For more information, see https://cloud.google.com/composer/docs/troubleshooting-environment-creation.
An internal error occurred while processing task /app-engine-flex/flex_await_healthy/flex_await_healthy>2021-07-20T14:31:23.047Z7050.xd.0: Your deployment has failed to become healthy in the allotted time and therefore was rolled back. If you believe this was an error, try adjusting the 'app_start_timeout_sec' setting in the 'readiness_check' section.
Got error "Another operation failed." during CP_DEPLOYMENT_CREATING_STANDARD []
Is it a problem with permissions? If so, what permissions do I need? Thank you!
It looks like more of a temporary issue:
the first set of errors is stating you cannot load the metadata :
regions list, zones list ....
you dont have a clear
PERMISSION_DENIED error
the second error: is suggesting also:
This might be a temporary issue.
I am trying to run my own algorithm container in amazon sagemaker,at the time of deployment time ,I am getting error like below.
predictor = tree.deploy(1, 'ml.m4.xlarge', serializer=csv_serializer)
ValueError: Error hosting endpoint decision-trees-sample-2018-03-01-09-59-06-832: Failed Reason: The primary container for production variant AllTraffic did not pass the ping health check.
then I run same line of code this time i am getting below error.
predictor = tree.deploy(1, 'ml.m4.xlarge', serializer=csv_serializer)
ClientError: An error occurred (ValidationException) when calling the CreateEndpoint operation: Cannot create already existing endpoint "arn:aws:sagemaker:us-east-1:69759707XXxXX:endpoint/decision-trees-sample-2018-03-01-09-59-06-832".
Check out this issue: https://github.com/awslabs/amazon-sagemaker-examples/issues/210
#djarpin wrote:
The ping health check message is a general error that can be caused by several different issues. Typically the error message in the CloudWatch log group named /aws/sagemaker/Endpoints/ will provide a more detailed description of why the ping health check didn't pass.
Hope that helps!
Good day, I am using the AWS quick start for linux-bastion.
On changing the QSS3BucketName and QSS3KeyPrefix to the ones in my account it throws the error
Received 1 FAILURE signal(s) out of 1. Unable to satisfy 100% MinSuccessfulInstancesPercent requirement
everything else in the stack is getting created, the script being pulled from the s3 bucket and user data being on the instance. The only issue is, autoscaling group fails to create despite providing the instance and running the user data. My guess is something is happening in the s3accesscreds which i am not able to fathom.
WHAT CAN BE THE CATCH?? would really appreciate any help, thank you
I had a similar problem. You need to make sure that the bastion_bootstrap.sh file here is placed under the correct location in your bucket:
your-bucket-name/your-prefix/scripts/bastion_bootstrap.sh
And, of course, that the bastion_bootstrap script itself doesn't throw any errors. If it does, you'll see them in /var/log/cfn-init.log