Issue #3399 has been updated by Adam Kosmin.

After applying this update and removing the ensure attribute (due to bug 3004), 
I can create a zone with an exclusive iptype attribute. However, when running 
puppetd immediately after, I see the following error:

On line 5:
A net resource with the physical 'vnic1', and address '' already exists.
Resource incomplete.
err: //rbe2/Zone::Instance[fintegrity]/Zone[fintegrity]/ip: change from vnic1: 
to vnic1 failed: Failed to apply configuration

Also, line 5 tends to pop up at other times with an invalid '\n'. I'd post more 
about this but I haven't narrowed down the exact scenario required to duplicate 
the error.


----------------------------------------
Feature #3399: zone type should handle exclusive IP stacks
http://projects.puppetlabs.com/issues/3399

Author: Martin Englund
Status: Available In Testing Branch
Priority: Normal
Assigned to: Martin Englund
Category: Solaris
Target version: 
Affected version: 0.25.4
Keywords: 
Branch: http://github.com/pmenglund/puppet/commits/tickets/0.25.x/3399


Requested by: Adam Kosmin and Lars Tobias Børsting

Solaris zones should have the option to be created with an exclusive IP stack, 
i.e.
<pre>zone { "zonename":
  ip-type = [ exclusive | shared ]
}</pre>

which should translate to the zonecfg command:
<pre>set ip-type=exclusive</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.

Reply via email to