Issue #17503 has been updated by Garrett Honeycutt. Subject changed from when managing an interface on a cisco device where the vlan does not exist, puppet shows that the vlan is created, but does not actually do so. to when managing an interface on a cisco device where the vlan does not exist, puppet errors, then creates the vlan, which is strange behavior Description updated
---------------------------------------- Bug #17503: when managing an interface on a cisco device where the vlan does not exist, puppet errors, then creates the vlan, which is strange behavior https://projects.puppetlabs.com/issues/17503#change-76075 Author: Garrett Honeycutt Status: Unreviewed Priority: Normal Assignee: Category: device Target version: Affected Puppet version: 2.7.12 Keywords: cisco, vlan Branch: VLAN 1000 is specified, though it does not already exist. Puppet correctly sets the VLAN for the interface. Not sure that it should attempt to create the corresponding VLAN. from `site.pp`: <pre> node '10.0.1.3' { Interface { duplex => auto, speed => auto, } interface { 'GigabitEthernet 0/2': description => 'testing', mode => access, native_vlan => 1000, } } </pre> `puppet device --debug`: Notice lines 14 & 15 <pre> 1 info: Applying configuration version '1352189042' 2 debug: Stage[main]: Skipping host resources because running on a device 3 debug: Class[Main]: Skipping host resources because running on a device 4 debug: Node[10.0.1.3]: Skipping host resources because running on a device 5 debug: Prefetching cisco resources for interface 6 debug: command 7 debug: connecting to 10.0.1.3 as sysop 8 notice: /Stage[main]//Node[10.0.1.3]/Interface[GigabitEthernet 0/2]/description: defined 'description' as 'testing shit out' 9 notice: /Stage[main]//Node[10.0.1.3]/Interface[GigabitEthernet 0/2]/native_vlan: defined 'native_vlan' as '1000' 10 notice: /Stage[main]//Node[10.0.1.3]/Interface[GigabitEthernet 0/2]/mode: mode changed 'trunk' to 'access' 11 debug: command 12 debug: connecting to 10.0.1.3 as sysop 13 debug: Updating interface GigabitEthernet0/2 14 err: Error while executing switchport access vlan 1000, device returned switchport access vlan 1000 15 % Access VLAN does not exist. Creating vlan 1000 16 switch2(config-if)# 17 debug: /Stage[main]//Node[10.0.1.3]/Interface[GigabitEthernet 0/2]: The container Node[10.0.1.3] will propagate my refresh event 18 debug: /Stage[main]//Node[10.0.1.3]/Interface[GigabitEthernet 0/2]: The container Node[10.0.1.3] will propagate my refresh event 19 debug: /Stage[main]//Node[10.0.1.3]/Interface[GigabitEthernet 0/2]: The container Node[10.0.1.3] will propagate my refresh event 20 debug: Node[10.0.1.3]: Skipping host resources because running on a device 21 debug: Node[10.0.1.3]: The container Class[Main] will propagate my refresh event 22 debug: Class[Settings]: Skipping host resources because running on a device 23 debug: Class[Settings]: Skipping host resources because running on a device 24 debug: /Stage[main]//Filebucket[main]: Skipping host resources because running on a device 25 debug: /Filebucket[puppet]: Skipping host resources because running on a device 26 debug: Class[Main]: Skipping host resources because running on a device 27 debug: Class[Main]: The container Stage[main] will propagate my refresh event 28 debug: Stage[main]: Skipping host resources because running on a device 29 debug: Finishing transaction -607628508 30 debug: Storing state 31 debug: Stored state in 0.01 seconds 32 notice: Finished catalog run in 4.69 seconds 33 debug: Value of 'preferred_serialization_format' (pson) is invalid for report, using default (b64_zlib_yaml) 34 debug: report supports formats: b64_zlib_yaml raw yaml; using b64_zlib_yaml </pre> from switch: <pre> switch2#show vlan VLAN Name Status Ports ---- -------------------------------- --------- ------------------------------- 1 default active Gi0/1, Gi0/5, Gi0/6, Gi0/7 Gi0/8, Gi0/9, Gi0/10, Gi0/11 Gi0/12, Gi0/13, Gi0/14, Gi0/15 Gi0/16, Gi0/17, Gi0/18, Gi0/19 Gi0/20, Gi0/21, Gi0/22, Gi0/23 Gi0/24, Gi0/25, Gi0/26, Gi0/27 Gi0/28, Gi0/29, Gi0/30, Gi0/31 Gi0/32, Gi0/33, Gi0/34, Gi0/35 Gi0/36, Gi0/37, Gi0/38, Gi0/39 Gi0/40, Gi0/41, Gi0/42, Gi0/43 Gi0/44, Gi0/45, Gi0/46, Gi0/47 Gi0/48 22 Ops active 88 OOB active 202 Storage active 666 VLAN0666 active Gi0/4 1000 VLAN1000 active Gi0/2 1001 VLAN1001 active Gi0/3 1002 fddi-default act/unsup 1003 token-ring-default act/unsup 1004 fddinet-default act/unsup VLAN Name Status Ports ---- -------------------------------- --------- ------------------------------- 1005 trnet-default act/unsup VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2 ---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------ 1 enet 100001 1500 - - - - - 0 0 22 enet 100022 9000 - - - - - 0 0 88 enet 100088 1500 - - - - - 0 0 202 enet 100202 1500 - - - - - 0 0 666 enet 100666 1500 - - - - - 0 0 1000 enet 101000 1500 - - - - - 0 0 1001 enet 101001 1500 - - - - - 0 0 1002 fddi 101002 1500 - - - - - 0 0 1003 tr 101003 1500 - - - - - 0 0 1004 fdnet 101004 1500 - - - ieee - 0 0 1005 trnet 101005 1500 - - - ibm - 0 0 Remote SPAN VLANs ------------------------------------------------------------------------------ Primary Secondary Type Ports ------- --------- ----------------- ------------------------------------------ </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
