-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
ci-operator/config/openshift/installer/openshift-installer-master.yaml: Set containers_image_openpgp #3078
Conversation
…l: Set containers_image_openpgp To avoid [1]: 2019/03/12 16:18:40 Executing test unit vendor/github.com/containers/image/pkg/blobinfocache/boltdb.go:9:2: cannot find package "github.com/boltdb/bolt" in any of: /go/src/github.com/openshift/installer/vendor/github.com/boltdb/bolt (vendor tree) /usr/local/go/src/github.com/boltdb/bolt (from $GOROOT) /go/src/github.com/boltdb/bolt (from $GOPATH) and similar. [1]: https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_installer/1286/pull-ci-openshift-installer-master-unit/3190/build-log.txt
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wking 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 |
Would users of installer run tests without that tag? |
If they wanted to have the installer create and sign new images? But I don't think that's very likely ;). The gpgme backend is only needed for signing, golang.org/x/crypto/openpgp is sufficient for verification (which is all I expect the installer to ever need). |
/retest |
All green :). |
does that mean if we were to merge openshift/installer#1286 |
Yes, but I'd rather not include these in the installer's |
for example, we place all libvirt code behind |
Unless you expect the installer to create signatures for new images (which I don't), we won't need gpgme. The openpgp library I'm enabling with this tag is all we need for verifying signatures. The libvirt libraries, on the other hand, have a valid (if occasional) installer use case. |
/unassign |
@abhinavdahiya @wking @crawford o/ folks! Can one of you please remove me from the assignees? |
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.
Just setting request for change :)
@flaper87: changing LGTM is restricted to collaborators In response to this:
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: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
Doesn't seem to be much demand for this. /close |
@wking: Closed this PR. In response to this:
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. |
To avoid:
and similar. CC @abhinavdahiya