| jayaanand | @ganso vserver-aggr-info will show size of aggrigates assigned to vserver. so ask customer to associate aggregates to vserver. they can check list of aggrigates assigned to vserver using "vserver show -fields aggr-list" | 05:00 |
|---|---|---|
| jayaanand | 05:00 | |
| jayaanand | also, can you execute vserver-get ZAPI separately and share response for further analysis | 05:06 |
| opendevreview | jayaanand borra proposed openstack/manila master: Human readable export location documentation https://review.opendev.org/c/openstack/manila/+/913709 | 07:56 |
| gireesh | @jayaanand, in vserver scoping OpenStack will not show the pool if aggregate is not associated with vserver. | 08:34 |
| jayaanand | https://docs.netapp.com/us-en/ontap/disks-aggregates/assign-aggregates-svms-task.html. there is a possibility according to documentation "The listed aggregates are assigned to or removed from the SVM. If the SVM already has volumes that use an aggregate that is not assigned to the SVM, a warning message is displayed, but the command is completed successfully. Any aggregates that were already assigned to the SVM and | 09:17 |
| jayaanand | that were not named in the command are unaffected." | 09:17 |
| opendevreview | jayaanand borra proposed openstack/manila master: Human readable export location documentation https://review.opendev.org/c/openstack/manila/+/913709 | 16:43 |
| opendevreview | jayaanand borra proposed openstack/manila master: Human readable export location documentation https://review.opendev.org/c/openstack/manila/+/913709 | 17:04 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!