UpdateDeployment on non-controller roles can leave packages not updated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Brad P. Crochet |
Bug Description
Even after UpdateDeployment has triggered yum_update.sh, and puppet has also run to update packages it knows about, there are scenarios where some packages may still not be updated on the non-controller role nodes.
libvirt-python is one example. It requires a minimum version of libvirt. When yum-update.sh runs with --exclude libvirt-
Later when puppet runs with ensure=>latest, it updates the packages it knows about. However, it only knows to to update libvirt-
given that libvirt-python is a dependency of openstack-
Changed in tripleo: | |
assignee: | James Slagle (james-slagle) → Marios Andreou (marios-b) |
Changed in tripleo: | |
assignee: | Marios Andreou (marios-b) → Brad P. Crochet (brad-9) |
no longer affects: | tripleo/newton |
no longer affects: | tripleo/trunk |
Changed in tripleo: | |
milestone: | none → newton-rc3 |
i'm thinking that we just do another yum update run with no --exclude specified after puppet has run in a new SoftwareDeployment.