Closed Bug 760127 Opened 12 years ago Closed 12 years ago

new reference images need to be taken

Categories

(Infrastructure & Operations :: RelOps: General, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bear, Assigned: dividehex)

References

Details

(Whiteboard: [buildduty])

the following ref images have been updated for cltbld (and root where appropriate) password changes:

linux64-ix-ref
linux-ix-ref
talos-r3-fed64-ref
talos-r3-fed-ref
moz2-darwin10-ref
talos-r3-leopard-ref
talos-r4-snow-ref

    talos-r4-lion-ref - cltbld
Whiteboard: [buildduty]
What about:
 t-r3-w764-ref
 talos-r3-w7-ref
 talos-r3-xp-ref
 talos-r4-lion-ref (which you just list cltbld for?)
 win32-ix-ref

Also, was the Administrator account also updated on mac and windows machines?

Note: this will also require an mtv1 colo trip for moz2-darwin10-ref.
Assignee: server-ops-releng → jwatkins
colo-trip: --- → scl1
I spoke to bear, and he said if he didn't mention it in the original description, it hasn't been done yet.

To add to my list in comment 1, the build and try vms in scl3, but I think we'll need to do those since the templates don't get IPs.
talos-r4-lion-ref  root,cltbld passwords updated
talos-r4-lion-ref    root,cltbld passwords confirmed
talos-r4-snow-ref    root,cltbld passwords confirmed
talos-r3-leopard-ref root,cltbld passwords confirmed
moz2-darwin10-ref    root,cltbld,Administrator passwords confirmed
talos-r3-fed-ref     root,cltbld passwords confirmed
talos-r3-fed64-ref   root,cltbld passwords confirmed
linux-ix-ref         root,cltbld passwords confirmed
linux64-ix-ref       root,cltbld passwords confirmed
win32-ix-ref         cltbld,Administrator passwords confirmed
talos-r3-xp-ref      cltbld,Administrator passwords confirmed

These two I got errors about not being able to reach the AD when trying to change passwords
t-r3-w764-ref
talos-r3-w7-ref
t-r3-w764-ref    cltbld password confirmed
talos-r3-w7-ref  cltbld password confirmed
talos-r3-fed-ref     New Image taken
talos-r3-fed64-ref   New Image taken
bear: I can't VNC (ssh works) into talos-r4-lion-ref or talos-r4-snow-ref which might be caused by autologin passwd being outdated.
Blocks: 761846
talos-r4-snow-ref is now working for me

talos-r4-lion-ref refuses to fix...

[16:06]  <bear> arr - to confirm... I copied kcpassword from bld-lion-r5-022 and pushed that to talos-r4-lion-ref
[16:06]  <bear> and vnc just shutsdown after sending the password for login
[16:06]  <bear> and I confirmed that bld-lion-r5-022 works by vnc'ing to it 
[16:07]  <arr> bear: hm, actually was the ref machine one of the ones that got "fixed" previously (when the lion machines got hosed?)
[16:07]  <arr> we may need to reimage it


let's reimage it and try again
Bear: talos-r4-lion-ref has been restored to the previous ref image

linux-ix-ref         New image taken
linux64-ix-ref       New image taken
talos-r4-snow-ref    New image taken
talos-r4-lion-ref cltbld,vnc confirmed password changed
talos-r4-lion-ref     New image taken
win32-ix-ref          New image taken
Bear:  Can you take a look at t-r3-w764-ref and talos-r3-w7-ref?  Both MaRu and I were unable to VNC into these machines although RDP worked.
:dividehex

I've fixed the autologon and vnc configs for those two.

For future folk, I had to completely remove and reinstall the ultravnc service, it seems the device driver that ultravnc requires for windows vista/7 did not survive whatever work had been done to these two images.

I also had to recreate the autologon entries following this article:

http://superuser.com/questions/28647/how-do-i-enable-automatic-logon-in-windows-7-when-im-on-a-domain

(thanks Callek!)

which outlines the following (in case the above link every goes missing):

-----
1. Click Start, click Run, type regedit, and then click OK. In Windows Vista/7, simply type regedit in Start Search and hit Enter.

2. Navigate to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

3. Double-click the DefaultUserName entry, type the user name to log on with, and then click OK.

If DefaultUserName registry value name is not found, create a new String Value (REG_SZ) with value name as DefaultUserName.

4. Double-click the DefaultPassword entry, type the password for the user account under the value data box, and then click OK.

If there is no DefaultPassword value, create a new String Value (REG_SZ) with DefaultPassword as the value name.

Note that if no DefaultPassword string is specified, Windows automatically changes the value of the AutoAdminLogon registry key from 1 (true) to 0 (false) to turn off the AutoAdminLogon feature.

5. In Windows Vista/7, DefaultDomainName has to be specified as well, else Windows will prompt for invalid user name with the user name displayed as .\username. To do so, double click on DefaultDomainName, and specify the domain name of the user account. If it’s local user, specify local host name.

If the DefaultDomainName does not exist, create a new String Value (REG_SZ) registry key with value name as DefaultDomainName.

6. Double-click the AutoAdminLogon entry, type 1 in the Value Data box, and then click OK.

If there is no AutoAdminLogon entry, create a new String Value (REG_SZ) with AutoAdminLogon as the value name.

7. If it exists, delete the AutoLogonCount key.

8. Quit Registry Editor.

9. Click Start, click Restart, and then click OK.
-----
Images taken today:

talos-r3-leopard-ref
moz2-darwin10-ref 
talos-r3-xp-ref 
t-r3-w764-ref
talos-r3-w7-ref


All ref images are up to date.
All images taking today with the exception of moz2-darwin10-ref have been copied over to pxe1 (scl1) and workflows have been updated.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.