Rogue DHCP server not detected; enlist fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
maas-test |
Fix Committed
|
Critical
|
Jeroen T. Vermeulen |
Bug Description
I see this error:
cmd #0025: {{{ssh -i /home/ubuntu/
LogLevel=quiet -o UserKnownHostsF
StrictHostKeyCh
ipmipower -h 10.0.0.101 -u maas -p 6rFuvt3r --on}}}
cmd #0025 retcode: {{{0}}}
cmd #0025 stdout: {{{10.0.0.101: ok}}}
Traceback (most recent call last):
File "/usr/lib/
in test_enlist_node
self.
File "/usr/lib/
raise self.failureExc
AssertionError: Failed to enlist node.
Which means the IPMI command worked and then there is no further feedback at all other than the ugly traceback.
The node was indeed powered on but I've no idea why it didn't go further.
Related branches
- Raphaël Badin (community): Approve
-
Diff: 23 lines (+6/-4)1 file modifiedmaastest/detect_dhcp.py (+6/-4)
- Raphaël Badin (community): Approve
-
Diff: 137 lines (+84/-24)1 file modifiedmaastest/main.py (+84/-24)
- Gavin Panella (community): Needs Fixing
- Graham Binns (community): Approve
-
Diff: 474 lines (+235/-100)5 files modifiedmaastest/cases.py (+11/-38)
maastest/main.py (+106/-57)
maastest/script.py (+31/-0)
maastest/tests/test_main.py (+85/-3)
setup.py (+2/-2)
- Raphaël Badin (community): Approve
-
Diff: 770 lines (+459/-149)7 files modifiedmaastest/cases.py (+15/-82)
maastest/detect_dhcp.py (+2/-4)
maastest/maasfixture.py (+7/-3)
maastest/main.py (+216/-58)
maastest/script.py (+31/-0)
maastest/tests/test_main.py (+187/-1)
setup.py (+1/-1)
summary: |
- Failure to enlist node + Failure to enlist node with no information as to why |
Changed in maas-test: | |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in maas-test: | |
assignee: | nobody → Jeroen T. Vermeulen (jtv) |
status: | Triaged → In Progress |
Changed in maas-test: | |
status: | In Progress → Fix Committed |
Ok I see why now - there is a rogue DHCP server that the initial checks have not picked up.