Project

Profile

Help

Bug #6638

CentOS6 QEMU box does not work

Added by Timofey Turenko over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Immediate
Category:
-
Sprint/Milestone:
Start date:
19.01.2016
Due date:
23.01.2016
% Done:

100%

Estimated time:
Target branch:
Test scenario:

Description

Template:

{
"cookbook_path" : "../recipes/cookbooks/",
"build" : {
"hostname" : "default",
"box" : "centos_6.5_libvirt",
"product" : {
"name" : "packages"
}
}
}

Box:

"centos_6.5_libvirt": {
"provider": "libvirt",
"box": "dliappis/centos65minlibvirt",
"platform": "centos",
"platform_version": "6"
}

Error:

vagrant@ns3014560:~/mdbci$ ./mdbci up cenots6_vm03
INFO: MariaDb CI CLI
INFO: mdbci called with: ["up", "cenots6_vm03"]
INFO: Checking this machine configuration requirments
INFO: .....NOT IMPLEMENTED YET
INFO: Load Boxes from ./BOXES
INFO: Loaded boxes: 37
INFO: Load AWS config from aws-config.yml
INFO: Load Repos from ./repo.d
INFO: Looking up for repos ./repo.d
INFO: Loaded repos: 749
INFO: Node isn't specified in cenots6_vm03
INFO: Current provider: libvirt
INFO: Bringing up configuration cenots6_vm03, attempt: 1
INFO: Destroying current instance
INFO: > build: Remove stale volume...
> build: Domain is not created. Please run `vagrant up` first.
INFO: Actual command: vagrant up --destroy-on-error --provider=libvirt
INFO: Bringing machine 'build' up with 'libvirt' provider...
INFO: > build: Creating image (snapshot of base box volume).
INFO: > build: Creating domain with the following settings...
INFO: > build: -- Name: cenots6_vm03_build
INFO: > build: -- Domain type: kvm
INFO: > build: -- Cpus: 1
INFO: > build: -- Memory: 512M
INFO: > build: -- Management MAC:
INFO: > build: -- Loader:
INFO: > build: -- Base box: dliappis/centos65minlibvirt
INFO: > build: -- Storage pool: default
INFO: > build: -- Image: /var/lib/libvirt/images/cenots6_vm03_build.img (40G)
INFO: > build: -- Volume Cache: default
INFO: > build: -- Kernel:
INFO: > build: -- Initrd:
INFO: > build: -- Graphics Type: vnc
INFO: > build: -- Graphics Port: 5900
INFO: > build: -- Graphics IP: 127.0.0.1
INFO: > build: -- Graphics Password: Not defined
INFO: > build: -- Video Type: cirrus
INFO: > build: -- Video VRAM: 9216
INFO: > build: -- Keymap: en-us
INFO: > build: -- INPUT: type=mouse, bus=ps2
INFO: > build: -- Command line :
INFO: > build: Creating shared folders metadata...
INFO: > build: Starting domain.
INFO: > build: Waiting for domain to get an IP address...
INFO: > build: Waiting for SSH to become available...
INFO: build:
INFO: build: Vagrant insecure key detected. Vagrant will automatically replace
INFO: build: this with a newly generated keypair for better security.
INFO: build:
INFO: build: Inserting generated public key within guest...
INFO: build: Removing insecure key from the guest if its present...
INFO: build: Key inserted! Disconnecting and reconnecting using new SSH key...
INFO: > build: Setting hostname...
INFO: > build: Configuring and enabling network interfaces...
INFO: > build: Rsyncing folder: /home/vagrant/mdbci/cenots6_vm03/ => /vagrant
INFO: ==> build: Rsyncing folder: /home/vagrant/mdbci/recipes/cookbooks/ => /tmp/vagrant-chef/5647e9fbc8a74e8fe1cfa518d9f38f42/cookbooks
INFO: ==> build: Rsyncing folder: /home/vagrant/mdbci/cenots6_vm03/ => /tmp/vagrant-chef/83d9ade55b331a8575c611af5d776c78/roles
INFO: > build: Running provisioner: chef_solo...
INFO: build: Installing Chef (latest)...
ERROR: Bringing up failed
ERROR: The following SSH command responded with a non-zero exit status.
ERROR: Vagrant assumes that this means the command failed!
ERROR:
ERROR: curl -sL https://www.chef.io/chef/install.sh | sudo bash
ERROR:
ERROR: Stdout from the command:
ERROR:
ERROR:
ERROR:
ERROR: Stderr from the command:
ERROR:
ERROR: sudo: sorry, you must have a tty to run sudo
INFO: UP ERROR, exit code 1
INFO: Bringing up configuration cenots6_vm03, attempt: 2
INFO: Destroying current instance
INFO: > build: Removing domain...
==> build: Running cleanup tasks for 'chef_solo' provisioner...


