Bug 1479829
| Summary: | Can't set DHCP bootproto for non-VM network that is attached to a bond interface | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] vdsm | Reporter: | Nikolai Sednev <nsednev> | ||||||||
| Component: | Core | Assignee: | Edward Haas <edwardh> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | high | ||||||||||
| Version: | 4.19.27 | CC: | bugs, danken, edwardh, mburman, nsednev | ||||||||
| Target Milestone: | ovirt-4.1.5 | Keywords: | Regression | ||||||||
| Target Release: | --- | Flags: | rule-engine:
ovirt-4.1+
rule-engine: blocker+ nsednev: testing_plan_complete? |
||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2017-08-23 08:04:22 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Nikolai Sednev
2017-08-09 13:28:37 UTC
Created attachment 1311233 [details]
screencast
Created attachment 1311234 [details]
sosreport from the engine
Sosreport from host alma04 available from here https://drive.google.com/a/redhat.com/file/d/0B85BEaDBcF88enRrTmQyMFZwZFE/view?usp=sharing Please note that the only scenario in which this is reproduced is when trying to set DHCP boot protocol for a non-VM network that is attached to a bond interface, failing with on vdsm side:
2017-08-09 16:45:07,828+0300 ERROR (jsonrpc/6) [jsonrpc.JsonRpcServer] Internal server error (__init__:642)
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 637, in _handle_request
res = method(**params)
File "/usr/lib/python2.7/site-packages/vdsm/rpc/Bridge.py", line 201, in _dynamicMethod
result = fn(*methodArgs)
File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1409, in setupNetworks
supervdsm.getProxy().setupNetworks(networks, bondings, options)
File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in __call__
return callMethod()
File "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in <lambda>
**kwargs)
File "<string>", line 2, in setupNetworks
File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod
raise convert_to_error(kind, result)
IOError: [Errno 19] bond0.162 is not present in the system
2017-08-09 16:45:07,829+0300 INFO (jsonrpc/6) [jsonrpc.JsonRpcServer] RPC call Host.setupNetworks failed (error -32603) in 15.51 seconds (__init__:604)
Nikolai, can you attach supervdsm.log? Michael, do you see this as well, or is it specific to Nikolai's host? (In reply to Dan Kenigsberg from comment #5) > Nikolai, can you attach supervdsm.log? > > Michael, do you see this as well, or is it specific to Nikolai's host? It's not Nikolai's spesific host, it is easily reproduced with next steps: 1) Create bond via setup networks 2) Attach non-VM network to the bond 3) Try to set dhcp bootproto for the non-vm network Result - failed with error on vdsm side: IOError: [Errno 19] bond0.162 is not present in the system I will attach the log Created attachment 1311240 [details]
supervdsm log
(In reply to Dan Kenigsberg from comment #5) > Nikolai, can you attach supervdsm.log? > > Michael, do you see this as well, or is it specific to Nikolai's host? Everything was already attached in https://bugzilla.redhat.com/show_bug.cgi?id=1479829#c3, also there is a screencast attached to this bug which exactly shows what and how to reproduce. (In reply to Nikolai Sednev from comment #8) > (In reply to Dan Kenigsberg from comment #5) > > Nikolai, can you attach supervdsm.log? > > > > Michael, do you see this as well, or is it specific to Nikolai's host? > > Everything was already attached in > https://bugzilla.redhat.com/show_bug.cgi?id=1479829#c3, also there is a > screencast attached to this bug which exactly shows what and how to > reproduce. As specically-requested log attachement is more helpful than an off-bz dump of everything. But Burman has already done that. How could it be a blocker but medium severity? Verified on - vdsm-4.19.28-1.el7ev.x86_64 I still see this issue happening on ovirt-engine-4.2.0-0.0.master.20170811144920.gita423008.el7.centos.noarch on hosts with vdsm-4.20.2-74.git2be4775.el7.centos.x86_64. Should this fix get cloned to the master any soon? (In reply to Nikolai Sednev from comment #12) > I still see this issue happening on > ovirt-engine-4.2.0-0.0.master.20170811144920.gita423008.el7.centos.noarch on > hosts with vdsm-4.20.2-74.git2be4775.el7.centos.x86_64. > Should this fix get cloned to the master any soon? Nikolai, This was fixed for master and working as expected on vdsm-4.20.2-74.git2be4775.el7.centos.x86_64 (In reply to Michael Burman from comment #13) > (In reply to Nikolai Sednev from comment #12) > > I still see this issue happening on > > ovirt-engine-4.2.0-0.0.master.20170811144920.gita423008.el7.centos.noarch on > > hosts with vdsm-4.20.2-74.git2be4775.el7.centos.x86_64. > > Should this fix get cloned to the master any soon? > > Nikolai, > This was fixed for master and working as expected on > vdsm-4.20.2-74.git2be4775.el7.centos.x86_64 Working now, after clicking on "Refresh Capabilities" on host. |