[2.1, IPv6] omapi code does not deal well with ipv6 addresses

Bug #1606281 reported by LaMont Jones
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Expired
High
Unassigned

Bug Description

Seen in rackd.log, context is largely forgotten. Most likely this was 2.0 (and trunk, of course.)

            'exception')(error_info.get('message'))
        provisioningserver.drivers.power.PowerConnError: Could not connect to BMC. Check BMC configuration and try again.

<STDIN> line 1: 2602 exceeds max (255) for precision.
set ip-address = 2602:
                  ^
<STDIN> line 1: 306 exceeds max (255) for precision.
set ip-address = 2602:306:
                      ^
<STDIN> line 1: ce26 exceeds max (255) for precision.
set ip-address = 2602:306:ce26:
                          ^
<STDIN> line 1: fc80 exceeds max (255) for precision.
set ip-address = 2602:306:ce26:fc80:
                               ^
<STDIN> line 1: eea8 exceeds max (255) for precision.
set ip-address = 2602:306:ce26:fc80:eea8:
                                    ^
<STDIN> line 1: 6bff exceeds max (255) for precision.
set ip-address = 2602:306:ce26:fc80:eea8:6bff:
                                         ^
<STDIN> line 1: fefd exceeds max (255) for precision.
set ip-address = 2602:306:ce26:fc80:eea8:6bff:fefd:
                                              ^
<STDIN> line 1: ac71 exceeds max (255) for precision.

Changed in maas:
milestone: none → 2.1.0
status: New → Incomplete
Changed in maas:
milestone: 2.0.1 → next
importance: Undecided → Critical
milestone: next → 2.1.0
summary: - omapi code does not deal well with ipv6 addresses
+ [2.1, IPv6] omapi code does not deal well with ipv6 addresses
Changed in maas:
milestone: 2.1.0 → 2.1.1
Changed in maas:
milestone: 2.1.1 → 2.1.2
Changed in maas:
milestone: 2.1.2 → 2.1.3
Changed in maas:
importance: Critical → High
milestone: 2.1.3 → 2.4.x
Changed in maas:
milestone: 2.4.x → 2.5.x
Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Incomplete → Expired
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.