Skip to content

Oracle WebLogic Server Cluster deployment failed #137

@majguo

Description

@majguo

Problem description

Failed to deploy Oracle WebLogic Server Cluster from Azure portal, the deployment of embedded template clusterLinkedTemplate failed with the following error messages:

{
  "code": "DeploymentFailed",
  "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
  "details": [
    {
      "code": "VMExtensionProvisioningError",
      "message": "VM has reported a failure when processing extension 'newuserscript'. Error message: \"Enable failed: processing file downloads failed: failed to download file[1]: failed to download file: unexpected status code: actual=404 expected=200\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionCSELinuxTroubleshoot "
    },
    {
      "code": "VMExtensionProvisioningError",
      "message": "VM has reported a failure when processing extension 'newuserscript'. Error message: \"Enable failed: processing file downloads failed: failed to download file[1]: failed to download file: unexpected status code: actual=404 expected=200\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionCSELinuxTroubleshoot "
    }
  ]
}

How to reproduce

Follow steps below to reproduce the issue:

  1. Open Oracle WebLogic Server Cluster offer.
  2. In "Basics" page: Fill in value for the required field(s). Click "Review + Create". Click "Create".
  3. Wait until the deployment of embedded template clusterLinkedTemplate failed.

Potential RCA

The clusterTemplate will look for some files from ../../../../../utilities/custom-hostname-verifier/, which seems to depend on the recent changes of parent pom com.microsoft.azure.iaas:azure-javaee-iaas-parent:

Specifically, the dependent parent pom com.microsoft.azure.iaas:azure-javaee-iaas-parent has been updated to 1.0.15 in order to add utilities directory from WebLogic offers, see PR-24. However, the old version 1.0.13 and its commit hash 13fe6ec487024eb61355d661ab5700ae90cb0a8f are NOT updated accordingly:

It looks like all upstream WebLogic offers that're impacted by the PR-24 should be checked, verified and updated appropriately.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions