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.

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

Update default staging target to Xenial #4311

Merged
merged 2 commits into from
Apr 3, 2019
Merged

Update default staging target to Xenial #4311

merged 2 commits into from
Apr 3, 2019

Conversation

eloquence
Copy link
Member

Resolves #4310

Status

Ready for review

If you made changes to the system configuration:

(Staging VMs are provisioned and working, but testinfra tests are failing locally for me - most likely unrelated.)

Copy link
Contributor

@conorsch conorsch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We also need to update the overrides in the staging scenarios themselves, given that we were leveraging this "Trusty" default to determine which packages we should install against Trusty or Xenial hosts. To illustrate the error:

rm -rf build/*
make staging-trusty

Observe error about lack of Xenial debs—it should be looking for Trusty debs! I'll append a commit to resolve prior to approval.

The "default" target distro for staging is now Xenial, which means we
need to tweak the overrides in the various staging-related Molecule
scenarios. Overrides are in place to force Trusty, and overrides
referencing Xenial are removed, due to the new default behavior.
@emkll emkll merged commit cbeadb9 into develop Apr 3, 2019
@emkll emkll deleted the staging-fix branch April 3, 2019 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants