Project

Profile

Help

Task #6898

cp: cannot stat ���/home/vagrant/cnf_templates/server4.cnf���: No such file or directory

Added by Mark Zaslavskiy over 5 years ago. Updated over 5 years ago.

Status:
Duplicated
Priority:
Normal
Category:
mdbci testing
Sprint/Milestone:
Start date:
17.03.2016
Due date:
% Done:

0%

Estimated time:
Target branch:
Test scenario:

Description

http://max-tst-01.mariadb.com:8089/job/run_test/824/console

> node3: STDOUT:
> node3: STDERR: cp: cannot stat ���/home/vagrant/cnf_templates/server4.cnf���: No such file or directory
> node3: ---- End output of cp /home/vagrant/cnf_templates/server4.cnf /etc/my.cnf.d/ ----
> node3: Ran cp /home/vagrant/cnf_templates/server4.cnf /etc/my.cnf.d/ returned 1
==> node3: [2016-03-16T12:44:24-04:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
INFO: Checking for all nodes to be started
INFO: Checking Chef log for failed nodes
INFO: Checking for all nodes to be started
INFO: Checking Chef log for failed nodes
INFO: Checking for all nodes to be started
INFO: Checking Chef log for failed nodes
ERROR: Bringing up failed
INFO: Failed Chef nodes:
INFO: node3
ERROR: /home/vagrant/mdbci/core/session.rb:608:in `block (2 levels) in up'
/usr/lib/ruby/1.9.1/open3.rb:208:in `popen_run'
/usr/lib/ruby/1.9.1/open3.rb:90:in `popen3'
/home/vagrant/mdbci/core/session.rb:565:in `block in up'
/home/vagrant/mdbci/core/session.rb:547:in `each'
/home/vagrant/mdbci/core/session.rb:547:in `up'
/home/vagrant/mdbci/core/session.rb:411:in `commands'
./mdbci:112:in `<main>'
ERROR: Some machines are still down or Chef provision failed! Check failed Chef nodes!

History

#1 Updated by Timofey Turenko over 5 years ago

one more log:

http://max-tst-01.mariadb.com:8089/job/run_test_regular/backend=mariadb-5.5,box=sles_12_aws/41/consoleFull

 INFO:      node3: Installing Chef (latest)...
ERROR:  Bringing up failed
ERROR:  /home/vagrant/.vagrant.d/gems/gems/vagrant-aws-0.7.0/lib/vagrant-aws/action/run_instance.rb:98: warning: duplicated key at line 100 ignored: :associate_public_ip
ERROR:  The following SSH command responded with a non-zero exit status.
ERROR:  Vagrant assumes that this means the command failed!
ERROR:  
ERROR:  yum install -y -q curl
ERROR:  
ERROR:  Stdout from the command:
ERROR:  
ERROR:  Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=extras&infra=stock error was
ERROR:  12: Timeout on http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=extras&infra=stock: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
ERROR:  
ERROR:  
ERROR:  Stderr from the command:
ERROR:  
ERROR:  
ERROR:  
ERROR:   One of the configured repositories failed (Unknown),
ERROR:   and yum doesn't have enough cached data to continue. At this point the only
ERROR:   safe thing yum can do is fail. There are a few ways to work "fix" this:
ERROR:  
ERROR:       1. Contact the upstream for the repository and get them to fix the problem.
ERROR:  
ERROR:       2. Reconfigure the baseurl/etc. for the repository, to point to a working
ERROR:          upstream. This is most often useful if you are using a newer
ERROR:          distribution release than is supported by the repository (and the
ERROR:          packages for the previous distribution release still work).
ERROR:  
ERROR:       3. Disable the repository, so yum won't use it by default. Yum will then
ERROR:          just ignore the repository until you permanently enable it again or use
ERROR:          --enablerepo for temporary usage:
ERROR:  
ERROR:              yum-config-manager --disable <repoid>
ERROR:  
ERROR:       4. Configure the failing repository to be skipped, if it is unavailable.
ERROR:          Note that yum will try to contact the repo. when it runs most commands,
ERROR:          so will have to try and fail each time (and thus. yum will be be much
ERROR:          slower). If it is a very temporary problem though, this is often a nice
ERROR:          compromise:
ERROR:  
ERROR:              yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
ERROR:  
ERROR:  Cannot find a valid baseurl for repo: extras/7/x86_64
ERROR:  exit code 1
 INFO:  Checking for all nodes to be started
ERROR:  Machine maxscale isn't in 'running' state
 INFO:  Checking Chef log for failed nodes
 INFO:  Checking for all nodes to be started
 INFO:  Checking Chef log for failed nodes
 INFO:  Checking for all nodes to be started
ERROR:  Machine galera3 isn't in 'running' state
 INFO:  Checking Chef log for failed nodes
 INFO:  Checking for all nodes to be started
 INFO:  Checking Chef log for failed nodes
 INFO:  Checking for all nodes to be started
 INFO:  Checking Chef log for failed nodes
 INFO:  Checking for all nodes to be started
 INFO:  Checking Chef log for failed nodes
 INFO:  Checking for all nodes to be started
ERROR:  Machine galera2 isn't in 'running' state
 INFO:  Checking Chef log for failed nodes
 INFO:  Checking for all nodes to be started
ERROR:  Machine galera1 isn't in 'running' state
 INFO:  Checking Chef log for failed nodes
 INFO:  Checking for all nodes to be started
ERROR:  Machine galera0 isn't in 'running' state
 INFO:  Checking Chef log for failed nodes
ERROR:  Bringing up failed
 INFO:  Failed Chef nodes:
ERROR:  /home/vagrant/mdbci/core/session.rb:608:in `block (2 levels) in up'
/usr/lib/ruby/1.9.1/open3.rb:208:in `popen_run'
/usr/lib/ruby/1.9.1/open3.rb:90:in `popen3'
/home/vagrant/mdbci/core/session.rb:565:in `block in up'
/home/vagrant/mdbci/core/session.rb:547:in `each'
/home/vagrant/mdbci/core/session.rb:547:in `up'
/home/vagrant/mdbci/core/session.rb:411:in `commands'
./mdbci:112:in `<main>'
ERROR:  Some machines are still down or Chef provision failed! Check failed Chef nodes!

#2 Updated by Alexander Kaluzhny over 5 years ago

  • Status changed from New to Active / In progress

#3 Updated by Mark Zaslavskiy over 5 years ago

  • Assignee changed from Alexander Kaluzhny to Mark Zaslavskiy

#4 Updated by Mark Zaslavskiy over 5 years ago

  • Status changed from Active / In progress to New

#5 Updated by Mark Zaslavskiy over 5 years ago

  • Status changed from New to Duplicated

Also available in: Atom PDF