Related issues

Related to [mdbci] Maria DB Continuous integration tool - Bug #6655: Implement ifconfig IP address parsing without platformClosed26.01.201627.01.2016

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by Kirill Yudenok over 4 years ago

  • Status changed from New to Assigned
  • Assignee set to Kirill Yudenok

#2 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Assigned to Active / In progress

#3 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Active / In progress to Resolved
  • % Done changed from 0 to 100
  • fix for libvirt centos 6 and 7 boxes in 6638_libvirt_centos_fix branch
  • other providers works fine without config.ssh.pty = true option
  • vbox and libvirt ubuntu trusty box fail with config.ssh.pty = true option

#4 Updated by Timofey Turenko over 4 years ago

should config.ssh.pty be a part of box definition?

false by default, but it can be redefined in boxes,json for certain boxes

#5 Updated by Kirill Yudenok over 4 years ago

  • I think, it is not necessary to add this option to the boxes file, because, this option is not required for all boxes.
  • Or we may add this option to the boxes, that couldn't launch without it.

#6 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Resolved to Reopened

#7 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Reopened to Active / In progress

#8 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Active / In progress to Testing
  • Assignee changed from Kirill Yudenok to Timofey Turenko
  • implement new ssh_pty option in boxes json
  • add this to libvirt centos6.5 & 7.0 boxes
  • branch: 6638_libvirt_centos_fix

#9 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Testing to Pull request
  • Assignee changed from Timofey Turenko to Alexander Kaluzhny

#10 Updated by Kirill Yudenok over 4 years ago

  • Due date set to 23.01.2016
  • after code review, check with Jenkins

#11 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Pull request to Ask for information
  • Assignee changed from Alexander Kaluzhny to Timofey Turenko

#12 Updated by Timofey Turenko over 4 years ago

  • Status changed from Ask for information to Pull request

I restarted test run and result was ok. Probably there was random VBox failure during http://maxscale-jenkins.mariadb.com:8090/job/mdbci_integration_test/82/consoleFull

New test run: http://maxscale-jenkins.mariadb.com:8090/job/mdbci_integration_test/87/console

'longblob' test is expected to fail due to https://mariadb.atlassian.net/browse/MXS-300 . Please remove this test from test runs.

#13 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Pull request to Ask for information

#14 Updated by Timofey Turenko over 4 years ago

  • Status changed from Ask for information to Active / In progress

Variable 'test_set' is responsible for defining list of tests to be executed.

Variable is defined here
http://maxscale-jenkins.mariadb.com:8090/job/mdbci_integration_test/configure

I recopmmend to use test_set="15,16" to execute:
Test #15: server_weight
Test #16: slave_failover

Unfortunately latest maxscale-system-test package refactoring caused changing of all test numbers.
To see all tests and their number please use 'ctest -N' in the maxscale-system-tests source directory.

#15 Updated by Kirill Yudenok over 4 years ago

Ok, thanks. What about 4,5,,10 test sets or they must be changed to 14,15 set only?

#16 Updated by Timofey Turenko over 4 years ago

just change to 14,15

#17 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Active / In progress to Testing

#18 Updated by Timofey Turenko over 4 years ago

  • Status changed from Testing to Reopened

tried master + 6638 + 6652

+ ./mdbci show network build_centos_6.5_libvirt-20160125-2336/build --silent
export IP=addr:192.168.121.119
+ IP=addr:192.168.121.119

http://max-tst-01.mariadb.com:8089/job/build/473/console

