maniacs-setup fails with MAAS 3.3.0

Bug #2008022 reported by Rod Smith
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maas-cert-server
New
High
Rod Smith

Bug Description

The maniacs-setup script is failing when run against MAAS 3.3.0. The script crashes, with no error output, after displaying the text "Initializing rack controller." If re-run, the script will run to completion; however, logging into the MAAS server shows no subnets defined.

The cause appears to be a change to the MAAS CLI API. Currently, maniacs-setup's setup_ip_ranges() function includes a number of calls to set up IP address ranges, beginning with:

    echo "* Initializing rack controller"
    maas admin ipranges create type=dynamic start_ip="$DHCP_RANGE_LOW" end_ip="$DHCP_RANGE_HIGH" > /dev/null

That second line, if entered manually (with suitable variable substitution), produces an error message:

$ maas admin ipranges create type=dynamic start_ip=172.24.124.1 end_ip=172.24.124.255
{"subnet": ["This field is required."]}

Obviously, maniacs-setup must be updated to cope with this change to MAAS. It's possible that some other lines in this same block of code will need changing, too.

Related branches

Rod Smith (rodsmith)
Changed in maas-cert-server:
importance: Undecided → High
assignee: nobody → Rod Smith (rodsmith)
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.