Updating images

Updating from image

It is recommended that images be updated by updating from within the image itself for ensuring updates are done on the node.

Finding the image to use

CODE

$ cv-provision image list
[node]
uuid = e8fabee5-c457-46dc-a3a6-337fbe5da065
live = 1
size = 5.84 GB
branches:
- [Initial branch]
  uuid = 1
  cv_version = 2.25.08-5961
  distro = el8
  last_change = 1756933687
  size = 5.84 GB
  kernels:
  - 5.14.0-570.12.1.el9_6.x86_64

Edit the node

Edit the node and run the commands needed. When done, type exit and Provisioner will recalculate the image. Note, it’s best to wait for this process to finish before trying to boot a node from this image.

CODE

$ cv-provision image edit node
bash-5.1# dnf --refresh update -y
<snip dnf output>
Complete!
bash-5.1# exit
exit
Re-calculating branch size...
6.41 GB

Be sure to type exit when editing is complete to ensure a clean exit from the image editor

Updating from node

Updating an image from a node is not the recommended best practice for updating an image. However, there are times when nodes are “special” or “non-standard” and provisioning every boot is not desired, meaning the image is primarily a “backup” of the node. Examples of these types of nodes are storage devices or head/login nodes that host a database (where pulling from the image would be destroying all database content since last backup). Thus, updates (eg: dnf update) should be done on the node itself and the update done afterwards.

Finding the image to use

CODE

$ cv-provision image list
[storage]
uuid = 724cfcd7-742d-43d7-aed4-9fb73e6d378e
live = 1
size = 42.7 GB
branches:
- [Initial branch]
  uuid = 1
  cv_version = 2.25.08-5961
  distro = el8
  last_change = 1757362191
  size = 42.7 GB
  kernels:
  - 5.14.0-570.12.1.el9_6.x86_64
  - 5.14.0-570.37.1.el9_6.x86_64

Updating the image

Please note! This is incremental meaning that only the difference between what the image currently has and what is on the node will be transferred. As such, only a fraction of the files calculated will end up being copied. Thus, if there is only 10% file difference, then the progress bar will only reach 10%.

The important part is that there is a successful “Finished incremental file transfer”.

CODE

$ cv-provision image update-from-source -i storage --source storage01
Starting incremental transfer [NOTE: progress may not reach 100%]
Copied 116.49K from node at 7.93MB/s:                
  0%| 
Finished incremental file transfer