Skip to content
This repository has been archived by the owner on May 11, 2020. It is now read-only.

Fixin stuff #4

Merged
merged 3 commits into from
Dec 11, 2018
Merged

Fixin stuff #4

merged 3 commits into from
Dec 11, 2018

Conversation

tehsmyers
Copy link
Contributor

Three separate commits:

Sean Myers added 3 commits November 8, 2018 13:18
If the role is unable to detect which connection manages the given
interface, fail with a better error than 'Error: unknown connection
"--"'

closes oasis-roles#3
In the process of actually using this role, I was reminded that it
exists mainly to address a bit of an edge case, which is to be able to
add an address to an interface after that interface has already been
configured (e.g. after installing a system that receives addresses via
DHCP, this role can be used to add an additional static address to that
interface).
@tehsmyers
Copy link
Contributor Author

downstream jenkins appears to be generally failing due to an pytest regression, which is in the process of being fixed: pytest-dev/pytest#4304

Test output show that the tests passed before pytest exploded. I'm content to wait for the pytest fix to roll out, but if we want to fix it right now, we could pin pytest to 3.9.3, the most recent release prior to the regression.

@tehsmyers
Copy link
Contributor Author

This comment contains a specific fix for molecule, which is handy, should this problem persist. :)

@tehsmyers
Copy link
Contributor Author

ok build

@tehsmyers
Copy link
Contributor Author

The downstream tests are failing in automation due to an odd pipeline bug, but the molecule scenario works when run directly. (oasis-origin/oasis-pipeline#1)

@tehsmyers tehsmyers merged commit 2f2495b into oasis-roles:master Dec 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support interfaces without a connection Don't default to omit
1 participant