Closed Bug 1485213 (T-W1064-MS-116) Opened 7 years ago Closed 7 years ago

[MDC1] T-W1064-MS-116 problem tracking

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: riman, Unassigned)

References

Details

Attachments

(1 file)

Attached image t-w1064-ms-116.PNG
This machine is missing from Taskcluster. I did not succeed to re-image it because of: (see the attachment)
What you can see in the above attachment happens if a re-imaging process is interrupted (usually by continuous pxe boot). I've re-imaged it again making sure it boots accordingly and has now started a job. Will leave this opened for one more day to see if it continues working. https://tools.taskcluster.net/provisioners/releng-hardware/worker-types/gecko-t-win10-64-hw/workers/mdc1/T-W1064-MS-116
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
No jobs for one day, rebooted still no jobs. Errors bellow. This will be reimaged. Oct 02 23:18:22 T-W1064-MS-116.mdc1.mozilla.com Microsoft-Windows-DSC: Job {E1A5C1AF-C6D3-11E8-9A5B-F40343DF3306} : This event indicates that failure happens when LCM is processing the configuration. Error Id is 0x1. Error Detail is The SendConfigurationApply function did not succeed.. Resource Id is [Package]MsiInstall_Mercurial and Source Info is C:\windows\TEMP\xDynamicConfig.ps1::385::9::Package. Error Message is PowerShell DSC resource MSFT_PackageResource failed to execute Set-TargetResource functionality with error message: The specified Name (Mercurial 4.7.1 (x64)) and IdentifyingNumber ({68FA175A-0F28-49AF-9E65-30CE6B60AE1C}) do not match Name (Mercurial 4.5.3 (x64)) and IdentifyingNumber ({3F975FA0-6C28-4A37-882B-2AB806D67736}) in the MSI file .#015 Oct 02 23:18:22 T-W1064-MS-116.mdc1.mozilla.com Microsoft-Windows-DSC: Job {E1A5C1AF-C6D3-11E8-9A5B-F40343DF3306} : MIResult: 1 Error Message: PowerShell DSC resource MSFT_PackageResource failed to execute Set-TargetResource functionality with error message: The specified Name (Mercurial 4.7.1 (x64)) and IdentifyingNumber ({68FA175A-0F28-49AF-9E65-30CE6B60AE1C}) do not match Name (Mercurial 4.5.3 (x64)) and IdentifyingNumber ({3F975FA0-6C28-4A37-882B-2AB806D67736}) in the MSI file Message ID: ProviderOperationExecutionFailure Error Category: 7 Error Code: 1 Error Type: MI#015 Oct 02 23:19:47 T-W1064-MS-116.mdc1.mozilla.com Microsoft-Windows-DSC: Job {E1A5C1AF-C6D3-11E8-9A5B-F40343DF3306} : Job runs under the following LCM setting. ConfigurationMode: ApplyAndMonitor ConfigurationModeFrequencyMins: 15 RefreshMode: PUSH RefreshFrequencyMins: 30 RebootNodeIfNeeded: NONE DebugMode: False#015 Oct 02 23:19:47 T-W1064-MS-116.mdc1.mozilla.com Microsoft-Windows-DSC: RESULT 1 [NXLOG@14506 Keywords="4611686018427387904" EventType="ERROR" EventID="4252" ProviderGuid="{50DF9E12-A8C4-4939-B281-47E1325BA63E}" Version="0" Task="0" OpcodeValue="0" RecordNumber="45667" ActivityID="{9377881E-5AE0-0000-839D-7793E05AD401}" ThreadID="6464" Channel="Microsoft-Windows-DSC/Operational" Domain="NT AUTHORITY" AccountName="SYSTEM" UserID="S-1-5-18" AccountType="User" Opcode="Info" JobId="{E1A5C1AF-C6D3-11E8-9A5B-F40343DF3306}" MIResult="1" ErrorMessage="The SendConfigurationApply function did not succeed." ErrorCategory="0" ErrorCode="1" ErrorType="MI" EventReceivedTime="2018-10-03 06:19:46" SourceModuleName="eventlog" SourceModuleType="im_msvistalog"] Job {E1A5C1AF-C6D3-11E8-9A5B-F40343DF3306} : MIResult: 1 Error Message: The SendConfigurationApply function did not succeed. Message ID: MI RESULT 1 Error Category: 0 Error Code: 1 Error Type: MI#015 Oct 02 23:19:47 T-W1064-MS-116.mdc1.mozilla.com Microsoft-Windows-DSC: Job {E1A5C1AF-C6D3-11E8-9A5B-F40343DF3306} : Details logging completed for C:\windows\System32\Configuration\ConfigurationStatus\{E1A5C1AF-C6D3-11E8-9A5B-F40343DF3306}-0.details.json.#015 Oct 02 23:19:47 T-W1064-MS-116.mdc1.mozilla.com Microsoft-Windows-DSC: Job DscTimerConsistencyOperationResult : DSC Engine Error : #011 Error Message: NULL #011Error Code : 1 #015 Oct 02 23:20:52 T-W1064-MS-116.mdc1.mozilla.com Microsoft-Windows-DSC: The local configuration manager was shut down.#015 Oct 02 23:26:54 T-W1064-MS-116.mdc1.mozilla.com VSS: Volume Shadow Copy Service information: The COM Server with CLSID {0b5a2c52-3eb9-470a-96e2-6c6d4570e40f} and name Coordinator cannot be started. [0x80070422, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ] #015 Oct 02 23:26:54 T-W1064-MS-116.mdc1.mozilla.com VSS: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80070422, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. . #015 Oct 02 23:27:11 T-W1064-MS-116.mdc1.mozilla.com VSS: Volume Shadow Copy Service information: The COM Server with CLSID {e579ab5f-1cc4-44b4-bed9-de0991ff0623} and name IVssCoordinatorEx2 cannot be started. [0x80070422, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ] Operation: Instantiating VSS server#015 Oct 02 23:27:11 T-W1064-MS-116.mdc1.mozilla.com VSS: Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80070422, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. . Operation: Instantiating VSS server#015
Status: RESOLVED → REOPENED
Flags: needinfo?(mcornmesser)
Resolution: FIXED → ---
I think this is related to bug 1493759.
Flags: needinfo?(mcornmesser)
Reimaged, running tasks.
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: