I have pushed my last work to the repository, however, when I try to deploy, I get this error:
$ eb deploy myapp -v
Password:
INFO: Deploying code to myapp in region us-east-1
INFO: Getting version label from git with git-describe
INFO: Pushing local code to codecommit with git-push
INFO: Creating AppVersion app-V-2_0-90-g57b9-181013_080409
ERROR: InvalidParameterValueError - "Error making request to CodeCommit: Could not retrieve 57b9246856a66460a7d04161d3f107f0553ac6ce (Service: AWSCodeCommit; Status Code: 400; Error Code: CommitIdDoesNotExistException; Request ID: 6d67928b-cea5-11e8-8620-d3a635300337)"
How can I get more details about that InvalidParameterValueError as in the error above?
What does CommitIdDoesNotExistException mean? I already pushed my latest commit.
Any idea?
Related
※I am a beginner, so if you have any information you need, please comment.
Based on the yaml file, I am trying to publish a sample app that has already been launched in Pod via Ingress.
$kubectl apply -f ./overlays/stg/bookinfo-ingress.yaml
■Errormessage
Error from server (InternalError): error when creating "./overlays/stg/bookinfo-ingress.yaml": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": failed to call webhook: Post "https://ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1/ingresses?timeout=10s": x509: certificate signed by unknown authority
I have created an AQL that gives me a number of artifacts I want to delete from Artifactory. I can run a search command with the jfrog-cli on it, and get the correct list of artifacts:
jfrog rt s --spec search-aql.json
When I try to delete the same artifacts with the same AQL, everything seems fine:
The artifacts are listed
I get a questions of whether to delete them or not.
I answer yes, and the command goes on to log the deletion of each item.
Each item seems to be returned and printed to my console, followed by this message:
[Error] Artifactory response: 200 OK
Binaries are also printed to the console, so the console output is really messy.
In the end, I get a summary:
{
"status": "failure",
"totals": {
"success": 0,
"failure": 68
}
}
[Error] Artifactory response: 200 OK
With the same user, I can delete individual artifacts using the REST API, so the user does have the necessary rights to do deletion.
I am on version 1.38.2 of the JFrog CLI and 7.2.1 of Artifactory.
Can anybody help me understand what is wrong or how to debug this problem?
Update 2020/08/06:
When setting the log level to debug as suggested by #Prostagma, I get two extra lines of logging for each artifact. Here is an example of logging for two artifacts:
[Info] [Thread 1] Deleting <path>/<artifact>.jar.sha512
[Debug] Sending HTTP DELETE request to: https://repo.enonic.com/<path>/<artifact>.jar.sha512
[Error] Artifactory response: 200 OK
<sha512 hash>
[Info] [Thread 0] Deleting <path>/<artifact>.jar
[Debug] Sending HTTP DELETE request to: https://repo.enonic.com/<path>/<artifact>.jar
[Error] Artifactory response: 200 OK
<binary contents of <artifact>.jar
More detailed answer to whomever encounter this issue in the future -
By diving into the code we can see that the CLI expects to get status 204 from Artifactory after deletion:
https://github.com/jfrog/jfrog-client-go/blob/v0.12.0/artifactory/services/delete.go#L110
In some installations, there may be a proxy that changes the response codes, for example when Artifactory returns 204, it may change the status code to 200.
Please make sure that your proxy doesn't change the status codes returned from Artifactory.
I am setting up Bitbucket pipeline for a Wordpress deployment on Elastic Beanstalk.
This error message pops up in line eb init --region AWS_DEFAULT_REGION --platform php-5.5 :
ERROR: ServiceError - '/20200712/$AWS_DEFAULT_REGION/elasticbeanstalk/aws4_request' not a valid key=value pair (missing equal-sign) in Authorization header: 'AWS4-HMAC-SHA256 Credential=$AWS_ACCESS_KEY_ID/20200712/$AWS_DEFAULT_REGION/elasticbeanstalk/aws4_request, SignedHeaders=content-type;host;x-amz-content-sha256;x-amz-date, Signature=3d7fef....8383d5'.
Other relevant questions and why it doesn't solve my problem :
1 2 : Don't have /.aws/config in Bitbucket environment
3 : Error message mentioned above
The Bitbucket pipeline till now :
image: tyrellsys/aws-ebcli
pipelines:
branches:
master:
- step:
script:
- export AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID
- export AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY
- export AWS_DEFAULT_REGION=$AWS_DEFAULT_REGION
- export APPLICATION_NAME=$APPLICATION_NAME
- export ENVIRONMENT_NAME=$ENVIRONMENT_NAME
- eb init --region ap-southeast-1 --platform php-5.5
- eb deploy wordpress-beanstalk
Based on the comments.
The issue was related to incorrectly set $AWS_ACCESS_KEY_ID, $AWS_SECRET_ACCESS_KEY and $AWS_DEFAULT_REGION.
Fixing the values was the solution to the reported issue with key=value pair (missing equal-sign).
I tried to create client app of my API created using API Platform. I follow this guide https://api-platform.com/docs/client-generator/vuejs/.
I use Laravel Homestead for the VM when developing it.
I've added myapp .crt file to Keychan Access.
Problem was, when I try to execute
generate-api-platform-client --generator vue https://myapp-api.local/api src/
It return error message like this:
{
api: Api { entrypoint: 'https://myapp-api.local/api', resources: [] },
error: FetchError: request to https://myapp-api.local/api failed, reason: unable to verify the first certificate
at ClientRequest.<anonymous> (/Users/permana.jayanta/.config/yarn/global/node_modules/node-fetch/index.js:133:11)
at ClientRequest.emit (events.js:209:13)
at TLSSocket.socketErrorListener (_http_client.js:406:9)
at TLSSocket.emit (events.js:209:13)
at emitErrorNT (internal/streams/destroy.js:91:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
name: 'FetchError',
message: 'request to https://myapp-api.local/api failed, reason: unable to verify the first certificate',
type: 'system',
errno: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE',
code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'
},
response: undefined,
status: undefined
}
I'm thinking this is related with SSL certificate. That node doesn't recognise the certificate. How to make node.js recognise the custom SSL certificate generated by Homestead?
it failed to verify https signature.
To disable it, type in shell
export NODE_TLS_REJECT_UNAUTHORIZED=0
When I use vs-mda-remote to test cordova on mac, it failed with an error:
error CordovaModuleLoadError 4.1.2
and when I use vs-mda-remote test, the error is:
error CordovaModuleLoadError 4.3.0
vs-mda-remote
this start the server ok.
And I try the cordova, it can build success. Following is the full output:
New build request submitted:
/build/tasks?command=build&vcordova=4.1.2&cfg=release
{ 'accept-language': 'zh-CN',
host: '192.168.1.244:3000',
connection: 'keep-alive',
'transfer-encoding': 'chunked' }
New build request submitted for cordovaVersion: 4.1.2; buildCommand: build; configuration: release
Build will be executed under: /Users/czcz1024/remote-builds/builds/610
Saving build request payload to : /Users/czcz1024/remote-builds/builds/610
Saved upload to /Users/czcz1024/remote-builds/builds/610/upload_610.tgz
Extracting /Users/czcz1024/remote-builds/builds/610/upload_610.tgz to /Users/czcz1024/remote-builds/builds/610/cordovaApp...
POST /build/tasks?command=build&vcordova=4.1.2&cfg=release 202 2291ms - 495b
GET /build/tasks/610 200 2ms - 495b
Extracted app contents from uploaded build request to /Users/czcz1024/remote-builds/builds/610/cordovaApp. Requesting build.
Taking 610 as current build
Building cordova app BlankCordovaApp1 at appDir /Users/czcz1024/remote-builds/builds/610/cordovaApp
Opened build log file /Users/czcz1024/remote-builds/builds/610/build.log
GET /build/tasks/610 200 1ms - 585b
Done building 610 : error CordovaModuleLoadError [ '4.1.2' ]
Done with currentBuild. Checking for next build in queue.
GET /build/tasks/610 200 1ms - 621b
GET /build/tasks/610/log 200 6ms
and follow is output run test
New build request submitted:
/build/tasks?vcordova=4.3.0&cfg=release&command=build&options=--emulator
{ host: 'localhost:3000',
connection: 'close',
'transfer-encoding': 'chunked' }
New build request submitted for cordovaVersion: 4.3.0; buildCommand: build; configuration: release
Build will be executed under: /Users/czcz1024/remote-builds/builds/611
Saving build request payload to : /Users/czcz1024/remote-builds/builds/611
Saved upload to /Users/czcz1024/remote-builds/builds/611/upload_611.tgz
Extracting /Users/czcz1024/remote-builds/builds/611/upload_611.tgz to /Users/czcz1024/remote-builds/builds/611/cordovaApp...
POST /build/tasks?vcordova=4.3.0&cfg=release&command=build&options=--emulator 202 217ms - 505b
Extracted app contents from uploaded build request to /Users/czcz1024/remote-builds/builds/611/cordovaApp. Requesting build.
Taking 611 as current build
Building cordova app HelloCordova at appDir /Users/czcz1024/remote-builds/builds/611/cordovaApp
Opened build log file /Users/czcz1024/remote-builds/builds/611/build.log
Done building 611 : error CordovaModuleLoadError [ '4.3.0' ]
Done with currentBuild. Checking for next build in queue.
GET /build/tasks/611 200 1ms - 627b
what's wrong?
This might be a permissions issue with your .npm folder where the new version of vs-mda-remote tries to install the Cordova package.
Can you try to run the following 2 commands:
$ sudo npm cache clear
$ sudo chown -R `whoami` ~/.npm
And then restart your vs-mda-remote server?