From Fedora Project Wiki

No edit summary
No edit summary
 
(25 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Category:Package vzctl test cases]]
[[Category:Package vzctl test cases]]
{{QA/Test_Case
{{QA/Test_Case
|description=A brief description of the functionality being tested.
|description=Basic tests for OpenVZ Linux Containers and Checkpoint/Restore In Userspace (CRIU)
==Known issues==
* criu: command not found
** On not x8_64 arches CRIU not working. Work in progress.
* Problems with SELinux
** Temporary fix: <code>setenforce 0</code>
** In version 4.4 we introduced new script for disable SELinux <code>/usr/libexec/vzctl/scripts/vz-postinstall</code>
* Random system freezes
** {{bz | 982489}}
* Kernel older or equal 3.10
** You shall execute <code>vzctl exec 101  killall udevd</code>
===4.3.1 specific===
* criu: command not found
** <code>yum install crtools</code> (Patch sent to maintainers)
* Doesn't work <code>vzctl exec 101 ps axf</code> (proc is not mounted)
** OpenVZ # [https://bugzilla.openvz.org/show_bug.cgi?id=2658 2658]
* Doesn't work <code>vzctl restore 101</code> (VE_VETH_DEVS failure)
** OpenVZ # [https://bugzilla.openvz.org/show_bug.cgi?id=2659 2659]
==Bug Reports==
* If something went wrong you can see dump.log in <code>/var/lib/vz/dump/Dump.101.fail/</code> and send bugreport.
* For bugreport you shall create archive dump and attach to BZ. Create archive (as root):
<code>cd /var/lib/vz/dump/Dump.101.fail/ && tar -cJf /Dump.101.fail.tar.xz *</code>
* For problems with ethernet you shall send to us <code>ip addr; ip route</code> from host and guest in two files.
* [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=vzctl New bug]
|setup=
|setup=
# Install: {{command|su -c 'yum install vzctl'}}
# Open terminal
# Open terminal
# Switch to root user: {{command | su -}}
# Switch to root user: <code>su -</code>
# Install: <code>yum install vzctl</code>
|actions=
|actions=
# Create new container: {{command | vzctl create 101 --ostemplate centos-6-x86_64}}
# Create new container: <code>vzctl create 101 --ostemplate centos-6-x86_64</code>
# Start container: {{command | vzctl start 101}}
# Start container: <code>vzctl start 101</code>
# Enter to container: {{command | vzctl enter 101}}
# Exec ps in container: <code>vzctl exec 101 ps axf</code>
# Enter to container: <code>vzctl enter 101</code>
# Exec ps in container directly: <code>ps axf</code>
# Exit from container: <code>logout</code>
# Suspend container: <code>vzctl suspend 101</code>
# Restore container: <code>vzctl restore 101</code> or <code>vzctl resume 101</code>
# Stop container: <code>vzctl stop 101</code>
|results=
|results=
The following must be true to consider this a successful test run. Be brief ... but explicit.  
* All steps completes without error
# Step #1 completes without error
* Steps #3, #5 shows the same. Like this:
# The system boots into runlevel 5
<pre>
# Program completes with exit code 0
Directory /proc/vz not found, assuming non-OpenVZ kernel
|optional=Optionally provide hints for exploratory testing.
  PID TTY      STAT  TIME COMMAND
  551 pts/0    R+    0:00 ps axf
    1 ?        Ss    0:00 init
  59 ?        S<s    0:00 /sbin/udevd -d
  299 ?        S<    0:00  \_ /sbin/udevd -d
  459 ?        Sl    0:00 /sbin/rsyslogd -i /var/run/syslogd.pid -c 5
  488 ?        Ss    0:00 /usr/sbin/sshd
  495 ?        Ss    0:00 xinetd -stayalive -pidfile /var/run/xinetd.pid
  502 ?        Ss    0:00 /usr/sbin/saslauthd -m /var/run/saslauthd -a pam -n 2
  503 ?        S      0:00  \_ /usr/sbin/saslauthd -m /var/run/saslauthd -a pam -n 2
  518 ?        Ss    0:00 sendmail: accepting connections
  526 ?        Ss    0:00 sendmail: Queue runner@01:00:00 for /var/spool/clientmqueue
  534 ?        Ss    0:00 /usr/sbin/httpd
  537 ?        S      0:00  \_ /usr/sbin/httpd
  542 ?        Ss    0:00 crond
</pre>
|optional=
}}
}}

Latest revision as of 16:52, 23 July 2013


Description

Basic tests for OpenVZ Linux Containers and Checkpoint/Restore In Userspace (CRIU)

Known issues

  • criu: command not found
    • On not x8_64 arches CRIU not working. Work in progress.
  • Problems with SELinux
    • Temporary fix: setenforce 0
    • In version 4.4 we introduced new script for disable SELinux /usr/libexec/vzctl/scripts/vz-postinstall
  • Random system freezes
  • Kernel older or equal 3.10
    • You shall execute vzctl exec 101 killall udevd

4.3.1 specific

  • criu: command not found
    • yum install crtools (Patch sent to maintainers)
  • Doesn't work vzctl exec 101 ps axf (proc is not mounted)
  • Doesn't work vzctl restore 101 (VE_VETH_DEVS failure)

Bug Reports

  • If something went wrong you can see dump.log in /var/lib/vz/dump/Dump.101.fail/ and send bugreport.
  • For bugreport you shall create archive dump and attach to BZ. Create archive (as root):

cd /var/lib/vz/dump/Dump.101.fail/ && tar -cJf /Dump.101.fail.tar.xz *

  • For problems with ethernet you shall send to us ip addr; ip route from host and guest in two files.
  • New bug

Setup

  1. Open terminal
  2. Switch to root user: su -
  3. Install: yum install vzctl

How to test

  1. Create new container: vzctl create 101 --ostemplate centos-6-x86_64
  2. Start container: vzctl start 101
  3. Exec ps in container: vzctl exec 101 ps axf
  4. Enter to container: vzctl enter 101
  5. Exec ps in container directly: ps axf
  6. Exit from container: logout
  7. Suspend container: vzctl suspend 101
  8. Restore container: vzctl restore 101 or vzctl resume 101
  9. Stop container: vzctl stop 101

Expected Results

  • All steps completes without error
  • Steps #3, #5 shows the same. Like this:
Directory /proc/vz not found, assuming non-OpenVZ kernel
  PID TTY      STAT   TIME COMMAND
  551 pts/0    R+     0:00 ps axf
    1 ?        Ss     0:00 init
   59 ?        S<s    0:00 /sbin/udevd -d
  299 ?        S<     0:00  \_ /sbin/udevd -d
  459 ?        Sl     0:00 /sbin/rsyslogd -i /var/run/syslogd.pid -c 5
  488 ?        Ss     0:00 /usr/sbin/sshd
  495 ?        Ss     0:00 xinetd -stayalive -pidfile /var/run/xinetd.pid
  502 ?        Ss     0:00 /usr/sbin/saslauthd -m /var/run/saslauthd -a pam -n 2
  503 ?        S      0:00  \_ /usr/sbin/saslauthd -m /var/run/saslauthd -a pam -n 2
  518 ?        Ss     0:00 sendmail: accepting connections
  526 ?        Ss     0:00 sendmail: Queue runner@01:00:00 for /var/spool/clientmqueue
  534 ?        Ss     0:00 /usr/sbin/httpd
  537 ?        S      0:00  \_ /usr/sbin/httpd
  542 ?        Ss     0:00 crond