netapp fqdn and system-name not matching

[jamesosbourn]

Whilst setting up puppet for one of our netapp units I ran across a problem which was seen with the error

Debug: Not connected to a vserver, so gather system facts
Debug: System info = {"version"=>"NetApp Release 8.3.2: Tue Feb 23 23:35:06 UTC 2016", "clustered"=>"true", "hostname"=>nil}
Debug: Result = #<NaElement:0x00000004559bb0 @name="results", @content="", @children=[#<NaElement:0x00000004559408 @name="attributes-list", @content="", @children=[#<NaElement:0x00000004558be8 @name="system-info", @content="", @children=[#<NaElement:0x00000004558490 @name="board-speed", @content="2993", @children=[], @attrkeys=[], @attrvals=[]>, #<NaElement:0x0000000472a9d0 @name="board-type", @content="NetApp VSim", @children=[], @attrkeys=[], @attrvals=[]>, #<NaElement:0x00000004728f68 @name="cpu-microcode-version", @content="1805", @children=[], @attrkeys=[], @attrvals=[]>, #<NaElement:0x0000000465f2f8 @name="cpu-processor-id", @content="0x206d7", @children=[], @attrkeys=[], @attrvals=[]>, #<NaElement:0x0000000465d890 @name="cpu-serial-number", @content="999999", @children=[], @attrkeys=[], @attrvals=[]>, #<NaElement:0x000000044afe08 @name="memory-size", @content="5120", @children=[], @attrkeys=[], @attrvals=[]>, #<NaElement:0x000000044ae0f8 @name="number-of-processors", @content="2", @children=[], @attrkeys=[], @attrvals=[]>, #<NaElement:0x000000044ac640 @name="prod-type", @content="FAS", @children=[], @attrkeys=[], @attrvals=[]>, #<NaElement:0x000000047469f0 @name="supports-raid-array", @content="true", @children=[], @attrkeys=[], @attrvals=[]>, #<NaElement:0x00000004744f10 @name="system-id", @content="4082368507", @children=[], @attrkeys=[], @attrvals=[]>, #<NaElement:0x00000005317040 @name="system-machine-type", @content="SIMBOX", @children=[], @attrkeys=[], @attrvals=[]>, #<NaElement:0x00000005315218 @name="system-model", @content="SIMBOX", @children=[], @attrkeys=[], @attrvals=[]>, #<NaElement:0x00000005302ff0 @name="system-name", @content="pup-netappa", @children=[], @attrkeys=[], @attrvals=[]>, #<NaElement:0x00000005301100 @name="system-serial-number", @content="4082368-50-7", @children=[], @attrkeys=[], @attrvals=[]>, #<NaElement:0x000000052b71b8 @name="vendor-id", @content="NetApp", @children=[], @attrkeys=[], @attrvals=[]>], @attrkeys=[], @attrvals=[]>], @attrkeys=[], @attrvals=[]>, #<NaElement:0x000000052b4eb8 @name="num-records", @content="1", @children=[], @attrkeys=[], @attrvals=[]>], @attrkeys=["status"], @attrvals=["passed"]>
Debug: System-name = netapp1. downcase = netapp1
Debug: Match = false
Error: Could not retrieve local facts: No matching system found with the system name netapp1.example.com
Error: Failed to apply catalog: Could not retrieve local facts: No matching system found with the system name netapp1.example.com

On investigating I found that the file module/netapp/lib/puppet/util/network_device/netapp/facts.rb line 116 looks to match the system-name of the netapp against the fqdn or the device in the device.conf file with the url directive.

For example with the netapp cluster name of netapp1 and the fqdn of netapp1.example.com the devices.conf url directive would be

url https://username:[email protected].

The code would then fail as above as the Match is false

changing the url directive to the following, assuming DNS resolution works, solves the issue

url https://usename:password@netapp1

I am running with ONTAP 8.3.2

[amit0701]

Hi james,

I noticed that, the facts.rb file
https://github.com/puppetlabs/puppetlabs-netapp/blob/master/lib/puppet/util/network_device/netapp/facts.rb is one commit ahead of what we would be getting when u do a "puppet module install puppetlabs-netapp" . Can you check if new facts.rb fixes the issue? If not, feel free to reach out at [email protected] . We can look at it together.

[jamesosbourn]

I took a copy of the github version and relinked the puppet module location to point this copy, ran a puppet agent -t and then a puppet device and I am still seeing the same error produced at this point in the facter gathering. The debug message before the failure indicates that the name check still fails.