FailedConsole Output

Started by timer
[EnvInject] - Loading node environment variables.
Building in workspace /var/lib/jenkins/jobs/push_images_s2i/workspace
[workspace] $ /bin/sh -xe /tmp/jenkins7833521405804867715.sh
+ set +x
Not found: ~/.latest_images_s2i

Detected update in https://github.com/openshift/openldap, rebuilding openldap-2441


Building openshift;openshift;openldap-2441;2.4.41;https://github.com/openshift/openldap;443bade

+ vagrant origin-local-checkout --replace
You don't seem to have the GOPATH environment variable set on your system.
See: 'go help gopath' for more details about GOPATH.
Waiting for the cloning process to finish
Checking repo integrity for /var/lib/jenkins/jobs/push_images_s2i/workspace/origin
~/jobs/push_images_s2i/workspace/origin ~/jobs/push_images_s2i/workspace
# On branch master
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#	launched
nothing added to commit but untracked files present (use "git add" to track)
~/jobs/push_images_s2i/workspace
Replacing: /var/lib/jenkins/jobs/push_images_s2i/workspace/origin
~/jobs/push_images_s2i/workspace/origin ~/jobs/push_images_s2i/workspace
Already on 'master'
HEAD is now at d0eff76 Merge pull request #19578 from danwinship/auto-egress-ip-ha
Removing .vagrant-openshift.json
Removing .vagrant/
Removing launched
fatal: branch name required
~/jobs/push_images_s2i/workspace
Origin repositories cloned into /var/lib/jenkins/jobs/push_images_s2i/workspace
+ pushd origin
~/jobs/push_images_s2i/workspace/origin ~/jobs/push_images_s2i/workspace
+ vagrant origin-init --stage inst --os rhel7 --instance-type c4.large --volume-size 25 origin_push_images_s2i_19452
Reading AWS credentials from /var/lib/jenkins/.awscred
Searching devenv-rhel7_* for latest base AMI (required_name_tag=)
Found: ami-83a1fc95 (devenv-rhel7_6323)
+ touch launched
++ seq 0 2
+ for i in '$(seq 0 2)'
+ vagrant up --provider aws
Bringing machine 'openshiftdev' up with 'aws' provider...
==> openshiftdev: Warning! The AWS provider doesn't support any of the Vagrant
==> openshiftdev: high-level network configurations (`config.vm.network`). They
==> openshiftdev: will be silently ignored.
==> openshiftdev: Warning! You're launching this instance into a VPC without an
==> openshiftdev: elastic IP. Please verify you're properly connected to a VPN so
==> openshiftdev: you can access this machine, otherwise Vagrant will not be able
==> openshiftdev: to SSH into it.
==> openshiftdev: Launching an instance with the following settings...
==> openshiftdev:  -- Type: c4.large
==> openshiftdev:  -- AMI: ami-83a1fc95
==> openshiftdev:  -- Region: us-east-1
==> openshiftdev:  -- Keypair: libra
==> openshiftdev:  -- Subnet ID: subnet-cf57c596
==> openshiftdev:  -- User Data: yes
==> openshiftdev:  -- User Data: 
==> openshiftdev: # cloud-config
==> openshiftdev: 
==> openshiftdev: growpart:
==> openshiftdev:   mode: auto
==> openshiftdev:   devices: ['/']
==> openshiftdev: runcmd:
==> openshiftdev: - [ sh, -xc, "sed -i s/^Defaults.*requiretty/#Defaults requiretty/g /etc/sudoers"]
==> openshiftdev:         
==> openshiftdev:  -- Block Device Mapping: [{"DeviceName"=>"/dev/sda1", "Ebs.VolumeSize"=>25, "Ebs.VolumeType"=>"gp2"}, {"DeviceName"=>"/dev/sdb", "Ebs.VolumeSize"=>35, "Ebs.VolumeType"=>"gp2"}]
==> openshiftdev:  -- Terminate On Shutdown: false
==> openshiftdev:  -- Monitoring: false
==> openshiftdev:  -- EBS optimized: false
==> openshiftdev:  -- Assigning a public IP address in a VPC: false
There was an error talking to AWS. The error message is shown
below:

