Astute repors "ready" even if DHCP checks are failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Artem Roma | ||
Mitaka |
Fix Released
|
High
|
Artem Roma |
Bug Description
(the issue was found within bug #1569325)
We should report any sort of errors to Nailgun, they must not be hidden.
Steps to reproduce:
0. Deploy master node with few slaves.
1. Create any cluster.
2. Add few nodes to cluster.
3. Run network checker and make DHCP checks to fail (by hacking dhcpcheck to return error)
Expected results:
Astute reports to Nailgun, that "dhcp_check" task is failed.
Actual results:
Astute reports to Nailgun, that "dhcp_check" task is ready. However, we can see in Astute.log something like:
"Spawning listener for enp0s6 failed.\nenp0s6: That device is not up\n2016-04-12 11:55:06 ERROR (api) enp0s6: That device is not up\nSpawning listener for enp0s7 failed.\nenp0s7: That device is not up\n\n",
Changed in fuel: | |
assignee: | Fuel Python (Deprecated) (fuel-python) → Networking (l23-network) |
Changed in fuel: | |
assignee: | Networking (l23-network) → Artem Roma (aroma-x) |
tags: | added: on-verification |
Fix proposed to branch: master /review. openstack. org/316861
Review: https:/