-
Notifications
You must be signed in to change notification settings - Fork 104
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
Return err if db-migration fails #318
Conversation
docs/DEPLOYMENT.md
Outdated
@@ -122,23 +126,26 @@ db-migration-8vhpd 0/1 Completed 0 17s | |||
|
|||
You can also check the logs using `kubectl logs -n tekton-hub db-migration-8vhpd` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can delete this line now
e8d2878
to
8cf3867
Compare
$ kubectl get pods -n tekton-hub | ||
NAME READY STATUS RESTARTS AGE | ||
db-589d44fdd5-ksf8v 1/1 Running 0 50s | ||
db-migration-8vhpd 0/1 Error 0 17s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess it's already there. Ref: https://github.com/tektoncd/hub/pull/318/files#diff-ea9864292e6e392d0c8edbabfe41014d61d6ebd2e08f34d8ae21bf9d070fb274L120
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: PuneetPunamiya The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Earlier db-migration does not returns with error code if it fails and thus we had to check the logs for the failure. With this PR if the migration fails it will return an exit code and thus the job will fail. Also updated the Deployment docs and also fixed some formatting of the docs. Signed-off-by: vinamra28 <vinjain@redhat.com>
8cf3867
to
307a75f
Compare
lgtm |
/lgtm |
Changes
Earlier db-migration does not returns with error code if it fails and thus
we had to check the logs for the failure. With this PR if the migration
fails it will return an exit code and thus the job will fail.
Also updated the Deployment docs and also fixed some formatting of the
docs.
Signed-off-by: vinamra28 vinjain@redhat.com
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
make api-check
make ui-check
See the contribution guide for more details.