Remove the scapy dependency in the rogue dhcp validations
Bug #1634023 reported by
Tomas Sedovic
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Martin André |
Bug Description
We have a couple of validations that check for DHCP responses on interfaces where there should be none. It's now using scapy, but we're having to do workarounds to make that dependency available. We should just write an Ansible module that checks for DHCP responses directly.
https:/
Some links:
http://
https:/
Changed in tripleo: | |
milestone: | ocata-1 → ocata-2 |
Changed in tripleo: | |
status: | In Progress → Triaged |
Changed in tripleo: | |
milestone: | ocata-2 → ocata-3 |
tags: | removed: in-stable-newton |
Changed in tripleo: | |
milestone: | ocata-3 → pike-1 |
Changed in tripleo: | |
milestone: | pike-1 → pike-2 |
Changed in tripleo: | |
milestone: | pike-2 → pike-3 |
To post a comment you must log in.
This validation will always fail in the rogue-dhcp validation that's in Newton, with the following error:
/var/log/ mistral/ engine. log:2016- 11-11 14:34:07.161 32287 INFO workflow_trace [-] Task 'run_validation' (2e98c310- 1da5-456c- a3f5-6c13366913 fb) [RUNNING -> ERROR, msg={u'stderr': u'', u'stdout': u"Task 'Install scapy' failed:\nHost: localhost\nMessage: Failed to find required executable virtualenv\ n\nFailure! The validation failed for the following hosts:\n* localhost\n"}] (execution_ id=6cd7c9d0- 94a2-4ddd- 9ea3-4c3b394178 87)