We're trying to deploy our Google Cloud Functions, but keep getting this error. We get the same error when trying to trigger our functions.
Everything worked fine until today, with no code changes.
Error message:
ERROR: (gcloud.beta.functions.deploy) OperationError: code=13, message=Failure in the execution environment
Steps Taken:
Delete all functions
Redeploy all functions (gcloud SDK)
AFAICT, these are Kubernetes errors, which appears to be a GCF implementation detail leaking through.
There was an issue with Cloud Functions deployments on Firebase just now. See the issue status page for details.
In general, the Firebase status dashboard is a great place to see if there are any known issues. If there aren't, it doesn't hurt to reach out to Firebase support either.
Problem was a bug in GCF.
Contacted support team for resolution. There was an outage at the same time (thanks #Frank van Puffelen), but it was unrelated.
Related
I recently deployed a Next.js application for a software engineering boot camp. I am using Vercel for hosting the web app. The problem I am having has been spoken about on the internet before. However, I couldn't find much helpful information.
When I look at the real-time logs for my application from my Vercel dashboard, a 504 error gets thrown for multiple API routes I have created. I am aware that Vercel places restrictions on requests depending on the hosting plan someone subscribes to. However, I can't help but wonder if I have overlooked an important step when deploying my application.
When deploying my application, I did the following things:
Connected a session store to my MongoDB database.
Created a password-protected MongoDB Atlas account (credentials are environment variables).
White-listed all IP addresses so that any user can interact with their portion of the database.
I would appreciate help finding out if these errors are my fault and if there is anything I can do about them or if they are solely caused by the restrictions of the "Hobby" plan.
Thank you very much in advance,
-Sam
Screen Shot:
I had a similar issue, turned out, it was just the fact that I did not add the vercel ip addr to the network access page on mongodb so momgodb was blocking vercel from accessing data.
You need to integrate MongoDB in your project on Vercel.
Go to your project settings in Vercel and go to the Integrations tab. Click the Browse Marketplace button and find MongoDb. Click Add Integration button and follow the instructions.
Hope this helps... I know this was asked quite a while ago.
You have to troubleshoot the issue by doing the following
Eliminate the NextJS app out of the equation - Using postman https://www.postman.com/downloads/ - Confirm the output of your API, what is the time the API takes? Given function invocation has a limit, you need to optimize the API to meet the threshold.
If the API times are fine and resolution occurs outside of your app, the next step is to troubleshoot the API route, remove the DB parts and just echo back a success message and check the function invocation time.
If #2 turns out to be the issue, reach out to vercel support - Another option could be hosting it outside and whitelisting the cross domain API ask from your application.
I am trying to use KubeFlow on GCP and I am following this codelab, but "click-to-deploy" is no longer supported so I followed the documentation of "kubectl and kpt". However, I keep getting this "You cannot perform this action because the Cloud SDK component manager is disabled for this installation." error and none of the solutions I found worked. I have 2 other friends told me they tried to make KubeFlow work since last year, it never worked, but I did see people post question about KubeFlow on Stackoverflow still, so I want to ask if it is still working, if so, where can I find a decent guide to follow?
Thanks!
I finally got it working. For that error message, it turned out that I just didn't install the Cloud SDK properly. There will be a lot of other issues too down the road, but at least the KubeFlow web UI is working for me now.
yes, as the kubectl and kpt says, the first step in getting prepared to install cluster is installing gcloud that is CLI that manages authentication, local configuration, developer workflow, interactions with Google Cloud APIs.
Without is you simply cant work with objects(in your case you need to enable kpt anthoscli beta) and perform tasks like
creating a Compute Engine VM instance, managing a Google Kubernetes
Engine cluster, and deploying an App Engine application, either from
the command line or in scripts and other automations..
I'm using GitLab CI/CD to automatically transfer the code after every push to the master branch. Everything is going well there. But when Kubernete gets the code, it throws this error message:
Extended error:
I need some help about that.
A CrashLoopBackoff error means that GKE is trying to launch a Pod but the containers within are crashing or being terminated.
There is no simple answer to this. This is a specific error within your application which could be caused by various reasons. You will have to investigate it by looking through the logs.
By the way, I found another thread that looks very similar to yours.
I'm trying to create a build and release to a actors service in Visual Studio Online. I already created build and release to anothers services fabric without problem. But with this specific service I getting the error below:
The BuildLayout of the application in E:\SFabric\SP\SP2DS\Fabric\work\ImageBuilderProxy\AppType\SchedulerServiceAppType is invalid. Config is missing for service SchedulerServicePkg.
The first time the release works fine, but after the first version is released, the others releases I got this error.
The others services are Stateless, I dont know why this problem happens and just with this service that is Stateful.
New Information
I'm trying to change advantages setting and I got successful sometimes.
Even that, I want to know how I do correctly
# Novac - Just noticed a duplicate post on Github addressing this specific issue. More importantly, a member of Azure's Service Fabric Dev team is actively engaged and waiting for your response to his followup questions - ref snip below:
Currently tracked via GitHub issue:https://github.com/Azure/service-fabric-issues/issues/802. Strongly recommend redirecting this conversation to the Github thread/url above.
The presence insight server on bluemix has been quite unstable now. Cannot get access to the server.
Is there any way to deploy the instance on softlayer server for production?
There were definitely some problems with PI last evening, but the team worked until early this morning to get them resolved. It looks like the system is back up and functioning. Are you still seeing the issue?
Also, as a general reference, this page has service status details on it that may be of help if you notice a problem.