Troubleshoot Deployments of Images from Azure Marketplace Using CloudCenter

Available Languages

Download Options

  • PDF     (6.1 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (76.0 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (70.5 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:August 1, 2017
Document ID:211529

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

    Introduction

    This document describes on how to troubleshoot the deployments of Azure Marketplace images from CloudCenter deploying very slowly.

    Prerequisites

    Requirements

    Cisco recomments that you have knowledge of these topics:

    • How to deploy Azure marketplace images using CloudCenter
    • How to use AzureRM
    • How to put osmosix logs in debug mode

    Components Used

    This information in this document is based on these software and hardware versions:

    • CCO and AMQP of any version being deployed on a AzureRM cloud

    The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

    Troubleshoot Deployments of Images from Azure Marketplace Using CloudCenter

    The main symptom to look out for when you face issues while deploying virtual machines from Azure Marketplace images is the amount of time it takes to fully deploy. With this issue, basic deployments of a base operating system can take 15 to 20 minutes to deploy. These are some points to check in order to identify whether the issue is with Azure Marketplace or CloudCenter.

    1. Check the osmosix.log file on the CloudCenter Orchestrator (CCO)

      The full error message to look out for is:
      DEBUG azure.AzureNetworkService [threadPoolExecutor-1]  - Failed to create network interface, retrying...
java.util.concurrent.ExecutionException: com.microsoft.windowsazure.exception.ServiceException: 404: Operation e7489b92-676e-4a33-8bd8-0654976551a8 not found.
    2. Log in to Azure account and check AzureRM notifications for any notifications about virtual machine provisioning of Azure Marketplace images.

    3. Test deployments of custom images if experiencing the large delay

    If the issue is Azure, then the error message listed in step 1 shows up many times, as Cloud Center keeps waiting on Azure. Custom images are not affected by the slow down either, so if custom images deploy quickly then the issue likely lies with Azure.

    Follow these steps to determine if the cause of slowness in deploying Azure Marketplace virtual machines is due to CloudCenter or Azure.

    TAC Authored

    Contributed by Cisco Engineers

    • Mitch Cramer
      Cisco TAC Engineer

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco

    This Document Applies to These Products