#19 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Reopened to Active / In progress
  • Is it a max-tst-01.mariadb.com server?
  • Master is very old! I am pull it.
vagranttest@ns3014560:~/mdbci$ git checkout master
Switched to branch 'master'
Your branch is behind 'origin/master' by 97 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)
  • this error is already fixed!

#20 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Active / In progress to Ask for information

#21 Updated by Timofey Turenko over 4 years ago

Master was updated Jan 18.

Author: Kirill Krinkin <>
Date: Mon Jan 18 19:50:50 2016 +0300

Merge pull request #64 from OSLL/integration
Integration -> master

vagrant@ns3014560:~/mdbci$ ./mdbci show network build_centos_6.5_libvirt-20160126-0627
INFO: MariaDb CI CLI
INFO: mdbci called with: ["show", "network", "build_centos_6.5_libvirt-20160126-0627"]
INFO: Checking this machine configuration requirments
INFO: .....NOT IMPLEMENTED YET
INFO: Load Boxes from ./BOXES
INFO: Loaded boxes: 36
INFO: Load AWS config from aws-config.yml
INFO: Load Repos from ./repo.d
INFO: Looking up for repos ./repo.d
INFO: Loaded repos: 749
INFO: Load configuration nodes from vagrant status ...
Connection to 192.168.121.72 closed.
INFO: Node.GetIp vagrant ssh build -c "/sbin/ifconfig eth0 | grep \"inet \" "
INFO: IP:addr:192.168.121.72
addr:192.168.121.72

I reopened 6627

#22 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Ask for information to Active / In progress
  • master updated in github, but not updated ~/mdbci repo at server max-tst-01
vagranttest@ns3014560:~/mdbci$ ./mdbci show network libvirt_debian_network/
 INFO:  MariaDb CI CLI
 INFO:  mdbci called with: ["show", "network", "libvirt_debian_network/"]
 INFO:  Checking this machine configuration requirments
 INFO:  .....NOT IMPLEMENTED YET
 INFO:  Load Boxes from ./BOXES
 INFO:  Loaded boxes: 30
 INFO:  Load AWS config from aws-config.yml
 INFO:  Load Repos from ./repo.d
 INFO:  Looking up for repos ./repo.d
 INFO:  Loaded repos: 749
 INFO:  Load configuration nodes from vagrant status ...
Connection to 192.168.121.244 closed.
 INFO:  Node.GetIp vagrant ssh node0 -c "/sbin/ifconfig eth0 | grep \"inet \" " 
 INFO:  IP:192.168.121.244
192.168.121.244
vagranttest@ns3014560:~/mdbci$ ./mdbci show network libvirt-11.12/
 INFO:  MariaDb CI CLI
 INFO:  mdbci called with: ["show", "network", "libvirt-11.12/"]
 INFO:  Checking this machine configuration requirments
 INFO:  .....NOT IMPLEMENTED YET
 INFO:  Load Boxes from ./BOXES
 INFO:  Loaded boxes: 30
 INFO:  Load AWS config from aws-config.yml
 INFO:  Load Repos from ./repo.d
 INFO:  Looking up for repos ./repo.d
 INFO:  Loaded repos: 749
 INFO:  Load configuration nodes from vagrant status ...
Connection to 192.168.121.96 closed.
 INFO:  Node.GetIp vagrant ssh build -c "/sbin/ifconfig eth0 | grep \"inet \" " 
 INFO:  IP:192.168.121.96
192.168.121.96

#23 Updated by Kirill Yudenok over 4 years ago

  • Related to Bug #6655: Implement ifconfig IP address parsing without platform added

#24 Updated by Timofey Turenko over 4 years ago

  • Assignee changed from Timofey Turenko to Kirill Yudenok

#25 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Active / In progress to Testing
  • Assignee changed from Kirill Yudenok to Timofey Turenko

#26 Updated by Timofey Turenko over 4 years ago

  • Status changed from Testing to Pull request
  • Assignee changed from Timofey Turenko to Kirill Krinkin

works, please integrate

#27 Updated by Timofey Turenko over 4 years ago

it was tested together with 6655

#28 Updated by Kirill Yudenok over 4 years ago

  • Status changed from Pull request to Closed

Also available in: Atom PDF