Issue #17503 has been reported by Garrett Honeycutt.
----------------------------------------
Bug #17503: 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.
https://projects.puppetlabs.com/issues/17503
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, though it says that it does, but in fact the VLAN is not
created.
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>
--
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.
