Red Hat Bugzilla – Bug 994600
[vdsm] SuperVdsm fails to start due to ValueError: ipaddr rhevm is not properly defined
Last modified: 2016-02-10 14:55:26 EST
Created attachment 783965 [details]
engine, vdsm, supervdsm logs
Description of problem:
Adding a host to rhevm failed due to supervdsm failure to start. This is caused by attempting to configure routes and failing. supervdsm attempts to configure source route with parameters:
Configuring gateway - ip: 10.35.164.143, network: 10.35.164.0/24, subnet: 255.255.255.0, gateway: rhevm, table: 170108047, device: rhev
gateway = rhevm is passed, and this fails because 'rhevm' is not a valid ip address
Version-Release number of selected component (if applicable):
? happened during host installation in automated test
Steps to Reproduce:
1. Attempt to add host
Supervdsm fails to start
supervdsm should start
Fixed on upstream vdsm master and ovirt-3.3 branches.
verified - did not reproduce in automated tests on is11.
This bug is currently attached to errata RHBA-2013:15291. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.