InternalError => An internal error has occurred
+ echo ''\''vagrant up'\'' failed - retrying'
'vagrant up' failed - retrying
+ vagrant destroy -f
==> openshiftdev: Instance is not created. Please run `vagrant up` first.
+ for i in '$(seq 0 2)'
+ vagrant up --provider aws
Bringing machine 'openshiftdev' up with 'aws' provider...
==> openshiftdev: Warning! The AWS provider doesn't support any of the Vagrant
==> openshiftdev: high-level network configurations (`config.vm.network`). They
==> openshiftdev: will be silently ignored.
==> openshiftdev: Warning! You're launching this instance into a VPC without an
==> openshiftdev: elastic IP. Please verify you're properly connected to a VPN so
==> openshiftdev: you can access this machine, otherwise Vagrant will not be able
==> openshiftdev: to SSH into it.
==> openshiftdev: Launching an instance with the following settings...
==> openshiftdev:  -- Type: c4.large
==> openshiftdev:  -- AMI: ami-83a1fc95
==> openshiftdev:  -- Region: us-east-1
==> openshiftdev:  -- Keypair: libra
==> openshiftdev:  -- Subnet ID: subnet-cf57c596
==> openshiftdev:  -- User Data: yes
==> openshiftdev:  -- User Data: 
==> openshiftdev: # cloud-config
==> openshiftdev: 
==> openshiftdev: growpart:
==> openshiftdev:   mode: auto
==> openshiftdev:   devices: ['/']
==> openshiftdev: runcmd:
==> openshiftdev: - [ sh, -xc, "sed -i s/^Defaults.*requiretty/#Defaults requiretty/g /etc/sudoers"]
==> openshiftdev:         
==> openshiftdev:  -- Block Device Mapping: [{"DeviceName"=>"/dev/sda1", "Ebs.VolumeSize"=>25, "Ebs.VolumeType"=>"gp2"}, {"DeviceName"=>"/dev/sdb", "Ebs.VolumeSize"=>35, "Ebs.VolumeType"=>"gp2"}]
==> openshiftdev:  -- Terminate On Shutdown: false
==> openshiftdev:  -- Monitoring: false
==> openshiftdev:  -- EBS optimized: false
==> openshiftdev:  -- Assigning a public IP address in a VPC: false
There was an error talking to AWS. The error message is shown
below:

InternalError => An internal error has occurred
+ echo ''\''vagrant up'\'' failed - retrying'
'vagrant up' failed - retrying
+ vagrant destroy -f
==> openshiftdev: Instance is not created. Please run `vagrant up` first.
+ for i in '$(seq 0 2)'
+ vagrant up --provider aws
Bringing machine 'openshiftdev' up with 'aws' provider...
==> openshiftdev: Warning! The AWS provider doesn't support any of the Vagrant
==> openshiftdev: high-level network configurations (`config.vm.network`). They
==> openshiftdev: will be silently ignored.
==> openshiftdev: Warning! You're launching this instance into a VPC without an
==> openshiftdev: elastic IP. Please verify you're properly connected to a VPN so
==> openshiftdev: you can access this machine, otherwise Vagrant will not be able
==> openshiftdev: to SSH into it.
==> openshiftdev: Launching an instance with the following settings...
==> openshiftdev:  -- Type: c4.large
==> openshiftdev:  -- AMI: ami-83a1fc95
==> openshiftdev:  -- Region: us-east-1
==> openshiftdev:  -- Keypair: libra
==> openshiftdev:  -- Subnet ID: subnet-cf57c596
==> openshiftdev:  -- User Data: yes
==> openshiftdev:  -- User Data: 
==> openshiftdev: # cloud-config
==> openshiftdev: 
==> openshiftdev: growpart:
==> openshiftdev:   mode: auto
==> openshiftdev:   devices: ['/']
==> openshiftdev: runcmd:
==> openshiftdev: - [ sh, -xc, "sed -i s/^Defaults.*requiretty/#Defaults requiretty/g /etc/sudoers"]
==> openshiftdev:         
==> openshiftdev:  -- Block Device Mapping: [{"DeviceName"=>"/dev/sda1", "Ebs.VolumeSize"=>25, "Ebs.VolumeType"=>"gp2"}, {"DeviceName"=>"/dev/sdb", "Ebs.VolumeSize"=>35, "Ebs.VolumeType"=>"gp2"}]
==> openshiftdev:  -- Terminate On Shutdown: false
==> openshiftdev:  -- Monitoring: false
==> openshiftdev:  -- EBS optimized: false
==> openshiftdev:  -- Assigning a public IP address in a VPC: false
There was an error talking to AWS. The error message is shown
below:

