I am running successfully workflow related to QOS ( workflow version 4.0 as 4.1 failed for me ), which used to work on WFA3.1 . Now on WFA188.8.131.52.2 , I don't see the QOS appearing on the clusters.
In the aqos.log , frequently finding:
2017/07/05 09:24:45 INFO Start executing KP Script 2017/07/05 09:24:45 INFO Configuration file location : E:\Program Files\NetApp\WFA\bin\..\aqos\config.txt 2017/07/05 09:24:45 INFO Refer : service_manager.log under ..\jboss\standalone\log for STDOUT 2017/07/05 09:24:45 INFO REST API will use HTTP port : 80 2017/07/05 09:24:45 INFO call read_configuration function to read configuration file line no. 2017/07/05 09:24:45 INFO Reading service levels in E:\Program Files\NetApp\WFA\bin\..\aqos\config.txt 2017/07/05 09:24:45 INFO Extreme : 12288 IOPS/TB 2017/07/05 09:24:45 INFO Value : 512 IOPS/TB 2017/07/05 09:24:45 INFO High_Write : 8192 IOPS/TB 2017/07/05 09:24:45 INFO High_Read : 4096 IOPS/TB 2017/07/05 09:24:45 INFO Capacity : 128 IOPS/TB 2017/07/05 09:24:45 INFO Performance : 2048 IOPS/TB 2017/07/05 09:24:45 INFO Using configuration in E:\Program Files\NetApp\WFA\bin\..\aqos\config.txt 2017/07/05 09:24:45 INFO reading configuration file is done 2017/07/05 09:24:46 ERROR credentials are not retrived successfully 2017/07/05 09:24:46 INFO Ignoring as no crdentials found in WFA crdentials for node PIRULO1 2017/07/05 09:24:46 INFO Ignoring as no crdentials found in WFA crdentials for node PIRULO1.COM
I've recently been looking at the aqos scripts and one oddity seems to be that only credentials with the "match" type "exact" are being used by the script. This not only will be quite a problem for us (because we'd like to use "pattern" instead), but it might also be what is causing the problem for you. How are your credentials setup in WFA?
That is very interesting. So you are having no Auth issues when setting QoS levels via AQoS? I had a case open on this and was told to enable http (LOL-No) on the cluster (ONTAP 9.1) and that https wasn't supported. It may be tied to the ONTAP version. ¯\_(ツ)_/¯
Yeah we got a similar response from support. That's when I started poking around in the script and the supporting NaServer perl classes and funny enough all my testing were working fine. Only difference to production was a slightly newer package so we upgraded the production package and voilá everything worked (and still seems to work as far as I can see).
Would be interesting if you have any more success using the newest package.