Cruft in storage section in specific node view

[Dave Chiluk]

After upgrading from 1.8 to 1.9.0+bzr4533-0ubuntu1 (trusty1), the storage section of our node view from the webui now contains the following information.

"1400.0GB over [{"is_boot":false,"available_size_human":"400.1 GB","partition_table_type":"","name":"nvme0n1","tags":["ssd"],"used_size":0,"partitions":null,"filesystem":null,"used_for":"Unused","size_human":"400.1 GB","used_size_human":"0.0 bytes","available_size":400088457216,"path":"/dev/disk/by-dname/nvme0n1","model":"","block_size":4096,"type":"physical","id":185,"serial":"","size":400088457216},{"is_boot":true,"available_size_human":"0.0 bytes","partition_table_type":"GPT","name":"sda","tags":["rotary"],"used_size":500104691712,"partitions":[{"size_human":"536.9 MB","name":"sda-part1","filesystem":{"is_format_fstype":true,"mount_point":"/boot/efi","fstype":"fat32","label":"efi"},"path":"/dev/disk/by-dname/sda-part1","used_for":"fat32 formatted filesystem mounted at /boot/efi","type":"partition","id":35,"size":536870912},{"size_human":"499.6 GB","name":"sda-part2","filesystem":{"is_format_fstype":true,"mount_point":"/","fstype":"ext4","label":"root"},"path":"/dev/disk/by-dname/sda-part2","used_for":"ext4 formatted filesystem mounted at /","type":"partition","id":36,"size":499562577920}],"filesystem":null,"used_for":"GPT partitioned with 2 partitions","size_human":"500.1 GB","used_size_human":"500.1 GB","available_size":0,"path":"/dev/disk/by-dname/sda","model":"MM0500GBKAK","block_size":4096,"type":"physical","id":98,"serial":"5000c5007b32c313","size":500107862016},{"is_boot":false,"available_size_human":"500.1 GB","partition_table_type":"","name":"sdb","tags":["rotary"],"used_size":0,"partitions":null,"filesystem":null,"used_for":"Unused","size_human":"500.1 GB","used_size_human":"0.0 bytes","available_size":500107862016,"path":"/dev/disk/by-dname/sdb","model":"MM0500GBKAK","block_size":4096,"type":"physical","id":99,"serial":"5000c5007b32c53f","size":500107862016}] disks"

I don't think this is intentional.

[Andres Rodriguez (andreserl)]

This is a known issue that will no longer be present, but due to it being 1.8-> 1.9 upgrade, it still shows. It wont show after 1.9 _> others anymore. You only need to F5 to clear the message.

[Dave Chiluk (chiluk)]

Can't you do something on upgrade so this is not an issue? Perhaps you could put something in the debian pre or post scripts.

Also as it really is an issue please mark real bugs as won't fix instead. This is definitely upgrade issue. Customers upgrade. They avoid blatant complete redeployments. They will see this and it will affect the perception of maas's quality negatively.

[Andres Rodriguez (andreserl)]

You can now point your users to:
http://maas.ubuntu.com/docs1.9/changelog.html#known-problems-workarounds

[Dave Chiluk (chiluk)]

I do not see explicit mention of this issue in the known-problems-workarounds. I also do not understand how this is a duplicate of bug #1515380.

I understand this is not a high priority issue.

[Dave Chiluk (chiluk)]

NM it looks like the client side cache needs to be refreshed.