Closed sjabasti closed 4 years ago
@sjabasti Hey, Steven! This is a bug in MetroAE. We failed to consider the case where the VSC might be patched along with the VSD. It will certainly work, but we put that assertion in there that is stopping it from making progress. That assertion should be removed.
You have two choices for a work-around:
For the edit option, you would need to remove these lines from src/playbooks/with_build/upgrade_vscs_before_vrs and upgrade_vscs_after_vrs:
For the second deployment option, you would do something like this in upgrade.yml:
upgrade_from_version: "5.3.2" upgrade_to_version: "5.4.1"
Metro will then to a .tim file replacement on the VSC. It just so happens that the code under the covers only uses those two versions to determine if it's a patch upgrade or not. It won't mess anything up to use "5.3.2" for the first and to leave off the "u" on the second.
Created METROAE-1176 to fix this.
Fixed.
Hi,
So i am trying to upgrade from 5.4.1.u6 to 5.4.1.u8
using the below commands: (using an openstack deployment)
This results in the following assertion:
So is it normal that we cannot use metro to perform a VSC patch upgrade where it only should replace the tim file?
Kind Regards Steven Bastiaens