Re: [zones-discuss] Upgrade from 127 to 128a blew up all my zones

2009-12-08 Thread Jerry Jelinek
Robert Hartzell wrote: My normal procedure is to image-update, reboot, check that everything is working then update each zone. This has always worked because the zones would still be running. All my external services are running in zones (dns, smtp, http, ftp) so when I reboot I have no dns

[zones-discuss] Upgrade from 127 to 128a blew up all my zones

2009-12-07 Thread Robert Hartzell
I have upgraded 3 systems from 127 to 128a and all the zones basically have the same error. autofs is in maintenance with 17 dependent services not running. I haven't upgraded the zones because they are in production and don't want to have to recreate all 7 of them again. Is this a known issue

Re: [zones-discuss] Upgrade from 127 to 128a blew up all my zones

2009-12-07 Thread Jerry Jelinek
Robert Hartzell wrote: I have upgraded 3 systems from 127 to 128a and all the zones basically have the same error. autofs is in maintenance with 17 dependent services not running. I haven't upgraded the zones because they are in production and don't want to have to recreate all 7 of them

Re: [zones-discuss] Upgrade from 127 to 128a blew up all my zones

2009-12-07 Thread Robert Hartzell
Jerry Jelinek wrote: Robert Hartzell wrote: I have upgraded 3 systems from 127 to 128a and all the zones basically have the same error. autofs is in maintenance with 17 dependent services not running. I haven't upgraded the zones because they are in production and don't want to have to