no easy way to delete a dhcp configuration through the maas-cli

Bug #1059954 reported by Diogo Matsubara
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Raphaël Badin

Bug Description

I set up the dhcp configuration using the maas-cli

maas-cli api maas node-group-interfaces new master ip=192.168.21.1 interface=eth0 management=2 subnet_mask=255.255.255.0 broadcast_ip=192.168.21.255 router_ip=192.168.21.1 ip_range_low=192.168.21.10 ip_range_high=192.168.21.50

Then I noticed the interface should have been br0 instead.

I tried a suggestion from Julian to set management to "Unmanaged", management=0

ubuntu@lenovo-RD230-01:~$ maas-cli api maas node-group-interface update master eth0 management=0
200 OK

  Content-Length: 223
    Content-Type: application/json; charset=utf-8
            Date: Tue, 02 Oct 2012 03:33:38 GMT
          Server: Apache/2.2.22 (Ubuntu)
          Status: 200
            Vary: Authorization,Cookie

{
    "ip_range_high": "192.168.21.50",
    "ip_range_low": "192.168.21.10",
    "broadcast_ip": "192.168.21.255",
    "ip": "192.168.21.1",
    "subnet_mask": "255.255.255.0",
    "management": 2,
    "interface": "eth0"
}

I got the 200 OK response but the master node-group-interface still reports as being managed

Related branches

Changed in maas:
status: New → Triaged
importance: Undecided → Critical
Revision history for this message
Raphaël Badin (rvb) wrote :

I'm trying to reproduce the problem but I'm unable to do so (see http://paste.ubuntu.com/1255568/).

Also while working on this I found bug 1060079 (Gavin is working on it).

But you're right, I'm adding a method to delete an interface.

Changed in maas:
assignee: nobody → Raphaël Badin (rvb)
status: Triaged → In Progress
Revision history for this message
Raphaël Badin (rvb) wrote :

I'm marking this as fixed released because I've added a way to delete an interface, but feel free to open a new bug if the 'update' operation on a nodegroup interface does not work.

Changed in maas:
status: In Progress → Fix Released
Revision history for this message
Raphaël Badin (rvb) wrote :

Let me add that I had to manually work around bug 1060079 to get that to work.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.