Problem: Using in-product upgrade feature in v1.6 (or easier) fails to upgrade to v1.7 due to package name convention change.
Workaround/Fix: Download the new package and upgrade per steps laid out here.
Problem: When upgrading from v1.2 with a S3 output configured
stagePath was allowed to be undefined. In v1.4+ it is a required field and may causing schema violations on older configs when upgrading.
Workaround/Fix: Re-configure the output with a valid
stagePath filesystem path.