Closed
Bug 1048765
Opened 11 years ago
Closed 10 years ago
2008 Puppet: License are not activating through KMS
Categories
(Infrastructure & Operations :: RelOps: Puppet, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: markco, Assigned: markco)
References
Details
(Whiteboard: [windows])
A step will need to be added to the task sequence or with in the Puppet run to activate license. Puppet would be the better choice.
Assignee | ||
Updated•11 years ago
|
Assignee: relops → mcornmesser
Assignee | ||
Updated•11 years ago
|
Component: RelOps: Puppet → RelOps
QA Contact: dustin → arich
Assignee | ||
Comment 1•11 years ago
|
||
This has been moved into the task sequence. For some reason the command did to set KMS server would not set the server when ran by Puppet.
Steps added to task sequence:
C:\Windows\System32\cscript.exe C:\windows\system32\slmgr.vbs -skms "kms1.ad.mozilla.com
C:\Windows\System32\cscript.exe C:\windows\system32\slmgr.vbs /ato
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 2•11 years ago
|
||
I am reopening this bug. The kms manifest were incorrectly submitted in a patch. Also i want to take another look at getting this to work through Puppet.
Assignee | ||
Comment 3•11 years ago
|
||
When there is a DNS entry for kms pointing to kms1.ad.mozilla.com in ns1.private.releng.scl3.mozilla.com the license will activate without any further configuration. However, the machine will attempt to periodically re-authenticate its license with the server, and if it can't reach the server it will deactivate the license, so we may want to Puppet to verify that the license is activated and warn if it is not.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Updated•11 years ago
|
Component: RelOps → RelOps: Puppet
QA Contact: arich → dustin
Summary: Bare Metal Provisioning 2008 Puppet: Activate license through KMS → Bare Metal Provisioning 2008 Puppet: Support to verify license is activated through KMS
Updated•11 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/4135]
Comment 4•11 years ago
|
||
Puppet can't really do "warn" -- it can fail, or it can try to automatically fix (perhaps with /ato?)
Updated•10 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/4135] → [windows]
Assignee | ||
Updated•10 years ago
|
Summary: Bare Metal Provisioning 2008 Puppet: Support to verify license is activated through KMS → 2008 Puppet: Support to verify license is activated through KMS
Assignee | ||
Updated•10 years ago
|
Summary: 2008 Puppet: Support to verify license is activated through KMS → 2008 Puppet: License are not activating through KMS
Assignee | ||
Comment 5•10 years ago
|
||
The following srv records needed to be added:
_vlmcs._tcp.winbuild.releng.scl3.mozilla.com
_vlmcs._tcp.wintry.releng.scl3.mozilla.com
Without the winbuild or wintry suffix the activation attempts where failing because the local machine was not able to find the kms server.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•10 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 6•10 years ago
|
||
I also added entries for AWS build, test, and try VLANs in use1 and usw2:
_vlmcs._tcp.build.releng.use1.mozilla.com SRV kms1.ad.mozilla.com
_vlmcs._tcp.build.releng.usw2.mozilla.com SRV kms1.ad.mozilla.com
_vlmcs._tcp.test.releng.use1.mozilla.com SRV kms1.ad.mozilla.com
_vlmcs._tcp.test.releng.usw2.mozilla.com SRV kms1.ad.mozilla.com
_vlmcs._tcp.try.releng.use1.mozilla.com SRV kms1.ad.mozilla.com
_vlmcs._tcp.try.releng.usw2.mozilla.com SRV kms1.ad.mozilla.com
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Comment 7•10 years ago
|
||
Apparently we aren't using the KMS server for the MSDN licenses, just the OS, and that's handled through amazon directly. I removed the other SRV records so as not to conflict.
You need to log in
before you can comment on or make changes to this bug.
Description
•