-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[Conformance] deploymentconfigs with custom deployments should run the custom deployment steps flakes #17631
Comments
CC @tnozicka |
seen here as well https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/17628/test_pull_request_origin_extended_conformance_gce/12469/ /assign tnozicka |
@mfojtik I think those are 2 different flakes in the first case this is either journald (@soltysh ?) or docker logs issue because the deployer pod completed succesfully
in the second case it got stuck on failed (regular) pods:
not really sure how |
Journals can be easily checked, look for 'Suppressed x messages from....',
if it doesn't exist it's not journald. If it does ping me.
…On Dec 11, 2017 5:06 PM, "Tomáš Nožička" ***@***.***> wrote:
@mfojtik <https://github.com/mfojtik> I think those are 2 different flakes
in the first case this is either journald ***@***.***
<https://github.com/soltysh> ?) or docker logs issue because the deployer
pod completed succesfully
ec 6 13:15:35.770: INFO: At 2017-12-06 13:15:19 +0000 UTC - event for custom-deployment: {custom-deployment-1-deploy } Started: Running pre-hook ("/bin/echo test pre hook executed") for rc extended-test-cli-deployment-h94tt-x597n/custom-deployment-1
Dec 6 13:15:35.770: INFO: At 2017-12-06 13:15:19 +0000 UTC - event for custom-deployment: {custom-deployment-1-deploy } Completed: The pre-hook for rc extended-test-cli-deployment-h94tt-x597n/custom-deployment-1 completed successfully
in the second case it got stuck on failed (regular) pods:
Dec 6 14:53:14.339: INFO: At 2017-12-06 14:38:34 +0000 UTC - event for custom-deployment-1-h8rpp: {kubelet ci-prtest-5a37c28-12469-ig-n-hvz3} BackOff: Back-off restarting failed container
Dec 6 14:53:14.339: INFO: At 2017-12-06 14:39:21 +0000 UTC - event for custom-deployment-1-ztd6v: {kubelet ci-prtest-5a37c28-12469-ig-n-scf5} BackOff: Back-off restarting failed container
not really sure how /bin/bash sleep 10 could fail with Back-off
restarting failed container so this is likely something wrong on a
pod/infra level
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#17631 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAjLVQuwI4aFbIwXmRx77o1pH_zUPv1cks5s_VLmgaJpZM4Q4D97>
.
|
closing in favor of #17747 |
Seen here: https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/17606/test_pull_request_origin_extended_conformance_gce/12465/
A full log:
The text was updated successfully, but these errors were encountered: