From Fedora Project Wiki
(Created page with "{{QA/Test_Case |description=This is a simple testcase to determine whether docker-storage-setup runs correctly after booting an Atomic Host. {{Admon/note|Prerequisite|This tes...")
 
(update output text)
 
(2 intermediate revisions by the same user not shown)
Line 7: Line 7:
# Run the following commands:
# Run the following commands:
  # journalctl -o cat --unit docker-storage-setup.service
  # journalctl -o cat --unit docker-storage-setup.service
# docker info | grep 'Storage Driver'
  # lsblk
  # lsblk
|results=
|results=
# The output of the first command should resemble:
# The output of the first command should resemble:
  CHANGED: partition=2 start=411648 old: size=12171264 end=12582912 new: size=41531232,end=41942880
  <nowiki>
Physical volume "/dev/vda2" changed
# journalctl -o cat --unit docker-storage-setup.service
1 physical volume(s) resized / 0 physical volume(s) not resized
Starting Docker Storage Setup...
Size of logical volume atomicos/root changed from 1.95 GiB (500 extents) to 4.00 GiB (1024 extents).
WARN: sector size not found in sfdisk output, assuming 512
Logical volume root successfully resized
CHANGED: partition=2 start=2099200 old: size=10483712 end=12582912 new: size=39843807,end=41943007
Rounding up size to full physical extent 24.00 MiB
  Physical volume "/dev/vda2" changed
Logical volume "docker-meta" created
  1 physical volume(s) resized / 0 physical volume(s) not resized
  Logical volume "docker-data" created
  Size of logical volume atomicos/root changed from <5.00 GiB (1279 extents) to <19.00 GiB (4863 extents).
  Logical volume atomicos/root successfully resized.
meta-data=/dev/mapper/atomicos-root isize=512    agcount=4, agsize=327424 blks
        =                      sectsz=512  attr=2, projid32bit=1
        =                      crc=1        finobt=1 spinodes=0 rmapbt=0
        =                      reflink=0
data    =                      bsize=4096  blocks=1309696, imaxpct=25
        =                      sunit=0      swidth=0 blks
naming  =version 2              bsize=4096  ascii-ci=0 ftype=1
log      =internal              bsize=4096  blocks=2560, version=2
        =                      sectsz=512  sunit=0 blks, lazy-count=1
realtime =none                  extsz=4096  blocks=0, rtextents=0
data blocks changed from 1309696 to 4979712
Started Docker Storage Setup.
</nowiki>
# The 'docker info' command output should resemble:
  <nowiki>
# docker info | grep 'Storage Driver'
Storage Driver: overlay2
  WARNING: You're not using the default seccomp profile
</nowiki>                     
# The lsblk command output should resemble:
# The lsblk command output should resemble:
  NAME                     MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
  <nowiki>
  vda                       252:0    0   20G 0 disk  
# lsblk           
├─vda1                   252:1    0 200M 0 part /boot
NAME             MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
└─vda2                   252:2    0 19.8G 0 part  
sr0                11:0    1 366K  0 rom 
  ├─atomicos-root         253:0    0    4G 0 lvm  /sysroot
vda               252:0    0   6G 0 disk  
  ├─atomicos-docker--meta 253:1    0  24M  0 lvm 
├─vda1           252:1    0   1G 0 part /boot
  └─atomicos-docker--data 253:2    0  10G  0 lvm
└─vda2           252:2    0   5G 0 part  
  └─atomicos-root 253:0    0    5G 0 lvm  /sysroot
</nowiki>
}}
}}

Latest revision as of 15:59, 11 April 2018

Description

This is a simple testcase to determine whether docker-storage-setup runs correctly after booting an Atomic Host.

Note.png
Prerequisite
This testcase assumes you have already ran the boot test.

Setup

  1. Ensure you have a booted working Atomic Host

How to test

  1. Run the following commands:
# journalctl -o cat --unit docker-storage-setup.service
# docker info

Expected Results

  1. The output of the first command should resemble:
# journalctl -o cat --unit docker-storage-setup.service
Starting Docker Storage Setup...
WARN: sector size not found in sfdisk output, assuming 512
CHANGED: partition=2 start=2099200 old: size=10483712 end=12582912 new: size=39843807,end=41943007
  Physical volume "/dev/vda2" changed
  1 physical volume(s) resized / 0 physical volume(s) not resized
  Size of logical volume atomicos/root changed from <5.00 GiB (1279 extents) to <19.00 GiB (4863 extents).
  Logical volume atomicos/root successfully resized.
meta-data=/dev/mapper/atomicos-root isize=512    agcount=4, agsize=327424 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1 spinodes=0 rmapbt=0
         =                       reflink=0
data     =                       bsize=4096   blocks=1309696, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
log      =internal               bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
data blocks changed from 1309696 to 4979712
Started Docker Storage Setup.
  1. The 'docker info' command output should resemble:
# docker info | grep 'Storage Driver'
Storage Driver: overlay2
  WARNING: You're not using the default seccomp profile
  1. The lsblk command output should resemble:
# lsblk             
NAME              MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sr0                11:0    1  366K  0 rom  
vda               252:0    0    6G  0 disk 
├─vda1            252:1    0    1G  0 part /boot
└─vda2            252:2    0    5G  0 part 
  └─atomicos-root 253:0    0    5G  0 lvm  /sysroot


Retrieved from "https://fedoraproject.org/w/index.php?title=User:Roshi/QA/AtomicTests/Atomic_Docker_Storage_Setup&oldid=515722"