microsoft/Service-Fabric-POA

Issues

• Reboot loop on failed KB5034439. Possible to skip?

  #93 opened 10 months ago by bevan-criticalarc
  0

• NodeAgentService instance stops during uncertain time

  #90 opened 2 years ago by joaofpereira
  1

• This repo is missing important files

  #88 opened 2 years ago by microsoft-github-policy-service
  1

• POA fails when WindowsUpdate registry key is missing

  #30 opened 4 years ago by tastyeggs
  3

• Exception in NodeAgentNTService.exe: The process was terminated due to an unhandled exception.

  #81 opened 4 years ago by jay1891
  0

• WUFrequency - Week, Day, HH:MM:SS not working (v1.4.9)

  #79 opened 4 years ago by rajakumarbabu
  2

• Patch Orchestrator schedules so many repair tasks that it interferes with the Cluster PlatformUpdate tasks scheduled by Azure

  #63 opened 4 years ago by emil-mi
  0

• CoordinatorService.exe consumes all memory

  #77 opened 4 years ago by JohnNilsson
  0

• Number of health reports on NodeAgentService goes above MaxSuggestedNumberOfEntityHealthReports when number of nodes are more than MaxSuggestedNumberOfEntityHealthReports/2.

  #33 opened 4 years ago by khandelwalbrijesh
  3

• Support for POA in Ephemeral OS Disks

  #71 opened 4 years ago by saketharsh
  1

• v1.4.6 release sfpkg is failing to deploy

  #73 opened 4 years ago by rootik
  4

• POA binaries are not Authenticode Signed.

  #70 opened 4 years ago by saketharsh
  1

• Environment considerations during windows update

  #40 opened 5 years ago by davebally
  3

• Cannot register PatchOrchestrationApplication_v1.4.5.sfpkg with SF Cluster - invalid path

  #65 opened 5 years ago by Jaans
  2

• POA constantly creates repair items when non-Windows OS updates fail to install.

  #64 opened 5 years ago by techmantonio
  0

• Patch Orchestration support for specifying day-of-week for monthly frequency

  #59 opened 5 years ago by adibalwani
  0

• Patch Orchestration Agent shows error when Automatic Updates Registry is Absent

  #60 opened 5 years ago by saketharsh
  0

• HMACSHA1 broke verification of settings

  #57 opened 5 years ago by JosePedroMarques
  2

• TimeManager.cs uses non-FIPS approved MD5 algorithm.

  #42 opened 5 years ago by milope
  1

• Patch Orchestration Application (POA) does not install updates in gMSA security cluster

  #34 opened 5 years ago by vdvarlamov
  13

• WURescheduleCount is not honoured when update install keeps on failing continously.

  #51 opened 5 years ago by khandelwalbrijesh
  1

• CoordinatorService crash if no completed repair tasks

  #49 opened 5 years ago by dapathy
  2

• POA should not trigger downloading of the update all at the same time

  #54 opened 5 years ago by jackliums
  0

• Patch operation getting stuck in the stages after installation is completed and restart is attempted

  #45 opened 5 years ago by khandelwalbrijesh
  1

• Patching issue with 1.4.1

  #47 opened 5 years ago by EinarasTU
  1

• Add ability to space out the update timing for services with long startup time.

  #37 opened 5 years ago by yossistarz
  3

• ClearOrphanEvents workflow does not work properly because of different health message.

  #43 opened 5 years ago by khandelwalbrijesh
  2

• POA creates repair tasks even when 0 number of updates are downloaded

  #38 opened 5 years ago by khandelwalbrijesh
  0

• Crash due to Heap Corruption in NodeAgentNTService

  #36 opened 5 years ago by khandelwalbrijesh
  0

• NodeAgentNTService crashes while reporting health.

  #35 opened 5 years ago by khandelwalbrijesh
  0

• POA reporting invalid DateTime setting after upgrade to 1.4.1

  #29 opened 5 years ago by krawls19
  3

• Image based patching

  #24 opened 5 years ago by JohnNilsson
  5

• NodeAgentNTService is stuck in stopping state and NodeAgentService is not able to come up on few nodes.

  #23 opened 5 years ago by khandelwalbrijesh
  1

• Timeout repair task tries to complete the Repair task and this leads to crash in PatchOrchestrationApplication

  #25 opened 5 years ago by khandelwalbrijesh
  2

• POA should check for chained updates by looking for updates immediately after completing installing one

  #21 opened 6 years ago by raunakpandya
  0

• Trigger installation immediately after deploying for first time

  #22 opened 6 years ago by raunakpandya
  0

• In case of reboot failure, POA should post a warning/ error indicating pending reboot

  #20 opened 6 years ago by raunakpandya
  0

• Retries should be added in POA FabricClient Calls.

  #19 opened 6 years ago by khandelwalbrijesh
  0

• Patch Orchestration application is not able to come up on some of the nodes, fails with the error that ServiceType is not registeret within configured timeout

  #8 opened 6 years ago by khandelwalbrijesh
  1

• NodeAgentNTService is not able to update its CopyOfSettings.xml file when user passes corrupt settings while deploying the application

  #12 opened 6 years ago by khandelwalbrijesh
  2

• POA is throwing warning that the repair task with id “POS__nodeId_9f62fad1-9f3b-485b-bd63-f8a1e19742b8” is not completed after timeout.

  #9 opened 6 years ago by khandelwalbrijesh
  2

• POA doesnt fetch updates for other Microsoft products

  #11 opened 6 years ago by raunakpandya
  0

• Build.ps1 fails with 401 unauthorized error.

  #7 opened 6 years ago by khandelwalbrijesh
  2