-
Notifications
You must be signed in to change notification settings - Fork 783
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run an example 404 #2860
Comments
just run fission function test --name hello-js The command returned an error. Error: Error calling function hello-js: 404; Please try again or fix the error: 404 page not found。 I'm unsure about the potential impact of the following error. fission-v1-19-0-fission-v1.19.0-153-fxpdr 0/1 Completed 0 145m |
|
|
Can you share please following command output ?
|
I did not use Helm to install Fission. I used the method without Helm. After that, I installed Helm and executed the command, and the result is as follows: helm get values fission -n fission kubectl get functions -A kubectl get environments -A |
{ |
Unable to download any zip from above dump. Please check Eg.
You should be creating functions, and environments in only namespace which are part of |
|
I couldn't find the pod for the function. I'm not sure if this is normal. |
So you have configured/ created functions in fission namespace.
Where as fission expects functions in
You can try creating function default namespace and see if that works. Also similar discussion in Slack space. https://fissionio.slack.com/archives/C3LUX6BBP/p1697562243769999 |
Yes, indeed, it is this issue. I just tried creating in the default namespace and it worked. Thank you. |
How can I join Slack? My google email is zd514591981@163.com. |
Indeed, when I modify the function creation to the default namespace and test it, it can run successfully. However, other components of Fission, including the route, are all within the fission namespace. As a result, my HTTP calls cannot succeed. Is there a way for me to avoid creating in the default namespace? |
Fission/Kubernetes version
Kubernetes platform (e.g. Google Kubernetes Engine)
Describe the bug
To Reproduce
Error: Error getting function logs from controller: error executing get logs request: no active pods found. Try to get logs from log database.
Warning: version<1.18 used fission-function as pod's default namespace. Specify appropriate namespace with --pod-namespace tag or export an environment variable for function-namespace FUNCTION_NAMESPACE
Options:
--name='' Function name
--method=[GET] HTTP Methods: GET,POST,PUT,DELETE,HEAD. To mention single method: --method GET
and for multiple methods --method GET --method POST. [DEPRECATED for 'fn create',
use 'route create' instead]
--header=[] (-H) Request headers
--body='' (-b) Request body
--query=[] (-q) Request query parameters: -q key1=value1 -q key2=value2
--timeout=1m0s (-t) Length of time to wait for the response. If set to zero or negative number, no
timeout is set
--dbtype='kubernetes' Log database type, e.g. influxdb (currently influxdb and kubernetes logs are
supported)
--subpath='' Sub Path to check if function internally supports routing
Global Options:
--server='' Server URL
--verbosity=1 (-v) CLI verbosity (0 is quiet, 1 is the default, 2 is verbose)
--kube-context='' Kubernetes context to be used for the execution of Fission commands
--namespace='' (-n) If present, the namespace scope for this CLI request
Usage:
fission function test [options]
Error: error getting function response
Expected result
Actual result
Screenshots/Dump file
Additional context
The text was updated successfully, but these errors were encountered: