[JBoss JIRA] (WFWIP-177) Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink
by Martin Choma (Jira)
[ https://issues.jboss.org/browse/WFWIP-177?page=com.atlassian.jira.plugin.... ]
Martin Choma commented on WFWIP-177:
------------------------------------
It turned out it is caused by recent docker CVE fix. It is tracked by [1].
In OCP terms:
- I see test fails on v3.11.129 and v3.11.117
- I see test pass on v3.11.82
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1738599
[2] https://github.com/openshift/source-to-image/issues/987
> Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink
> --------------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-177
> URL: https://issues.jboss.org/browse/WFWIP-177
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Ken Wills
> Priority: Major
>
> Use case is providing settings.xml as secret. I wonder if this could be some ubi7 file permission issue.
> {code}
> Receiving source from STDIN as archive ...
> Using docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD... as the s2i builder image
> error: Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/etc/test-secret/..data" -> "..2019_08_19_13_20_57.538692366"
> ERROR: Error occurred during injecting "/var/run/secrets/openshift.io/build/test-secret" to "/etc/test-secret": Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/etc/test-secret/..data" -> "..2019_08_19_13_20_57.538692366"
> error: build error: non-zero (13) exit code from docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD...
> {code}
> {code:yaml|title=BuildConfig}
> apiVersion: build.openshift.io/v1
> kind: BuildConfig
> metadata:
> creationTimestamp: '2019-08-19T13:20:41Z'
> name: sti-secret-settings
> namespace: mchoma
> resourceVersion: '1345248'
> selfLink: >-
> /apis/build.openshift.io/v1/namespaces/mchoma/buildconfigs/sti-secret-settings
> uid: 249b6a94-c284-11e9-b93c-fa163e9a0fb6
> spec:
> failedBuildsHistoryLimit: 5
> nodeSelector: {}
> output:
> to:
> kind: ImageStreamTag
> name: 'sti-secret-settings:latest'
> postCommit: {}
> resources: {}
> runPolicy: Serial
> source:
> binary: {}
> secrets:
> - destinationDir: /etc/test-secret
> secret:
> name: test-secret
> type: Binary
> strategy:
> sourceStrategy:
> env:
> - name: MAVEN_ARGS
> value: install -s /etc/test-secret/settings.xml
> from:
> kind: DockerImage
> name: >-
> docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD...
> incremental: false
> type: Source
> successfulBuildsHistoryLimit: 5
> triggers:
> - generic:
> allowEnv: true
> secret: secret101
> type: Generic
> status:
> lastVersion: 1
> {code}
> {code:yaml|title=Secret}
> apiVersion: v1
> data:
> settings.xml: >-
> PHNldHRpbmdzPgogPHByb2ZpbGVzPiAgPHByb2ZpbGU+ICAgICA8aWQ+dGVzdDwvaWQ+ICAgICA8cmVwb3NpdG9yaWVzPiAgICAgICA8cmVwb3NpdG9yeT4gICAgICAgICA8aWQ+RUFQLTc8L2lkPiAgICAgICAgIDxuYW1lPkVBUDcgcmVwbzwvbmFtZT4gICAgICAgICA8dXJsPmh0dHBzOi8vbWF2ZW4ucmVwb3NpdG9yeS5yZWRoYXQuY29tL2dhLzwvdXJsPiAgICAgICA8L3JlcG9zaXRvcnk+ICAgICA8L3JlcG9zaXRvcmllcz4gICA8L3Byb2ZpbGU+ICA8L3Byb2ZpbGVzPiAgPGFjdGl2ZVByb2ZpbGVzPiAgICA8YWN0aXZlUHJvZmlsZT50ZXN0PC9hY3RpdmVQcm9maWxlPiA8L2FjdGl2ZVByb2ZpbGVzPiA8L3NldHRpbmdzPg==
> kind: Secret
> metadata:
> creationTimestamp: '2019-08-19T13:20:41Z'
> name: test-secret
> namespace: mchoma
> resourceVersion: '1345244'
> selfLink: /api/v1/namespaces/mchoma/secrets/test-secret
> uid: 246843e8-c284-11e9-b93c-fa163e9a0fb6
> type: Opaque
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFWIP-177) Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink
by Ken Wills (Jira)
[ https://issues.jboss.org/browse/WFWIP-177?page=com.atlassian.jira.plugin.... ]
Ken Wills edited comment on WFWIP-177 at 8/20/19 1:24 AM:
----------------------------------------------------------
[~mchoma] I've mounted the secret as part of the buildconfig and it appears to work find, though the builder pod completes so quickly I can't actually verify the secret is present in the pod. I'll have to try a longer running version in the morning and verify it is present.
I don't see any reason why there would be a permissions issue when mounting it though, and there is nothing obvious missing from the UBI 7 image (tar etc).
Do you have any more info on how this is all set up and triggered? If its in the testsuite, could you link me the test?
was (Author: luck3y):
[~mchoma] I've mounted the secret as part of the buildconfig and it appears to work find, though the builder pod completes so quickly I can't actually verify the secret is present in the pod. I'll have to try a longer running version in the morning and verify it is present.
I don't see any reason why there would be a permissions issue when mounting it though, and there is nothing obvious missing from the UBI 7 image (tar etc).
> Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink
> --------------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-177
> URL: https://issues.jboss.org/browse/WFWIP-177
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Ken Wills
> Priority: Major
>
> Use case is providing settings.xml as secret. I wonder if this could be some ubi7 file permission issue.
> {code}
> Receiving source from STDIN as archive ...
> Using docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD... as the s2i builder image
> error: Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/etc/test-secret/..data" -> "..2019_08_19_13_20_57.538692366"
> ERROR: Error occurred during injecting "/var/run/secrets/openshift.io/build/test-secret" to "/etc/test-secret": Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/etc/test-secret/..data" -> "..2019_08_19_13_20_57.538692366"
> error: build error: non-zero (13) exit code from docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD...
> {code}
> {code:yaml|title=BuildConfig}
> apiVersion: build.openshift.io/v1
> kind: BuildConfig
> metadata:
> creationTimestamp: '2019-08-19T13:20:41Z'
> name: sti-secret-settings
> namespace: mchoma
> resourceVersion: '1345248'
> selfLink: >-
> /apis/build.openshift.io/v1/namespaces/mchoma/buildconfigs/sti-secret-settings
> uid: 249b6a94-c284-11e9-b93c-fa163e9a0fb6
> spec:
> failedBuildsHistoryLimit: 5
> nodeSelector: {}
> output:
> to:
> kind: ImageStreamTag
> name: 'sti-secret-settings:latest'
> postCommit: {}
> resources: {}
> runPolicy: Serial
> source:
> binary: {}
> secrets:
> - destinationDir: /etc/test-secret
> secret:
> name: test-secret
> type: Binary
> strategy:
> sourceStrategy:
> env:
> - name: MAVEN_ARGS
> value: install -s /etc/test-secret/settings.xml
> from:
> kind: DockerImage
> name: >-
> docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD...
> incremental: false
> type: Source
> successfulBuildsHistoryLimit: 5
> triggers:
> - generic:
> allowEnv: true
> secret: secret101
> type: Generic
> status:
> lastVersion: 1
> {code}
> {code:yaml|title=Secret}
> apiVersion: v1
> data:
> settings.xml: >-
> PHNldHRpbmdzPgogPHByb2ZpbGVzPiAgPHByb2ZpbGU+ICAgICA8aWQ+dGVzdDwvaWQ+ICAgICA8cmVwb3NpdG9yaWVzPiAgICAgICA8cmVwb3NpdG9yeT4gICAgICAgICA8aWQ+RUFQLTc8L2lkPiAgICAgICAgIDxuYW1lPkVBUDcgcmVwbzwvbmFtZT4gICAgICAgICA8dXJsPmh0dHBzOi8vbWF2ZW4ucmVwb3NpdG9yeS5yZWRoYXQuY29tL2dhLzwvdXJsPiAgICAgICA8L3JlcG9zaXRvcnk+ICAgICA8L3JlcG9zaXRvcmllcz4gICA8L3Byb2ZpbGU+ICA8L3Byb2ZpbGVzPiAgPGFjdGl2ZVByb2ZpbGVzPiAgICA8YWN0aXZlUHJvZmlsZT50ZXN0PC9hY3RpdmVQcm9maWxlPiA8L2FjdGl2ZVByb2ZpbGVzPiA8L3NldHRpbmdzPg==
> kind: Secret
> metadata:
> creationTimestamp: '2019-08-19T13:20:41Z'
> name: test-secret
> namespace: mchoma
> resourceVersion: '1345244'
> selfLink: /api/v1/namespaces/mchoma/secrets/test-secret
> uid: 246843e8-c284-11e9-b93c-fa163e9a0fb6
> type: Opaque
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFWIP-177) Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink
by Ken Wills (Jira)
[ https://issues.jboss.org/browse/WFWIP-177?page=com.atlassian.jira.plugin.... ]
Ken Wills commented on WFWIP-177:
---------------------------------
[~mchoma] I've mounted the secret as part of the buildconfig and it appears to work find, though the builder pod completes so quickly I can't actually verify the secret is present in the pod. I'll have to try a longer running version in the morning and verify it is present.
I don't see any reason why there would be a permissions issue when mounting it though, and there is nothing obvious missing from the UBI 7 image (tar etc).
> Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink
> --------------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-177
> URL: https://issues.jboss.org/browse/WFWIP-177
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Ken Wills
> Priority: Major
>
> Use case is providing settings.xml as secret. I wonder if this could be some ubi7 file permission issue.
> {code}
> Receiving source from STDIN as archive ...
> Using docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD... as the s2i builder image
> error: Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/etc/test-secret/..data" -> "..2019_08_19_13_20_57.538692366"
> ERROR: Error occurred during injecting "/var/run/secrets/openshift.io/build/test-secret" to "/etc/test-secret": Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/etc/test-secret/..data" -> "..2019_08_19_13_20_57.538692366"
> error: build error: non-zero (13) exit code from docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD...
> {code}
> {code:yaml|title=BuildConfig}
> apiVersion: build.openshift.io/v1
> kind: BuildConfig
> metadata:
> creationTimestamp: '2019-08-19T13:20:41Z'
> name: sti-secret-settings
> namespace: mchoma
> resourceVersion: '1345248'
> selfLink: >-
> /apis/build.openshift.io/v1/namespaces/mchoma/buildconfigs/sti-secret-settings
> uid: 249b6a94-c284-11e9-b93c-fa163e9a0fb6
> spec:
> failedBuildsHistoryLimit: 5
> nodeSelector: {}
> output:
> to:
> kind: ImageStreamTag
> name: 'sti-secret-settings:latest'
> postCommit: {}
> resources: {}
> runPolicy: Serial
> source:
> binary: {}
> secrets:
> - destinationDir: /etc/test-secret
> secret:
> name: test-secret
> type: Binary
> strategy:
> sourceStrategy:
> env:
> - name: MAVEN_ARGS
> value: install -s /etc/test-secret/settings.xml
> from:
> kind: DockerImage
> name: >-
> docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD...
> incremental: false
> type: Source
> successfulBuildsHistoryLimit: 5
> triggers:
> - generic:
> allowEnv: true
> secret: secret101
> type: Generic
> status:
> lastVersion: 1
> {code}
> {code:yaml|title=Secret}
> apiVersion: v1
> data:
> settings.xml: >-
> PHNldHRpbmdzPgogPHByb2ZpbGVzPiAgPHByb2ZpbGU+ICAgICA8aWQ+dGVzdDwvaWQ+ICAgICA8cmVwb3NpdG9yaWVzPiAgICAgICA8cmVwb3NpdG9yeT4gICAgICAgICA8aWQ+RUFQLTc8L2lkPiAgICAgICAgIDxuYW1lPkVBUDcgcmVwbzwvbmFtZT4gICAgICAgICA8dXJsPmh0dHBzOi8vbWF2ZW4ucmVwb3NpdG9yeS5yZWRoYXQuY29tL2dhLzwvdXJsPiAgICAgICA8L3JlcG9zaXRvcnk+ICAgICA8L3JlcG9zaXRvcmllcz4gICA8L3Byb2ZpbGU+ICA8L3Byb2ZpbGVzPiAgPGFjdGl2ZVByb2ZpbGVzPiAgICA8YWN0aXZlUHJvZmlsZT50ZXN0PC9hY3RpdmVQcm9maWxlPiA8L2FjdGl2ZVByb2ZpbGVzPiA8L3NldHRpbmdzPg==
> kind: Secret
> metadata:
> creationTimestamp: '2019-08-19T13:20:41Z'
> name: test-secret
> namespace: mchoma
> resourceVersion: '1345244'
> selfLink: /api/v1/namespaces/mchoma/secrets/test-secret
> uid: 246843e8-c284-11e9-b93c-fa163e9a0fb6
> type: Opaque
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFLY-12394) Execute portions of the testsuite using a slimmed server instead of the normal dist
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-12394:
---------------------------------------
Summary: Execute portions of the testsuite using a slimmed server instead of the normal dist
Key: WFLY-12394
URL: https://issues.jboss.org/browse/WFLY-12394
Project: WildFly
Issue Type: Task
Components: Test Suite
Reporter: Brian Stansberry
Assignee: Brian Stansberry
A lot of the testsuite can run against a slimmed server, not requiring the standard installation. So, if -Dts.layers is set (which currently turns on testsuite/layers) also execute profiles in other testsuite modules that provision slimmed servers and all or a subset of the module's tests.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFWIP-176) Pod restarted because of failing liveness/rediness Probe
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFWIP-176?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFWIP-176:
----------------------------------------
[~mchoma] Is it possible that in CD 16 the test simply completed and exited before the probe could fail?
Before CLOUD-2742 internally the python code would loop up to 30 times trying to execute the request to the server, with a 5 sleep each time. And then the yaml configures 3 tries before failure with more sleep. So that's a long time.
Now the python fails immediately.
> Pod restarted because of failing liveness/rediness Probe
> --------------------------------------------------------
>
> Key: WFWIP-176
> URL: https://issues.jboss.org/browse/WFWIP-176
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Ken Wills
> Priority: Major
>
> During testing 73 image I came to case where really corner case is tested [0].
> Test is not using templates for deployment.
> In tested scenario liveness/readiness probe fails. In CD 17 and eap 73 pod is restarted. In CD 16 however, there was no liveness/rediness failures in events. Pod was not restarted.
> I dont see differences in pod yaml for CD16 case
> {code}
> livenessProbe:
> exec:
> command:
> - /bin/bash
> - '-c'
> - /opt/eap/bin/livenessProbe.sh
> failureThreshold: 3
> periodSeconds: 10
> successThreshold: 1
> timeoutSeconds: 1
> name: weirdusername
> readinessProbe:
> exec:
> command:
> - /bin/bash
> - '-c'
> - /opt/eap/bin/readinessProbe.sh
> failureThreshold: 3
> periodSeconds: 10
> successThreshold: 1
> timeoutSeconds: 1
> {code}
> and CD 17 case
> {code}
> livenessProbe:
> exec:
> command:
> - /bin/bash
> - '-c'
> - /opt/eap/bin/livenessProbe.sh
> failureThreshold: 3
> periodSeconds: 10
> successThreshold: 1
> timeoutSeconds: 1
> name: weirdusername
> readinessProbe:
> exec:
> command:
> - /bin/bash
> - '-c'
> - /opt/eap/bin/readinessProbe.sh
> failureThreshold: 3
> periodSeconds: 10
> successThreshold: 1
> timeoutSeconds: 1
> {code}
> What could cause this behaviour change?
> [0] https://issues.jboss.org/browse/CLOUD-1988
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFWIP-177) Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink
by Ken Wills (Jira)
[ https://issues.jboss.org/browse/WFWIP-177?page=com.atlassian.jira.plugin.... ]
Ken Wills commented on WFWIP-177:
---------------------------------
@mchoma I'll give this a try shortly here. I think its more likely something missing from the default UBI 7 install, but it could be default permissions too...
> Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink
> --------------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-177
> URL: https://issues.jboss.org/browse/WFWIP-177
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Martin Choma
> Assignee: Ken Wills
> Priority: Major
>
> Use case is providing settings.xml as secret. I wonder if this could be some ubi7 file permission issue.
> {code}
> Receiving source from STDIN as archive ...
> Using docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD... as the s2i builder image
> error: Uploading to container failed: Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/etc/test-secret/..data" -> "..2019_08_19_13_20_57.538692366"
> ERROR: Error occurred during injecting "/var/run/secrets/openshift.io/build/test-secret" to "/etc/test-secret": Error response from daemon: Error processing tar file(exit status 1): invalid symlink "/etc/test-secret/..data" -> "..2019_08_19_13_20_57.538692366"
> error: build error: non-zero (13) exit code from docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD...
> {code}
> {code:yaml|title=BuildConfig}
> apiVersion: build.openshift.io/v1
> kind: BuildConfig
> metadata:
> creationTimestamp: '2019-08-19T13:20:41Z'
> name: sti-secret-settings
> namespace: mchoma
> resourceVersion: '1345248'
> selfLink: >-
> /apis/build.openshift.io/v1/namespaces/mchoma/buildconfigs/sti-secret-settings
> uid: 249b6a94-c284-11e9-b93c-fa163e9a0fb6
> spec:
> failedBuildsHistoryLimit: 5
> nodeSelector: {}
> output:
> to:
> kind: ImageStreamTag
> name: 'sti-secret-settings:latest'
> postCommit: {}
> resources: {}
> runPolicy: Serial
> source:
> binary: {}
> secrets:
> - destinationDir: /etc/test-secret
> secret:
> name: test-secret
> type: Binary
> strategy:
> sourceStrategy:
> env:
> - name: MAVEN_ARGS
> value: install -s /etc/test-secret/settings.xml
> from:
> kind: DockerImage
> name: >-
> docker-registry.engineering.redhat.com/kwills/eap73-openshift-rhel7:CLOUD...
> incremental: false
> type: Source
> successfulBuildsHistoryLimit: 5
> triggers:
> - generic:
> allowEnv: true
> secret: secret101
> type: Generic
> status:
> lastVersion: 1
> {code}
> {code:yaml|title=Secret}
> apiVersion: v1
> data:
> settings.xml: >-
> PHNldHRpbmdzPgogPHByb2ZpbGVzPiAgPHByb2ZpbGU+ICAgICA8aWQ+dGVzdDwvaWQ+ICAgICA8cmVwb3NpdG9yaWVzPiAgICAgICA8cmVwb3NpdG9yeT4gICAgICAgICA8aWQ+RUFQLTc8L2lkPiAgICAgICAgIDxuYW1lPkVBUDcgcmVwbzwvbmFtZT4gICAgICAgICA8dXJsPmh0dHBzOi8vbWF2ZW4ucmVwb3NpdG9yeS5yZWRoYXQuY29tL2dhLzwvdXJsPiAgICAgICA8L3JlcG9zaXRvcnk+ICAgICA8L3JlcG9zaXRvcmllcz4gICA8L3Byb2ZpbGU+ICA8L3Byb2ZpbGVzPiAgPGFjdGl2ZVByb2ZpbGVzPiAgICA8YWN0aXZlUHJvZmlsZT50ZXN0PC9hY3RpdmVQcm9maWxlPiA8L2FjdGl2ZVByb2ZpbGVzPiA8L3NldHRpbmdzPg==
> kind: Secret
> metadata:
> creationTimestamp: '2019-08-19T13:20:41Z'
> name: test-secret
> namespace: mchoma
> resourceVersion: '1345244'
> selfLink: /api/v1/namespaces/mchoma/secrets/test-secret
> uid: 246843e8-c284-11e9-b93c-fa163e9a0fb6
> type: Opaque
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months