InternalError => An internal error has occurred
+ echo ''\''vagrant up'\'' failed - retrying'
'vagrant up' failed - retrying
+ vagrant destroy -f
==> openshiftdev: Instance is not created. Please run `vagrant up` first.
+ vagrant ssh -c 'sudo pvresize /dev/xvdb'
==> openshiftdev: Instance is not created. Please run `vagrant up` first.
+ cat /var/lib/jenkins/.dockercfg
+ vagrant ssh -c 'cat > ~/.dockercfg'
==> openshiftdev: Instance is not created. Please run `vagrant up` first.
+ set -e
+ vagrant push-openshift-images --registry=ci.dev.openshift.redhat.com:5000 '--build_images=openshift;openshift;openldap-2441;2.4.41;https://github.com/openshift/openldap;443bade' '--check_images=,openshift;openshift;openldap-2441;2.4.41;https://github.com/openshift/openldap;443bade'
Running ssh/sudo command '
sudo chmod a+rw /etc/sysconfig/docker
cat <<EOF > /etc/sysconfig/docker
OPTIONS='--insecure-registry ci.dev.openshift.redhat.com:5000 --selinux-enabled --skip-schema2-push'
EOF
sudo systemctl restart docker
          
set -x
set +e
echo "Pre-pulling base images ..."
docker pull ci.dev.openshift.redhat.com:5000/openshift/base-centos7
[[ "$?" == "0" ]] && docker tag ci.dev.openshift.redhat.com:5000/openshift/base-centos7 openshift/base-centos7
docker pull ci.dev.openshift.redhat.com:5000/openshift/base-rhel7
[[ "$?" == "0" ]] && docker tag ci.dev.openshift.redhat.com:5000/openshift/base-rhel7 openshift/base-rhel7
          
# so we can call s2i
export PATH=/data/src/github.com/openshift/source-to-image/_output/local/go/bin:/data/src/github.com/openshift/source-to-image/_output/local/bin/linux/amd64:$PATH
          
dest_dir=/tmp/images/openldap-2441
rm -rf ${dest_dir}; mkdir -p ${dest_dir}
set -e
pushd ${dest_dir}
git init && git remote add -t master origin https://github.com/openshift/openldap
git fetch && git checkout 443bade
git_ref=$(git rev-parse --short HEAD)
echo "Building and testing openldap-2441-centos7:$git_ref ..."
sudo env "PATH=$PATH" SKIP_SQUASH=1 make test TARGET=centos7 VERSION=2.4.41 TAG_ON_SUCCESS=true
echo "Building and testing openldap-2441-rhel7:$git_ref ..."
sudo env "PATH=$PATH" SKIP_SQUASH=1 SKIP_RHEL_SCL=1 make test TARGET=rhel7 VERSION=2.4.41 TAG_ON_SUCCESS=true

popd
set +e
          
set -e
pushd /tmp/images/openldap-2441
git checkout 443bade
git_ref=$(git rev-parse --short HEAD)
echo "Pushing image openldap-2441:443bade..."

