Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-6559

Installation manager could be unable to delete the candidate server when running in PowerShell

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 23.0.0.Beta1, 23.0.0.Final
    • None
    • None
    • None
    • Hide

      1. Explicitly disable the long paths support on the Windows machine via Local Group Policy Editor: Computer Configuration > Administrative Templates > System > Filesystem > Enable Win32 long paths
      2. Start the server in porweshell
      3. Update it from any CLI client (linux, windows ..)

      Show
      1. Explicitly disable the long paths support on the Windows machine via Local Group Policy Editor: Computer Configuration > Administrative Templates > System > Filesystem > Enable Win32 long paths 2. Start the server in porweshell 3. Update it from any CLI client (linux, windows ..)

      When a candidate server is created, it is stored at $WFLY_HOME/standalone/tmp/installation-manager/prepared-server/.

      Once the new server is applied, the installation-manager.ps1 script deletes the candidate server and initializes the installation manager to be ready to prepare a new server.

      The delete operation could fail if the OS is not configured to support long paths, either via Windows Registry or policy templates, see https://learn.microsoft.com/en-ca/windows/win32/fileio/maximum-file-path-limitation?tabs=registry for more information.

              yborgess1@redhat.com Yeray Borges Santana
              yborgess1@redhat.com Yeray Borges Santana
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: