You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -84,6 +84,14 @@ To fix this, the credentials in the appliance VM need to be updated. For more in
84
84
85
85
86
86
87
+
88
+
89
+
90
+
91
+
92
+
93
+
94
+
87
95
## Networking issues
88
96
89
97
### Back-off pulling image error
@@ -102,8 +110,6 @@ When trying to set the configuration for Arc resource bridge, you may receive an
102
110
103
111
This occurs when a `.local` path is provided for a configuration setting, such as proxy, dns, datastore or management endpoint (such as vCenter). Arc resource bridge appliance VM uses Azure Linux OS, which doesn't support `.local` by default. A workaround could be to provide the IP address where applicable.
104
112
105
-
106
-
107
113
### Azure Arc resource bridge is unreachable
108
114
109
115
Azure Arc resource bridge (preview) runs a Kubernetes cluster, and its control plane requires a static IP address. The IP address is specified in the `infra.yaml` file. If the IP address is assigned from a DHCP server, the address can change if not reserved. Rebooting the Azure Arc resource bridge (preview) or VM can trigger an IP address change, resulting in failing services.
@@ -187,21 +193,7 @@ Error: Error in reading OVA file: failed to parse ovf: strconv.ParseInt: parsing
187
193
value out of range.
188
194
```
189
195
190
-
This error occurs when you run the Azure CLI commands in a 32-bit context, which is the default behavior. The vSphere SDK only supports running in a 64-bit context. The specific error returned from the vSphere SDK is `Unable to import ova of size 6GB using govc`. When you install the Azure CLI, it's a 32-bit Windows Installer package. However, the Azure CLI `az arcappliance` extension needs to run in a 64-bit context.
191
-
192
-
To resolve this issue, perform the following steps to configure your management machine with the Azure CLI 64-bit version:
193
-
194
-
1. Uninstall the current version of the Azure CLI on Windows following these [steps](/cli/azure/install-azure-cli-windows#uninstall).
195
-
1. Install version 3.6 or higher of [Python](https://www.python.org/downloads/windows/) (64-bit).
196
-
197
-
> [!IMPORTANT]
198
-
> After you install Python, make sure to confirm that its path is added to the PATH environmental variable.
199
-
200
-
1. Install the [pip](https://pypi.org/project/pip/) package installer for Python.
201
-
1. Verify Python is installed correctly by running `py` in a Command Prompt.
202
-
1. From an elevated PowerShell console, run `pip install azure-cli` to install the Azure CLI from PyPI.
203
-
204
-
After you complete these steps, you can get started using the Azure Arc appliance CLI extension in a new PowerShell console.
196
+
This error occurs when you run the Azure CLI commands in a 32-bit context, which is the default behavior. The vSphere SDK only supports running in a 64-bit context. The specific error returned from the vSphere SDK is `Unable to import ova of size 6GB using govc`. To resolve the error, install and use Azure CLI 64-bit.
205
197
206
198
### Error during host configuration
207
199
@@ -218,122 +210,164 @@ When deploying the resource bridge on VMware vCenter, you specify the folder in
218
210
219
211
### Insufficient permissions
220
212
221
-
When deploying the resource bridge on VMware Vcenter, you may get an error saying that you have insufficient permission. To resolve this issue, make sure that your user account has all of the following privileges in VMware vCenter and then try again.
When deploying the resource bridge on VMware vCenter, you may get an error saying that you have insufficient permission. To resolve this issue, make sure that the user account being used to deploy the resource bridge has all of the following privileges in VMware vCenter and then try again.
214
+
215
+
216
+
**Datastore**
217
+
218
+
- Allocate space
219
+
220
+
- Browse datastore
221
+
222
+
- Low level file operations
223
+
224
+
**Folder**
225
+
226
+
- Create folder
227
+
228
+
**vSphere Tagging**
229
+
230
+
- Assign or Unassign vSphere Tag
231
+
232
+
**Network**
233
+
234
+
- Assign network
235
+
236
+
**Resource**
237
+
238
+
- Assign virtual machine to resource pool
239
+
240
+
- Migrate powered off virtual machine
241
+
242
+
- Migrate powered on virtual machine
243
+
244
+
**Sessions**
245
+
246
+
- Validate session
247
+
248
+
**vApp**
249
+
250
+
- Assign resource pool
251
+
252
+
- Import
253
+
254
+
**Virtual machine**
255
+
256
+
- Change Configuration
257
+
258
+
- Acquire disk lease
259
+
260
+
- Add existing disk
261
+
262
+
- Add new disk
263
+
264
+
- Add or remove device
265
+
266
+
- Advanced configuration
267
+
268
+
- Change CPU count
269
+
270
+
- Change Memory
271
+
272
+
- Change Settings
273
+
274
+
- Change resource
275
+
276
+
- Configure managedBy
277
+
278
+
- Display connection settings
279
+
280
+
- Extend virtual disk
281
+
282
+
- Modify device settings
283
+
284
+
- Query Fault Tolerance compatibility
285
+
286
+
- Query unowned files
287
+
288
+
- Reload from path
289
+
290
+
- Remove disk
291
+
292
+
- Rename
293
+
294
+
- Reset guest information
295
+
296
+
- Set annotation
297
+
298
+
- Toggle disk change tracking
299
+
300
+
- Toggle fork parent
301
+
302
+
- Upgrade virtual machine compatibility
303
+
304
+
- Edit Inventory
305
+
306
+
- Create from existing
307
+
308
+
- Create new
309
+
310
+
- Register
311
+
312
+
- Remove
313
+
314
+
- Unregister
315
+
316
+
- Guest operations
317
+
318
+
- Guest operation alias modification
319
+
320
+
- Guest operation modifications
321
+
322
+
- Guest operation program execution
323
+
324
+
- Guest operation queries
325
+
326
+
- Interaction
327
+
328
+
- Connect devices
329
+
330
+
- Console interaction
331
+
332
+
- Guest operating system management by VIX API
333
+
334
+
- Install VMware Tools
335
+
336
+
- Power off
337
+
338
+
- Power on
339
+
340
+
- Reset
341
+
342
+
- Suspend
343
+
344
+
- Provisioning
345
+
346
+
- Allow disk access
347
+
348
+
- Allow file access
349
+
350
+
- Allow read-only disk access
351
+
352
+
- Allow virtual machine download
353
+
354
+
- Allow virtual machine files upload
355
+
356
+
- Clone virtual machine
357
+
358
+
- Deploy template
359
+
360
+
- Mark as template
361
+
362
+
- Mark as virtual machine
363
+
364
+
- Snapshot management
365
+
366
+
- Create snapshot
367
+
368
+
- Remove snapshot
369
+
370
+
- Revert to snapshot
337
371
338
372
## Next steps
339
373
@@ -347,3 +381,4 @@ If you don't see your problem here or you can't resolve your issue, try one of t
347
381
348
382
-[Open an Azure support request](../../azure-portal/supportability/how-to-create-azure-support-request.md).
0 commit comments