MAAS doesn't ignore pre-composed node remote storage if InitiatorIQN is non-empty

Bug #1685835 reported by Newell Jensen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Newell Jensen
MAAS RSD
Fix Released
Critical
Newell Jensen

Bug Description

Currently, if a pre-composed node has remote storage and the InitiatorIQN is a non-empty string, we don't ignore this iscsi storage even though we will not be able to use it. This storage should be ignored and the total, avilable, and used iscsi storage for the Pod should be adjusted accordingly.

Related branches

Changed in maas:
importance: Undecided → Critical
status: New → Triaged
assignee: nobody → Newell Jensen (newell-jensen)
milestone: none → 2.2.0rc3
Changed in maas:
status: Triaged → In Progress
Changed in maasrsd:
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maasrsd:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
Changed in maasrsd:
status: Fix Committed → Fix Released
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.