The package-upgrade action is similar to the openstack-upgrade action
except that it performs package upgrades within the current openstack
release. If a new openstack release is available, the package-upgrade
action will not perform any upgrades.
Sync common files from release-tools, with modifications specific
to this layer.
Change-Id: I4eaee81e05d44d9649c37d397672d263bc2a1025
Charms that use the openstack-upgrade action have the option (by
default in charms.openstack) to re-render their configuration files
after the packages have been upgraded. If that charm has interfaces
that are based on the charms.reactive Endpoint class, then they need to
be discovered by the charms.reactive framework so that they can be
'found' by the from_flag() function when constructing an adapters
instance for the render function in charms.openstack (and ultimately
charm-helpers as a context)., This involves running the
hookenv._run_atstart() function.
Closes-Bug: #1908267
Change-Id: Idfeac39b6d9974bcbbe1891623ff09cc447d87bb
- added mising test-requirements.txt file
- updated testenv build to build in a tmp folder outside of src
- removing sitepackages in tox.ini to avoid test env pollution
- skip_missing_interpreters in tox.ini set to False to avoid false
positives by skipping missing interpreters.
Change-Id: I7985b07bb215ad43403a3e581197d5e139b603ac