docker tag openshift/openldap-2441-centos7 ci.dev.openshift.redhat.com:5000/openshift/openldap-2441-centos7:443bade
docker tag openshift/openldap-2441-centos7 ci.dev.openshift.redhat.com:5000/openshift/openldap-2441-centos7:latest
docker tag openshift/openldap-2441-centos7 docker.io/openshift/openldap-2441-centos7:latest

# We can't fully parallelize this because docker fails when you push to the same repo at the
# same time (using different tags), so we do two groups of push operations.
procs[0]="docker push ci.dev.openshift.redhat.com:5000/openshift/openldap-2441-centos7:443bade"
procs[1]="docker push docker.io/openshift/openldap-2441-centos7:latest"

# Run pushes in parallel
for i in {0..1}; do
  echo "pushing ${procs[${i}]}"
  ${procs[${i}]} &
  pids[${i}]=$!
  echo "push ${procs[${i}]} is pid ${pids[${i}]}"
done

# Wait for all pushes.  "wait" will check the return code of each process also.
for pid in ${pids[*]}; do
  echo "checking $pid"
  wait $pid
done

docker push ci.dev.openshift.redhat.com:5000/openshift/openldap-2441-centos7:latest

if [ openshift != "SKIP" ]; then
  docker tag openshift/openldap-2441-rhel7 ci.dev.openshift.redhat.com:5000/openshift/openldap-2441-rhel7:443bade
  docker tag openshift/openldap-2441-rhel7 ci.dev.openshift.redhat.com:5000/openshift/openldap-2441-rhel7:latest

  # this one is failing when done in parallel for unknown reasons
  docker push ci.dev.openshift.redhat.com:5000/openshift/openldap-2441-rhel7:443bade
  docker push ci.dev.openshift.redhat.com:5000/openshift/openldap-2441-rhel7:latest
fi

popd
set +e
          
        set +e
        rm -rf ~/latest_images ; touch ~/latest_images
          
git_ref=$(git ls-remote  -h refs/heads/master | cut -c1-7)
curl -s http://ci.dev.openshift.redhat.com:5000/v1/repositories//-centos7/tags/${git_ref} | grep -q "error"
if [[ "$?" != "0" ]]; then
  echo ";$git_ref" >> ~/latest_images
fi
            
