Red Hat Bugzilla – Bug 1602102
[DDF] This section lacks mandatory changes to first-boot.yaml. Of course, for the actual upgrade, these changes are not
Last modified: 2018-10-17 04:53:22 EDT
This section lacks mandatory changes to first-boot.yaml. Of course, for the actual upgrade, these changes are not needed. But if customers don't update first-boot.yaml according to the new version of the installation guide, then this means that on a cloud which went through a minor update, any node deployed after the minor update with a new overcloud-full image will receive the unnecessary and malicious changes that the old first-boot.yaml pushes to the /usr/lib OVS scripts. So while our documentation covers the upgrade of existing nodes, at the current state, users are not made aware that if they don't change first-boot.yaml, any new DPDK compute node will not work. - Andreas https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html/upgrading_red_hat_openstack_platform/sect-updating_the_environment#annotations:d9f8f2cc-18fa-43b9-86ff-09258d516ae3
For an example of what must be removed from first-boot.yaml see https://access.redhat.com/solutions/3538621. It looks like the NFV configuration guide got updated correctly in all but one spot which still has the legacy set_ovs_config software config: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/10/html-single/network_functions_virtualization_configuration_guide/#proc_sriov-dpdk-vxlan-vlan-firstboot
Additionally, we instructed users at some point to make the same changes to the post-install.yaml, these changes need to be removed, as well.
Changes required as per comment #2 and comment #3
I don't understand how this bz is different from 1611483. Are these duplicates?
This BZ specifies one section, but BZ #1611483, created after this, list all occurrences. And yes, it can be made duplicate of #1611483. *** This bug has been marked as a duplicate of bug 1611483 ***