If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

OSX 10.10 deploystudio workflow

RESOLVED FIXED

Status

Infrastructure & Operations
RelOps
RESOLVED FIXED
3 years ago
3 months ago

People

(Reporter: dividehex, Assigned: dividehex)

Tracking

Details

(Assignee)

Description

3 years ago
In support of the upcoming OS X 10.10 Yosemite work, we will need a Deploy Studio workflow for testers (and possible builders).  The expectation is the same as previous workflows, a minimal base image which will be puppetized.
(Assignee)

Updated

3 years ago
Depends on: 1059445
(Assignee)

Updated

3 years ago
Depends on: 1059578
(Assignee)

Comment 1

3 years ago
I've added a new group (t-yosemite-r5) and workflow (restore t-yosemite-r5) to install.test.releng.scl3.  t-mavericks-r5-003 as been allocated in bug1059578 for testing.  I'm really hoping this will 'just work' on yosemite and not require a new deploystudio version.
(Assignee)

Comment 2

3 years ago
First run of the workflow seemed to execute without any issue but never returned after the reboot.  Filed bug1060135.
Depends on: 1060135
(Assignee)

Updated

3 years ago
Depends on: 1061837
(Assignee)

Updated

3 years ago
Depends on: 1063687
(Assignee)

Comment 3

3 years ago
Now that we have a base 10.10 Yosemite image (that works), I've updated the new workflow to handle 10.10.
Particularly, I enabled CoreStorage conversion on the Deploy Image task.  After deployment, this converts the disk to Apples LVM (CoreStorage).  I've also created a new package set to include puppet 3.7.0 and facter 2.2.0.  Puppet 3.7.0 is a requirement for 10.10 compatibility. See bug1065184.

And last, I've fixed the typo in DSR-10100 Netboot set.  This was preventing the DS runtime from authenticating and starting automatically.  The file is located in the NetInstall.sparseimage dmg under /Library/Preferences/com.deploystudio.server.plist.  It is a binary file so vim -b to modify bits.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
(Assignee)

Updated

3 years ago
No longer depends on: 1059578
On startup, this image is displaying the setup assistant, asking for an Apple ID.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Every time we create a DS image, we do a deploy, go through the initial setup, then take a snapshot so that we bypass the initial setup (time, language, apple ID, etc). If we didn't do that with 10.10, we need to do so on a clean machine (without running puppet on it).
Having just upgraded to Mavericky, I noticed that it won't boot without asking for an apple id, until you give it one.  Presumably Yosemite is the same.  Do we have an Apple ID to put in there?
I added the releng apple ID to the relops passwords.txt.gpg file. I think that should work here?
http://derflounder.wordpress.com/2013/10/27/disabling-the-icloud-sign-in-pop-up-message-on-lion-and-later/
That link has a script, although I haven't tested it yet.  Thoughts on
 (a) run the script by hand and capture the result
 (b) run the script as a DS step
 (c) run the script via puppet
?
I confirmed that (c) is an option - puppetize.sh and puppet run at first boot, and it's only on the automatic login that the iCloud login appears.
It's a per-user setting, so we have to do it in Puppet.  Still, 

>  defaults write "${USER_HOME}"/Library/Preferences/com.apple.SetupAssistant DidSeeCloudSetup -bool TRUE

seems to do the trick and

>  defaults write "${USER_HOME}"/Library/Preferences/com.apple.SetupAssistant GestureMovieSeen none
>  defaults write "${USER_HOME}"/Library/Preferences/com.apple.SetupAssistant LastSeenCloudProductVersion "${sw_vers}"

can't hurt.
..which means this should be in bug 1078882.
Status: REOPENED → RESOLVED
Last Resolved: 3 years ago3 years ago
Resolution: --- → FIXED

Updated

3 months ago
See Also: → bug 1372964
You need to log in before you can comment on or make changes to this bug.