Project

General

Profile

Actions
Copy link

Bug #6718

closed

Unused IP request with virsh errors with: unable to retrive virsh info: Must define a name

Added by Dominic Cleal over 9 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
DHCP
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Since #6377, unused IP requests to the proxy when using DHCP + virsh provider now result in:

E, [2014-07-22T13:45:14.192720 #25723] ERROR -- : DHCP virsh provider error: unable to retrive virsh info: Must define a name: {:subnet=>192.168.122.0/255.255.255.0, :ip=>"192.168.122.251", :mac=>"52:54:00:f0:22:bf", :hostname=>nil}
127.0.0.1 - - [22/Jul/2014 13:45:14] "GET /dhcp/192.168.122.0/unused_ip?from=192.168.122.100&to=192.168.122.200 HTTP/1.1" 400 182 0.1210

Related issues 1 (0 open — 1 closed)

Related to Smart Proxy - Bug #6377: Incorrect dhcp providers server virsh.rb loadSubnetDataClosed06/25/2014Actions
Actions
Copy link
 #1

Updated by Dominic Cleal over 9 years ago

  • Related to Bug #6377: Incorrect dhcp providers server virsh.rb loadSubnetData added
Actions
Copy link
 #2

Updated by Lukas Zapletal over 9 years ago

How to reproduce? WFM


D, [2014-07-22T15:59:12.265784 #14945] DEBUG -- : Lazy loaded 192.168.122.0/255.255.255.0 records
D, [2014-07-22T15:59:12.266026 #14945] DEBUG -- : Searching for free IP - pinging 192.168.122.101
D, [2014-07-22T15:59:14.273910 #14945] DEBUG -- : Found free IP 192.168.122.101 out of a total of 98 free IPs
::1 - - [22/Jul/2014 15:59:14] "GET /dhcp/192.168.122.0/unused_ip?from=192.168.122.100&to=192.168.122.200 HTTP/1.1" 200 24 2.0396
localhost - - [22/Jul/2014:15:59:12 CEST] "GET /dhcp/192.168.122.0/unused_ip?from=192.168.122.100&to=192.168.122.200 HTTP/1.1" 200 24
- -> /dhcp/192.168.122.0/unused_ip?from=192.168.122.100&to=192.168.122.200
Actions
Copy link
 #3

Updated by Dominic Cleal over 9 years ago

Maybe it's these.. I have some DHCP reservations with no hostnames - maybe that's from before #4661? In which case I think it's still valid...

    <dhcp>
      <range start='192.168.122.128' end='192.168.122.254'/>
      <host mac='52:54:00:f0:22:bf' ip='192.168.122.251'/>
      <host mac='00:1a:4a:27:a4:41' ip='192.168.122.112'/>
      <host mac='00:1a:4a:27:a4:44' ip='192.168.122.116'/>
...
Actions
Copy link
 #4

Updated by Lukas Zapletal over 9 years ago

  • Status changed from New to Need more information

I've just reproduced, but I am not sure if this is a bug. Just add the missing info there, virsh adds these records correctly (with the name). We can implement a workaround that would make up a name (e.g. fixAA:BB:CC:DD:EE:FF), but I don't think we want that.

Actions
Copy link
 #5

Updated by Dominic Cleal over 9 years ago

  • Status changed from Need more information to Rejected
  • translation missing: en.field_release deleted (10)

Hmm, I think it's still valid, but will close out for now, maybe there isn't much we can do about it - short of a larger overhaul to permit reservations without hostnames.

Actions
Copy link

Also available in: Atom PDF