git_ref=$(git ls-remote https://github.com/openshift/openldap -h refs/heads/master | cut -c1-7)
curl -s http://ci.dev.openshift.redhat.com:5000/v1/repositories/openshift/openldap-2441-centos7/tags/${git_ref} | grep -q "error"
if [[ "$?" != "0" ]]; then
  echo "openldap-2441;$git_ref" >> ~/latest_images
fi
            ' with timeout 18000. Attempt #0
Error while running ssh/sudo command: 
sudo chmod a+rw /etc/sysconfig/docker
cat <<EOF > /etc/sysconfig/docker
OPTIONS='--insecure-registry ci.dev.openshift.redhat.com:5000 --selinux-enabled --skip-schema2-push'
EOF
sudo systemctl restart docker
          
set -x
set +e
echo "Pre-pulling base images ..."
docker pull ci.dev.openshift.redhat.com:5000/openshift/base-centos7
[[ "$?" == "0" ]] && docker tag ci.dev.openshift.redhat.com:5000/openshift/base-centos7 openshift/base-centos7
docker pull ci.dev.openshift.redhat.com:5000/openshift/base-rhel7
[[ "$?" == "0" ]] && docker tag ci.dev.openshift.redhat.com:5000/openshift/base-rhel7 openshift/base-rhel7
          
# so we can call s2i
export PATH=/data/src/github.com/openshift/source-to-image/_output/local/go/bin:/data/src/github.com/openshift/source-to-image/_output/local/bin/linux/amd64:$PATH
          
dest_dir=/tmp/images/openldap-2441
rm -rf ${dest_dir}; mkdir -p ${dest_dir}
set -e
pushd ${dest_dir}
git init && git remote add -t master origin https://github.com/openshift/openldap
git fetch && git checkout 443bade
git_ref=$(git rev-parse --short HEAD)
echo "Building and testing openldap-2441-centos7:$git_ref ..."
sudo env "PATH=$PATH" SKIP_SQUASH=1 make test TARGET=centos7 VERSION=2.4.41 TAG_ON_SUCCESS=true
echo "Building and testing openldap-2441-rhel7:$git_ref ..."
sudo env "PATH=$PATH" SKIP_SQUASH=1 SKIP_RHEL_SCL=1 make test TARGET=rhel7 VERSION=2.4.41 TAG_ON_SUCCESS=true

popd
set +e
          
set -e
pushd /tmp/images/openldap-2441
git checkout 443bade
git_ref=$(git rev-parse --short HEAD)
echo "Pushing image openldap-2441:443bade..."

docker tag openshift/openldap-2441-centos7 ci.dev.openshift.redhat.com:5000/openshift/openldap-2441-centos7:443bade
docker tag openshift/openldap-2441-centos7 ci.dev.openshift.redhat.com:5000/openshift/openldap-2441-centos7:latest
docker tag openshift/openldap-2441-centos7 docker.io/openshift/openldap-2441-centos7:latest

# We can't fully parallelize this because docker fails when you push to the same repo at the
# same time (using different tags), so we do two groups of push operations.
procs[0]="docker push ci.dev.openshift.redhat.com:5000/openshift/openldap-2441-centos7:443bade"
procs[1]="docker push docker.io/openshift/openldap-2441-centos7:latest"

# Run pushes in parallel
for i in {0..1}; do
  echo "pushing ${procs[${i}]}"
  ${procs[${i}]} &
  pids[${i}]=$!
  echo "push ${procs[${i}]} is pid ${pids[${i}]}"
done

# Wait for all pushes.  "wait" will check the return code of each process also.
for pid in ${pids[*]}; do
  echo "checking $pid"
  wait $pid
done

docker push ci.dev.openshift.redhat.com:5000/openshift/openldap-2441-centos7:latest

if [ openshift != "SKIP" ]; then
  docker tag openshift/openldap-2441-rhel7 ci.dev.openshift.redhat.com:5000/openshift/openldap-2441-rhel7:443bade
  docker tag openshift/openldap-2441-rhel7 ci.dev.openshift.redhat.com:5000/openshift/openldap-2441-rhel7:latest

  # this one is failing when done in parallel for unknown reasons
  docker push ci.dev.openshift.redhat.com:5000/openshift/openldap-2441-rhel7:443bade
  docker push ci.dev.openshift.redhat.com:5000/openshift/openldap-2441-rhel7:latest
fi

popd
set +e
          
        set +e
        rm -rf ~/latest_images ; touch ~/latest_images
          
git_ref=$(git ls-remote  -h refs/heads/master | cut -c1-7)
curl -s http://ci.dev.openshift.redhat.com:5000/v1/repositories//-centos7/tags/${git_ref} | grep -q "error"
if [[ "$?" != "0" ]]; then
  echo ";$git_ref" >> ~/latest_images
fi
            
git_ref=$(git ls-remote https://github.com/openshift/openldap -h refs/heads/master | cut -c1-7)
curl -s http://ci.dev.openshift.redhat.com:5000/v1/repositories/openshift/openldap-2441-centos7/tags/${git_ref} | grep -q "error"
if [[ "$?" != "0" ]]; then
  echo "openldap-2441;$git_ref" >> ~/latest_images
fi
            
The provider for this Vagrant-managed machine is reporting that it
is not yet ready for SSH. Depending on your provider this can carry
different meanings. Make sure your machine is created and running and
try again. Additionally, check the output of `vagrant status` to verify
that the machine is in the state that you expect. If you continue to
get this error message, please view the documentation for the provider
you're using.
Build step 'Execute shell' marked build as failure
[PostBuildScript] - Executing post build scripts.
[PostBuildScript] - Build does not have any of the results []. Did not execute build step #0.
Sending e-mails to: bparees@redhat.com
[BFA] Scanning build for known causes...
[BFA] Found failure cause(s):
[BFA] AWS Failure from category infrastructure
[BFA] Done. 0s
Finished: FAILURE