Hi! On Oct 19, 11:33 pm, windowsrefund <windowsref...@gmail.com> wrote: > Puppet 0.24.8 on both the client and server. My zone is being created > but the sysidcfg file is not being created under etc/ > > info: Caching catalog at /var//opt/csw/puppet/state/localconfig.yaml > notice: Starting catalog run > notice: //Node[labrat1]/Zone_instance[labrat1a]/zone_zfs_root/Zfs > [rpool/export/zones]/ensure: created > notice: //Node[labrat1]/Zone_instance[labrat1a]/zone_zfs_root/File[/ > export/zones]/mode: mode changed '755' to '700' > notice: //Node[labrat1]/Zone_instance[labrat1a]/Zfs[rpool/export/zones/ > labrat1a]/ensure: created > notice: //Node[labrat1]/Zone_instance[labrat1a]/File[/export/zones/ > labrat1a]/mode: mode changed '755' to '700' > err: //Node[labrat1]/Zone_instance[labrat1a]/Zone[labrat1a]/ensure: > change from absent to running failed: Could not create sysidcfg: No > such file or directory - /export/zones/labrat1a/root/etc/sysidcfg > notice: Finished catalog run in 689.95 seconds > This is because zones in OpenSolaris work differently than in Solaris 10.
Now a zone gets its own Boot Environment (be), which is a zfs root file system that doesn't get mounted until the zone is in the ready state. I'll file a bug for this... cheers, /Martin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
