See <https://ci.centos.org/job/atomicapp-test-kubernetes-master/8/>
------------------------------------------ [...truncated 5132 lines...] ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ... ./providers/kubernetes.sh answers ########## GENERATING KUBERNETES ANSWERS FILE ########## ./helloapache.sh run kubernetes ########## run: TESTING HELLOAPACHE EXAMPLE ########## Sending build context to Docker daemon 11.26 kB Sending build context to Docker daemon 11.26 kB Step 1 : FROM atomicapp:build ---> 4bc5e279f345 Step 2 : MAINTAINER Red Hat, Inc. <[email protected]> ---> Running in fff49573f327 ---> 756447696a9b Removing intermediate container fff49573f327 Step 3 : LABEL io.projectatomic.nulecule.providers "kubernetes,docker,marathon" io.projectatomic.nulecule.specversion "0.0.2" ---> Running in 4705eea7aa62 ---> 2740eddac1d0 Removing intermediate container 4705eea7aa62 Step 4 : ADD /Nulecule /Dockerfile README.md /application-entity/ ---> ba427160e41b Removing intermediate container 1c347557a550 Step 5 : ADD /artifacts /application-entity/artifacts ---> 562b46091555 Removing intermediate container 49c60dfe91d0 Successfully built 562b46091555 docker run -it --rm --privileged -v /tmp/test/cdrage-atomicapp-ci/functional-tests:/atomicapp -v /run:/run -v /:/host --net=host --name helloapache -e USER -e SUDO_USER -e NAME=helloapache -e IMAGE=projectatomic/helloapache projectatomic/helloapache run --provider=kubernetes -a answers.conf -v --destination=build --logtype=nocolor This container uses privileged security switches: [1mINFO: --net=host[0m Processes in this container can listen to ports (and possibly rawip traffic) on the host's network. [1mINFO: --privileged[0m This container runs without separation and should be considered the same as root on your system. For more information on these switches and their security implications, consult the manpage for 'docker run'. Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning. 1460481111 - [INFO] - cli/main.py - Action/Mode Selected is: run 1460481111 - [DEBUG] - cli/main.py - Final parsed cmdline: run --provider=kubernetes -a answers.conf -v --destination=build --logtype=nocolor 1460481111 - [DEBUG] - cli/main.py - Setting app_spec based on $IMAGE env var 1460481111 - [DEBUG] - nulecule/main.py - NuleculeManager init app_path: build 1460481111 - [DEBUG] - nulecule/main.py - NuleculeManager init image: projectatomic/helloapache 1460481111 - [DEBUG] - atomicapp/utils.py - Loading answers from file: answers.conf 1460481111 - [DEBUG] - nulecule/main.py - Request to unpack to projectatomic/helloapache to build 1460481111 - [INFO] - nulecule/base.py - Unpacking image: projectatomic/helloapache to build 1460481111 - [INFO] - nulecule/container.py - Skipping pulling Docker image: projectatomic/helloapache 1460481111 - [INFO] - nulecule/container.py - Extracting nulecule data from image: projectatomic/helloapache to build 1460481111 - [DEBUG] - nulecule/container.py - Creating docker container: /usr/bin/docker create --entrypoint /bin/true projectatomic/helloapache 1460481111 - [DEBUG] - nulecule/container.py - Copying data from Docker container: /usr/bin/docker cp 370386204f90cf23eb70e7ef723b5516ebc8cf3cf179b8439bc0de5d2d355348:/application-entity /tmp/nulecule-a616359a-00d1-11e6-88f5-002299c58402 1460481111 - [DEBUG] - nulecule/container.py - Copying nulecule data from /tmp/nulecule-a616359a-00d1-11e6-88f5-002299c58402 to build 1460481111 - [DEBUG] - nulecule/container.py - Removing tmp dir: /tmp/nulecule-a616359a-00d1-11e6-88f5-002299c58402 1460481111 - [DEBUG] - atomicapp/utils.py - Recursively removing directory: /tmp/nulecule-a616359a-00d1-11e6-88f5-002299c58402 1460481111 - [DEBUG] - nulecule/container.py - Removing Docker container: /usr/bin/docker rm -f 370386204f90cf23eb70e7ef723b5516ebc8cf3cf179b8439bc0de5d2d355348 370386204f90cf23eb70e7ef723b5516ebc8cf3cf179b8439bc0de5d2d355348 1460481114 - [DEBUG] - atomicapp/plugin.py - Loading providers from /opt/atomicapp/atomicapp/providers 1460481114 - [DEBUG] - atomicapp/plugin.py - Loading providers from /opt/atomicapp/atomicapp/providers 1460481114 - [DEBUG] - atomicapp/plugin.py - Found provider <class 'kubernetes.KubernetesProvider'> 1460481114 - [WARNING] - atomicapp/plugin.py - Configuration option 'provider-config' not found 1460481114 - [DEBUG] - atomicapp/plugin.py - Found provider <class 'kubernetes.KubernetesProvider'> 1460481114 - [WARNING] - atomicapp/plugin.py - Configuration option 'provider-config' not found 1460481114 - [DEBUG] - providers/kubernetes.py - Given config: {u'image': u'centos/httpd', u'hostport': 80, u'namespace': u'default', u'provider': u'kubernetes'} 1460481114 - [INFO] - providers/kubernetes.py - Using namespace default 1460481114 - [INFO] - providers/kubernetes.py - trying kubectl at /host/usr/bin/kubectl 1460481114 - [INFO] - providers/kubernetes.py - found kubectl at /host/usr/bin/kubectl 1460481114 - [INFO] - providers/kubernetes.py - Deploying to Kubernetes 1460481114 - [DEBUG] - providers/kubernetes.py - build/artifacts/kubernetes/.hello-apache-pod.json 1460481115 - [DEBUG] - atomicapp/utils.py - <<< stdout >>> <<< end >>> 1460481115 - [DEBUG] - atomicapp/utils.py - <<< stderr >>> Error from server: error when creating "build/artifacts/kubernetes/.hello-apache-pod.json": pods "helloapache" is forbidden: service account default/default was not found, retry after the service account is created <<< end >>> 1460481115 - [ERROR] - cli/main.py - cmd: ['/host/usr/bin/kubectl', 'create', '-f', u'build/artifacts/kubernetes/.hello-apache-pod.json', u'--namespace=default'] failed: Error from server: error when creating "build/artifacts/kubernetes/.hello-apache-pod.json": pods "helloapache" is forbidden: service account default/default was not found, retry after the service account is created Traceback (most recent call last): File "/opt/atomicapp/atomicapp/cli/main.py", line 119, in cli_func_exec cli_func(cli_func_args) File "/opt/atomicapp/atomicapp/cli/main.py", line 87, in cli_run nm.run(**argdict) File "/opt/atomicapp/atomicapp/nulecule/main.py", line 251, in run self.nulecule.run(cli_provider, dryrun) File "/opt/atomicapp/atomicapp/nulecule/base.py", line 205, in run component.run(provider_key, dryrun) File "/opt/atomicapp/atomicapp/nulecule/base.py", line 340, in run provider.run() File "/opt/atomicapp/atomicapp/providers/kubernetes.py", line 189, in run self._call(cmd) File "/opt/atomicapp/atomicapp/providers/kubernetes.py", line 114, in _call ec, stdout, stderr = Utils.run_cmd(cmd, checkexitcode=True) File "/opt/atomicapp/atomicapp/utils.py", line 266, in run_cmd "cmd: %s failed: \n%s" % (str(cmd), stderr)) AtomicAppUtilsException: cmd: ['/host/usr/bin/kubectl', 'create', '-f', u'build/artifacts/kubernetes/.hello-apache-pod.json', u'--namespace=default'] failed: Error from server: error when creating "build/artifacts/kubernetes/.hello-apache-pod.json": pods "helloapache" is forbidden: service account default/default was not found, retry after the service account is created make: *** [kubernetes] Error 1 Connection to n15.dusty.ci.centos.org closed. Running cmd: ssh -t -t -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no [email protected] "yum install -y git && mkdir /tmp/test && cd /tmp/test && git clone https://github.com/projectatomic/adb-tests.git . && /bin/bash -c 'cd cdrage-atomicapp-ci/functional-tests/ && make install kubernetes ATOMIC_SOURCE=rpm'" Done Build step 'Execute Python script' marked build as failure _______________________________________________ Container-tools mailing list [email protected] https://www.redhat.com/mailman/listinfo/container-tools
