Skip to content

Conversation

@wking
Copy link
Member

@wking wking commented Mar 13, 2020

Fixing errors like:

2020/03/12 23:45:35 Container cp-secret-wrapper in pod e2e-steps-ipi-conf completed successfully
mkdir: cannot create directory '/tmp/secret': File exists
error: [failed to execute wrapped command: exit status 1]
2020/03/12 23:45:37 Container ipi-conf in pod e2e-steps-ipi-conf failed, exit code 1, reason Error

I haven't traced this back to see when it broke, but I'd guess some ci-tools code is now creating /tmp/secret for each container.

Fixing errors like [1]:

  2020/03/12 23:45:35 Container cp-secret-wrapper in pod e2e-steps-ipi-conf completed successfully
  mkdir: cannot create directory '/tmp/secret': File exists
  error: [failed to execute wrapped command: exit status 1]
  2020/03/12 23:45:37 Container ipi-conf in pod e2e-steps-ipi-conf failed, exit code 1, reason Error

I haven't traced this back to see when it broke, but I'd guess some
ci-tools code is now creating /tmp/secret for each container.

[1]: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_installer/3269/pull-ci-openshift-installer-release-4.4-e2e-steps/138#1:build-log.txt%3A45
@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Mar 13, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 13, 2020
@wking
Copy link
Member Author

wking commented Mar 13, 2020

e2e-steps died on CI registry flakes and similar:

error: build error: Failed to push image: received unexpected HTTP status: 500 Internal Server Error
  * step ovirt-installer failed: could not wait for build: the build ovirt-installer failed after 5m14s with reason PushImageToRegistryFailed: Failed to push the image to the registry.

/retest

@wking
Copy link
Member Author

wking commented Mar 13, 2020

Hmm, doesn't seem to have stuck. Trying more directly:

/test pj-rehearse

@wking
Copy link
Member Author

wking commented Mar 13, 2020

Hrm:

level=error msg="Error: [ERR]: Error building changeset: InvalidChangeBatch: [Tried to create resource record set [name='api.ci-op-vvtn0znp-a9648.origin-ci-int-aws.dev.rhcloud.com.', type='A'] but it already exists]"
level=error msg="\tstatus code: 400, request id: f0d30ddf-bbb2-4839-b8cc-875876f4f964"

Cleaning up my project so I get a fresh namespace:

$ oc delete project ci-op-vvtn0znp

And trying again:

/test pj-rehearse

@bbguimaraes
Copy link
Contributor

This was caused by openshift/ci-tools#544.

I ended up running out of time yesterday, thanks for fixing it.

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 13, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bbguimaraes, wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit ac5280f into openshift:master Mar 13, 2020
@openshift-ci-robot
Copy link
Contributor

@wking: Updated the step-registry configmap in namespace ci at cluster default using the following files:

  • key ipi-conf-commands.sh using file ci-operator/step-registry/ipi/conf/ipi-conf-commands.sh
  • key ipi-install-install-commands.sh using file ci-operator/step-registry/ipi/install/install/ipi-install-install-commands.sh
Details

In response to this:

Fixing errors like:

2020/03/12 23:45:35 Container cp-secret-wrapper in pod e2e-steps-ipi-conf completed successfully
mkdir: cannot create directory '/tmp/secret': File exists
error: [failed to execute wrapped command: exit status 1]
2020/03/12 23:45:37 Container ipi-conf in pod e2e-steps-ipi-conf failed, exit code 1, reason Error

I haven't traced this back to see when it broke, but I'd guess some ci-tools code is now creating /tmp/secret for each container.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@wking wking deleted the drop-mkdir branch March 16, 2020 21:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants