Victoria Series Release Notes

13.1.0

Bug Fixes

  • The qemu user on the host gets created using uid/gid 107. Certificateson the host, but also the vhost-user sockets created by ovs use thisuid/gid. With the move to TCIB images the default kolla ids werereverted and the previous overwrite dropped. This make e.g. the qemuprocesses to fail to use the libvirt-vnc bind mounted certificates.This change brings back the previous overwrite of the qemu useruid/gid.

12.6.0

New Features

  • Added a image yaml for real time kernels support . If you use it, don’t forget to also add the rhel-8-for-x86_64-rt-rpms channel.

  • Addedmodify_only_with_source to the ContainerImagePrepare set that canbe used to limit modify container images to a specific image_source asdefined in the services to container images mapping.

Upgrade Notes

  • The default container prefix isopenstack- instead ofcentos-binary-starting with Victoria.

Bug Fixes

  • When using specifying ContainerImagePrepare if a tag is explicitly providedin a set, the tag_from_label functionality will not be run as we usethe defined tag for the containers. Previously we would still attempttag lookups even if we wanted a specific tag.

Other Notes

  • container-images/tripleo_containers.yaml.j2 is now used to determine whatcontainers are used for which services when running the container imageprepare process runs.

12.5.0

Bug Fixes

  • When the default tag doesn’t exist in the container repo during container image prepare, and a tag wasn’t set in the actual input for ContainerImagePrepare, the latest tag from the repo will be used instead of failing with a not found error.

  • Fixbug 1887692 solimit_hosts will take precedence over the blacklisted_hostnames.And therefore Ansible won’t be run with two –limit if both limit hostsand blacklisted hostnames are in use. When we want to run Ansible onspecific hosts, we will ignore the blacklisted nodes and assume we knowwhat we do. In the case of the scale-down scenario, the unreachable nodesare ignored.