Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Port upgrade scenario to Xenial #4237

Closed
conorsch opened this issue Mar 6, 2019 · 1 comment
Closed

Port upgrade scenario to Xenial #4237

conorsch opened this issue Mar 6, 2019 · 1 comment

Comments

@conorsch
Copy link
Contributor

conorsch commented Mar 6, 2019

Description

The "upgrade" scenario in Molecule is Trusty-only, and should be ported to Xenial (as default), so that upgrade testing can be performed on Xenial hosts. Related to #4155.

User Research Evidence

None, dev-env only.

User Stories

As a developer, I want to test upgrades on the primary supported platform, i.e. Xenial.
@redshiftzero redshiftzero mentioned this issue Mar 6, 2019
Closed
8 tasks
@conorsch conorsch mentioned this issue Mar 6, 2019
Merged
5 tasks
@conorsch conorsch mentioned this issue Mar 7, 2019
Closed
17 tasks
@conorsch
Copy link
Contributor Author

conorsch commented Mar 7, 2019

Started work on this front today, will resume tomorrow. Further clarification: we must update both the vagrant_packager logic and the upgrade logic, since the latter depends on the former. Plan of record is to add Xenial support as the default behavior, but provide Trusty support for the time being, to be removed at a later date.

@conorsch conorsch mentioned this issue Mar 9, 2019
Merged
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@conorsch