copy edit

Author: tfitzmac

articles/cyclecloud/common-issues/fetching-resources.md

@@ -2,15 +2,15 @@
 title: Common Issues - Fetching Resource
 description: Azure CycleCloud common issue - Fetching Resources
 author: adriankjohnson
-ms.date: 11/15/2019
+ms.date: 06/30/2025
 ms.author: adjohnso
 ---
-# Common Issues: Fetching Resources
+# Common issues: Fetching resources
 
-## Possible Error Messages
+## Possible error messages
 
 - `Staging Resources (urlopen error [Errno 104] Socket closed)`
 
 ## Resolution
 
-This is usually due to a network error. Click on the "retry" link to see it was an intermittent issue. Check the Azure network status if the problem isn't resolved via retry.
+This error usually happens because of a network error. Select **retry** to see if it's an intermittent issue. Check the Azure network status if retry doesn't resolve the problem.

articles/cyclecloud/common-issues/marketplace-images.md

@@ -2,26 +2,26 @@
 title: Common Issues - Marketplace Images
 description: Azure CycleCloud common issue - Marketplace Images
 author: adriankjohnson
-ms.date: 11/15/2019
+ms.date: 06/30/2025
 ms.author: adjohnso
 ---
-# Common Issues: Marketplace Images
+# Common issues: Marketplace images
 
-## Possible Error Messages
+## Possible error messages
 
 - `Creating Virtual Machine (User failed validation to purchase resources)`
 
 ## Resolution
 
-When using a marketplace image with CycleCloud, the service principal must have appropriate permissions on the subscription to programmatically accept the licensing terms for the image. To resolve this issue, you may either grant the appropriate AAD permission to the service principal or use the Azure portal or CLI to accept the terms with a user with appropriate permissions.
+When you use a marketplace image with CycleCloud, the service principal must have the right permissions on the subscription to programmatically accept the licensing terms for the image. To resolve this issue, either grant the appropriate Microsoft Entra ID permission to the service principal or use the Azure portal or CLI to accept the terms with a user who has the right permissions.
 
 ::: moniker range=">=cyclecloud-8"
-To enable CycleCloud to automatically accept license terms on your behalf, enable the "Accept marketplace terms on my behalf" option on your subscription in the web interface:
+To enable CycleCloud to automatically accept license terms on your behalf, enable the **Accept marketplace terms on my behalf** option on your subscription in the web interface:
 
 ![Accept Marketplace terms](../images/auto-accept-terms.png)
 ::: moniker-end
 
-To accept a license terms from the Azure CLI:
+To accept license terms from the Azure CLI:
 
 ```azurecli-interactive
 az vm image accept-terms --urn PUBLISHER:OFFER:SKU:VERSION
@@ -33,7 +33,7 @@ or
 az vm image accept-terms --publisher PUBLISHER --offer OFFER --plan SKU
 ```
 
-## More Information
+## More information
 
-For more information, see [Marketplace Terms](https://azure.microsoft.com/support/legal/marketplace-terms/)
+For more information, see [Marketplace Terms](https://azure.microsoft.com/support/legal/marketplace-terms/).
 

articles/cyclecloud/common-issues/node-cyclecloud-connectivity.md

@@ -2,14 +2,14 @@
 title: Common Issues - Node Connectivity
 description: Azure CycleCloud common issue - Node Connectivity
 author: adriankjohnson
-ms.date: 11/15/2019
+ms.date: 06/30/2025
 ms.author: adjohnso
 ---
-# Common Issues: Node to CycleCloud Connectivity
+# Common issues: Node to CycleCloud connectivity
 
-CycleCloud installs an agent on each virtual machine that needs to communicate with the CycleCloud application. The agent reports status and monitoring and makes API requests for autoscaling and distributed synchronization.
+CycleCloud installs an agent on each virtual machine that needs to communicate with the CycleCloud application. The agent reports status and monitoring data and makes API requests for autoscaling and distributed synchronization.
 
-We recommend deploying the application server in the same virtual network as the cluster. If this configuration isn't feasible, establish connectivity by doing [virtual network peering](../network-connectivity.md#virtual-network-peering) or using a [proxy node](../network-connectivity.md#proxy-node). These error messages indicate that nodes can't communicate with the CycleCloud application server.
+We recommend deploying the application server in the same virtual network as the cluster. If you can't use this configuration, establish connectivity by doing [virtual network peering](../network-connectivity.md#virtual-network-peering) or using a [proxy node](../network-connectivity.md#proxy-node). These error messages indicate that nodes can't communicate with the CycleCloud application server.
 
 ## Possible error messages
 - `Timeout awaiting system boot-up`
@@ -23,9 +23,9 @@ We recommend deploying the application server in the same virtual network as the
 
 - If the CycleCloud server and the cluster are in the same virtual network, check the network security groups for the subnets in the virtual network. Cluster nodes need to reach the CycleCloud server at TCP 9443 and 5672. In the other direction, Azure CycleCloud needs to reach ganglia (TCP 8652) and SSH (TCP 22) ports of the cluster for system and job monitoring.
 
-- You might need to add a public IP address.
+- Add a public IP address.
 
-- If the error message indicates a return proxy, check the [return proxy settings](../how-to/return-proxy.md).
+- Check the [return proxy settings](../how-to/return-proxy.md) if the error message indicates a return proxy.
 
 - After updating network or proxy settings, test connectivity by SSHing into the node as the cyclecloud user and using `curl -k {https://error-message-url}`.
 

articles/cyclecloud/common-issues/node-timeout-await-bootup.md

@@ -2,37 +2,31 @@
 title: Common Issues - Phase timeout expired while awaiting system boot-up
 description: Azure CycleCloud common issue - Node Storage Resolution
 author: mvrequa
-ms.date: 04/15/2020
+ms.date: 06/30/2025
 ms.author: mirequa
 ---
-# Common Issues: Node Storage Resolution Failure
+# Common issues: Node storage resolution failure
 
-## Possible Error Messages
+## Possible error messages
 
 - `Phase timeout expired while awaiting system boot-up`
 
 ## Resolution
 
-Cyclecloud nodes use [custom script extension](/azure/virtual-machines/extensions/custom-script-linux)
-to install jetpack. The jetpack installer is staged into the locker during the initial node phase
-and downloaded by the node at start time. Cyclecloud transmits the blob url and the chosen authentication
-method to the node via the script extension.
+CycleCloud nodes use the [custom script extension](/azure/virtual-machines/extensions/custom-script-linux) to install Jetpack. The Jetpack installer is staged into the locker during the initial node phase and downloaded by the node at start time. CycleCloud sends the blob URL and the authentication method to the node through the script extension.
 
 The installer is downloaded to the following location on the node:
 
 _/var/lib/waagent/custom-script/download/0/jetpack-7.9.4-linux.tar.gz_
 
-In some cases the download can fail without raising an error. The indication for such a failure 
-is that this is a *zero-byte file*. 
+In some cases, the download fails without raising an error. The indication for such a failure is that the installer is a *zero-byte file*.
 
-Most commonly the storage account either can't be reached or the name can't be resolved. A
-minimal reproduction of this issue can be done with _cURL_ example here with the _7.9.4_ version.
+Most commonly, the failure happens because the storage account can't be reached or the name can't be resolved. You can reproduce this issue with a minimal example using _cURL_ for version _7.9.4_.
 
 ```bash
 curl https://<storage-account>.blob.core.windows.net/cyclecloud/cache/jetpack/7.9.4/jetpack-7.9.4-linux.tar.gz
 ```
 
-A "success" results in a 404 http response. Afflicted nodes will show a _cURL_ error: host not resolvable or host timeout.
+A "success" results in a 404 HTTP response. Afflicted nodes show a _cURL_ error: host not resolvable or host timeout.
 
-To fix this and subsequent nodes, take action to repair the storage account 
-resolution either by investigating the node DNS resolution or firewall rules.
+To fix this issue and subsequent nodes, take action to repair the storage account resolution by investigating the node DNS resolution or firewall rules.

articles/cyclecloud/common-issues/osProfile.md

@@ -2,17 +2,17 @@
 title: Common Issues - os.Profile
 description: Azure CycleCloud common issue - os.Profile
 author: adriankjohnson
-ms.date: 07/24/2021
+ms.date: 06/30/2025
 ms.author: adjohnso
 ---
-# Common Issues: Parameter os.Profile
+# Common issues: Parameter os.Profile
 
-## Possible Error Messages
+## Possible error messages
 
 - `Parameter "os.Profile" is not allowed`
 
 ## Resolution
 
-Azure CycleCloud allows you to use [custom images](~/articles/cyclecloud/how-to/create-custom-image.md) but the custom image must be created from a generalized image. Since specialized images do not have an `osProfile` associated with them, errors are encountered when the osProfile parameter is passed to the custom image.
+Azure CycleCloud allows you to use [custom images](~/articles/cyclecloud/how-to/create-custom-image.md), but you must create the custom image from a generalized image. Since specialized images don't have an `osProfile` associated with them, you encounter errors when you pass the osProfile parameter to the custom image.
 
-Recreate your custom image using a generalized image to resolve.
+Recreate your custom image using a generalized image to resolve the issue.

articles/cyclecloud/common-issues/registering-providers.md

@@ -2,22 +2,22 @@
 title: Common Issues - Azure Credentials| Microsoft Docs
 description: Azure CycleCloud common issue - Azure Credentials
 author: adriankjohnson
-ms.date: 06/20/2023
+ms.date: 06/30/2025
 ms.author: adjohnso
 ms.topic: conceptual
 ms.service: azure-cyclecloud
 ms.custom: compute-evergreen
 ---
-# Common Issues: Azure provider registration error
+# Common issues: Azure provider registration error
 
-## Possible Error Messages
+## Possible error messages
 
 - `Failed to register Azure providers`
 
 ## Resolution
-Before you can use your Azure subscription, Azure requires that you register access to the Azure resource providers. CycleCloud, when adding new accounts, will attempt to register the providers for use in your subscription. If the service principal configured for CycleCloud does not have permission to register the providers, this error will occur.
+Before you can use your Azure subscription, Azure requires that you register access to the Azure resource providers. CycleCloud attempts to register the providers for use in your subscription when you add new accounts. This error occurs if the service principal configured for CycleCloud doesn't have permission to register the providers.
 
-There are two possible resolutions:
+Resolve this error by doing one of the following steps:
 1. Grant the CycleCloud service principal the following permissions:
     - `Microsoft.Compute/register/action`
     - `Microsoft.Storage/register/action`
@@ -34,6 +34,6 @@ az provider register --namespace "Microsoft.Resources"
 az provider register --namespace "Microsoft.Commerce"
 ```
 
-## More Information
+## More information
 
-For more information on specific permissions required for Azure CycleCloud, see [Create a custom role for CycleCloud](/azure/cyclecloud/managed-identities#create-a-custom-role-and-managed-identity-for-cyclecloud)
+For more information on specific permissions required for Azure CycleCloud, see [Create a custom role for CycleCloud](/azure/cyclecloud/managed-identities#create-a-custom-role-and-managed-identity-for-cyclecloud).

articles/cyclecloud/common-issues/resolving-cookbooks.md

@@ -2,33 +2,33 @@
 title: Common Issues - Resolving Cookbooks
 description: Azure CycleCloud common issue - Resolving Cookbooks
 author: adriankjohnson
-ms.date: 11/15/2019
+ms.date: 06/30/2025
 ms.author: adjohnso
 ---
-# Common Issues: Error resolving Chef cookbooks or Chef::Exceptions:RecipeNotFound
+# Common issues: Error resolving Chef cookbooks or Chef::Exceptions:RecipeNotFound
 
-## Possible Error Messages
+## Possible error messages
 
 - `Error resolving Chef cookbooks - No such cookbook: {FOO}`
 - `Chef::Exceptions::RecipeNotFound: could not find recipe bar for cookbook {FOO}`
 
 ## Resolution
 
-Node startup with jetpack will load Chef cookbooks from various sources. The cookbooks will be copied to `/opt/cycle/jetpack/system/chef/chef-repo/cookbooks`. Encountering this error indicates that jetpack did not load the cookbook from any of the potential sources. The sources include projects, referenced in the cluster-init specs for the node, and CycleCloud internal cookbooks.
+When a node starts with jetpack, it loads Chef cookbooks from different sources. Jetpack copies these cookbooks to `/opt/cycle/jetpack/system/chef/chef-repo/cookbooks`. If you see this error, it means jetpack didn't load the cookbook from any of the possible sources. These sources include projects that the cluster-init specs reference for the node and CycleCloud internal cookbooks.
 
-The required cookbooks are derived from the node _configuration.run_list_. You may see `run_list = recipe[foo]` or `= recipe[foo::bar]`. These run_lists both specify the `foo` cookbook and either the `default` or `bar` recipe in those cookbooks.
+The node's _configuration.run_list_ determines which cookbooks you need. You might see `run_list = recipe[foo]` or `= recipe[foo::bar]`. Both run_lists specify the `foo` cookbook and either the `default` or `bar` recipe in those cookbooks.
 
-Make sure the cookbook exists in the project
+Check that the cookbook exists in the project
 
-1. Make sure the cookbook `foo` exists in the project.
-1. Make sure the cookbook `foo` contains the recipe `bar`.
-1. Make sure the project containing `foo` has been uploaded to the storage locker.
-1. Make sure the spec is referenced in the cluster-init for the node.
-1. Make sure the version of the spec reference by the node is the same as the version of the spec containing the cookbook.
+1. Check that the `foo` cookbook exists in the project.
+1. Check that the `foo` cookbook contains the `bar` recipe.
+1. Make sure you uploaded the project containing `foo` to the storage locker.
+1. Make sure you reference the spec in the cluster-init for the node.
+1. Make sure the version of the spec reference by the node matches the version of the spec containing the cookbook.
 
 `RecipeNotFound` indicates that the cookbook can be found, but that the cookbook is missing a designated recipe.
 
-## More Information
+## More information
 
-Lean more about [CycleCloud Projects](~/articles/cyclecloud/how-to/projects.md)
+Learn more about [CycleCloud Projects](~/articles/cyclecloud/how-to/projects.md).
 

articles/cyclecloud/common-issues/resource-group-privileges.md

@@ -2,20 +2,20 @@
 title: Common Issues - Resource Group Privilege
 description: Azure CycleCloud common issue - Resource Group Privilege
 author: adriankjohnson
-ms.date: 11/15/2019
+ms.date: 06/30/2025
 ms.author: adjohnso
 ---
-# Common Issues: Azure Resource Group Privileges
+# Common issues: Azure resource group privileges
 
-## Possible Error Messages
+## Possible error messages
 
 - `Resource group {GROUP} for restricted credential {CRED} does not exist`
 - `Error creating resource group {GROUP} for credential`
 
 ## Resolution
 
-Azure CycleCloud, by default, creates a new resource group for each cluster. If the service principal associated with the credential does not have permission to create or access the resource group used by the cluster, CycleCloud will not operate. In the case of a "restricted" credential, one that uses a single resource group for all clusters, the resource group must be created and appropriate permissions applied.
+By default, Azure CycleCloud creates a new resource group for each cluster. If the service principal associated with the credential doesn't have permission to create or access the resource group used by the cluster, CycleCloud doesn't operate. For a "restricted" credential that uses a single resource group for all clusters, you must create the resource group and apply the appropriate permissions.
 
-## More Information
+## More information
 
-For more information, see [Configuring Azure Credentials](/azure/cyclecloud/configuration)
+For more information, see [Configuring Azure Credentials](/azure/cyclecloud/configuration).

articles/cyclecloud/common-issues/scaleset-attributes.md

@@ -2,19 +2,19 @@
 title: Common Issues - Scaleset Attribute| Microsoft Docs
 description: Azure CycleCloud common issue - Scaleset Attribute
 author: adriankjohnson
-ms.date: 11/15/2019
+ms.date: 06/30/2025
 ms.author: adjohnso
 ---
-# Common Issues: ScaleSet Attributes
+# Common issues: Scale set attributes
 
-## Possible Error Messages
+## Possible error messages
 
 - `This node does not match existing scaleset attributes`
 
 ## Resolution
 
-This error can occur when changing material aspects (global settings such as ImageId, MachineType, etc.) of your nodearray while it has running nodes. For example, if you change the definition of an MPI nodearray to use a different image, new nodes from the autoscaler will not match the last known configuration of the underlying scale set. 
+This error can occur when you change material aspects (global settings such as ImageId, MachineType, and so on) of your node array while it has running nodes. For example, if you change the definition of an MPI node array to use a different image, new nodes from the autoscaler don't match the last known configuration of the underlying scale set. 
 
-Potential resolutions to this error:
-- Terminate the running VMs in the nodearray to allow new nodes to use the new configuration, or, 
-- Terminate the new nodes with the error, undo the edits and save, start new nodes to keep the old configuration.
+To resolve this error, you can:
+- Terminate the running VMs in the node array to allow new nodes to use the new configuration, or
+- Terminate the new nodes with the error, undo the edits, and save. Start new nodes to keep the old configuration.

articles/cyclecloud/common-issues/slurmd-errors.md

@@ -2,19 +2,19 @@
 title: Common Issues - Slurm Configuration| Microsoft Docs
 description: Azure CycleCloud common issue - Slurm Configuration
 author: adriankjohnson
-ms.date: 11/15/2019
+ms.date: 06/30/2025
 ms.author: adjohnso
 ---
-# Common Issues: Slurm configuration errors
+# Common issues: Slurm configuration errors
 
-## Possible Error Messages
+## Possible error messages
 
 - `Unable to execute command /usr/bin/systemctl --system start slurmd`
 
 ## Resolution
 
-Because Slurm requires all of the nodes of a cluster to be defined in slurm.conf, CycleCloud pre-creates all of the VMs inside of CycleCloud when the scheduler node is first started. These VMs remain unallocated in Azure until a job requests them, but sometimes insufficient quota or incorrect autoscale limits can cause installation issues. 
+Because Slurm requires all of the nodes of a cluster to be defined in `slurm.conf`, CycleCloud pre-creates all of the VMs inside of CycleCloud when you first start the scheduler node. These VMs remain unallocated in Azure until a job requests them, but sometimes insufficient quota or incorrect autoscale limits cause installation issues. 
 
-- Make sure your subscription has enough quota for the selected VM type and that the autoscale limits are below the quota amount. You may have to select a different VM type or adjust your autoscale limits accordingly.
-- Check in `/var/log/slurmctld/slurm.log` for any errors related to starting the scheduler.
+- Make sure your subscription has enough quota for the selected VM type and that the autoscale limits are below the quota amount. You might have to select a different VM type or adjust your autoscale limits.
+- Check `/var/log/slurmctld/slurm.log` for any errors related to starting the scheduler.