Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Salt Cloud|AzureARM Compute CloudError has occurred: 'adminPassword' is missing (null). #54767

Closed
cskowronnek opened this issue Sep 26, 2019 · 6 comments
Labels
info-needed waiting for more info Pending-Discussion The issue or pull request needs more discussion before it can be closed or merged stale v2019.2.1 unsupported version
Milestone

Comments

@cskowronnek
Copy link

Description of Issue

salt-cloud -p linux_server test-server
[DEBUG   ] https://management.azure.com:443 "PUT /subscriptions/xxxxx/resourceGroups/ELK/providers/Microsoft.Compute/virtualMachines/test-server?api-version=2019-03-01 HTTP/1.1" 400 160
[DEBUG   ] Required parameter 'adminPassword' is missing (null).
[ERROR   ] An AzureARM Compute CloudError has occurred: Required parameter 'adminPassword' is missing (null).
[ERROR   ] Error creating VM test-server! ({})
Error: There was a profile error: Error creating VM test-server! ({})

Setup

Steps to Reproduce Issue

(Include debug logs if possible and relevant.)

Versions Report

Salt Version:
           Salt: 2019.2.1

Dependency Versions:
           cffi: 1.12.3
       cherrypy: Not Installed
       dateutil: 2.8.0
      docker-py: Not Installed
          gitdb: 0.6.4
      gitpython: 1.0.1
          ioflo: Not Installed
         Jinja2: 2.8
        libgit2: Not Installed
        libnacl: Not Installed
       M2Crypto: Not Installed
           Mako: 1.0.3
   msgpack-pure: Not Installed
 msgpack-python: 0.4.6
   mysql-python: Not Installed
      pycparser: 2.19
       pycrypto: 2.6.1
   pycryptodome: Not Installed
         pygit2: Not Installed
         Python: 2.7.12 (default, Aug 22 2019, 16:36:40)
   python-gnupg: 0.3.8
         PyYAML: 3.11
          PyZMQ: 15.2.0
           RAET: Not Installed
          smmap: 0.9.0
        timelib: Not Installed
        Tornado: 4.2.1
            ZMQ: 4.1.4

System Versions:
           dist: Ubuntu 16.04 xenial
         locale: UTF-8
        machine: x86_64
        release: 4.4.0-151-generic
         system: Linux
        version: Ubuntu 16.04 xenial

azure==2.0.0
azure-batch==3.0.0
azure-common==1.1.23
azure-datalake-store==0.0.45
azure-graphrbac==0.30.0
azure-keyvault==0.3.7
azure-mgmt==1.0.0
azure-mgmt-authorization==0.30.0
azure-mgmt-batch==4.0.0
azure-mgmt-cdn==0.30.3
azure-mgmt-cognitiveservices==1.0.0
azure-mgmt-compute==8.0.0
azure-mgmt-containerregistry==0.2.1
azure-mgmt-datalake-analytics==0.1.6
azure-mgmt-datalake-nspkg==3.0.1
azure-mgmt-datalake-store==0.1.6
azure-mgmt-devtestlabs==2.0.0
azure-mgmt-dns==1.0.1
azure-mgmt-documentdb==0.1.3
azure-mgmt-iothub==0.2.2
azure-mgmt-keyvault==0.31.0
azure-mgmt-logic==2.1.0
azure-mgmt-monitor==0.2.1
azure-mgmt-network==1.0.0
azure-mgmt-nspkg==3.0.2
azure-mgmt-rdbms==0.1.0
azure-mgmt-redis==4.1.1
azure-mgmt-resource==1.1.0
azure-mgmt-scheduler==1.1.3
azure-mgmt-sql==0.5.3
azure-mgmt-storage==1.0.0
azure-mgmt-trafficmanager==0.30.0
azure-mgmt-web==0.32.0
azure-nspkg==3.0.2
azure-servicebus==0.21.1
azure-servicefabric==5.6.130
azure-servicemanagement-legacy==0.20.6
azure-storage==0.34.3
msrest==0.6.10
msrestazure==0.6.2
@nicholasmhughes
Copy link
Collaborator

It's probably one of two things.

  1. The provider/profile you're using isn't providing the "right" combination of parameters to the API in order to have it properly evaluate that you're trying to stand up a Linux server w/ an SSH key (which is what I'm guessing you're trying to do) instead of of username/password. Please provide a sanitized version of your provider/profile stanzas. If this worked before the upgrade to 2019.2.1, then this is unlikely.
  2. The Azure Python SDK version on your machine drifted to a point that it was incompatible with the cloud driver. From your pip freeze output, it looks like you're running some odd versions. I've included my output below (I'm not running the latest), and you have an older base SDK version but a much newer compute SDK version. You might try running the versions below and see if anything changes for the better.
azure==4.0.0
azure-applicationinsights==0.1.0
azure-batch==4.1.3
azure-common==1.1.23
azure-cosmosdb-nspkg==2.0.2
azure-cosmosdb-table==1.0.5
azure-datalake-store==0.0.46
azure-eventgrid==1.3.0
azure-graphrbac==0.40.0
azure-keyvault==1.1.0
azure-loganalytics==0.1.0
azure-mgmt==4.0.0
azure-mgmt-advisor==1.0.1
azure-mgmt-applicationinsights==0.1.1
azure-mgmt-authorization==0.50.0
azure-mgmt-batch==5.0.1
azure-mgmt-batchai==2.0.0
azure-mgmt-billing==0.2.0
azure-mgmt-cdn==3.1.0
azure-mgmt-cognitiveservices==3.0.0
azure-mgmt-commerce==1.0.1
azure-mgmt-compute==4.6.2
azure-mgmt-consumption==2.0.0
azure-mgmt-containerinstance==1.5.0
azure-mgmt-containerregistry==2.8.0
azure-mgmt-containerservice==4.4.0
azure-mgmt-cosmosdb==0.4.1
azure-mgmt-datafactory==0.6.0
azure-mgmt-datalake-analytics==0.6.0
azure-mgmt-datalake-nspkg==3.0.1
azure-mgmt-datalake-store==0.5.0
azure-mgmt-datamigration==1.0.0
azure-mgmt-devspaces==0.1.0
azure-mgmt-devtestlabs==2.2.0
azure-mgmt-dns==2.1.0
azure-mgmt-eventgrid==1.0.0
azure-mgmt-eventhub==2.6.0
azure-mgmt-hanaonazure==0.1.1
azure-mgmt-iotcentral==0.1.0
azure-mgmt-iothub==0.5.0
azure-mgmt-iothubprovisioningservices==0.2.0
azure-mgmt-keyvault==1.1.0
azure-mgmt-loganalytics==0.2.0
azure-mgmt-logic==3.0.0
azure-mgmt-machinelearningcompute==0.4.1
azure-mgmt-managementgroups==0.1.0
azure-mgmt-managementpartner==0.1.1
azure-mgmt-maps==0.1.0
azure-mgmt-marketplaceordering==0.1.0
azure-mgmt-media==1.0.0
azure-mgmt-monitor==0.5.2
azure-mgmt-msi==0.2.0
azure-mgmt-network==4.0.0
azure-mgmt-notificationhubs==2.1.0
azure-mgmt-nspkg==3.0.2
azure-mgmt-policyinsights==0.1.0
azure-mgmt-powerbiembedded==2.0.0
azure-mgmt-rdbms==1.9.0
azure-mgmt-recoveryservices==0.3.0
azure-mgmt-recoveryservicesbackup==0.3.0
azure-mgmt-redis==5.0.0
azure-mgmt-relay==0.1.0
azure-mgmt-reservations==0.2.1
azure-mgmt-resource==2.2.0
azure-mgmt-scheduler==2.0.0
azure-mgmt-search==2.1.0
azure-mgmt-servicebus==0.5.3
azure-mgmt-servicefabric==0.2.0
azure-mgmt-signalr==0.1.1
azure-mgmt-sql==0.9.1
azure-mgmt-storage==2.0.0
azure-mgmt-subscription==0.2.0
azure-mgmt-trafficmanager==0.50.0
azure-mgmt-web==0.35.0
azure-nspkg==3.0.2
azure-servicebus==0.21.1
azure-servicefabric==6.3.0.0
azure-servicemanagement-legacy==0.20.6
azure-storage==0.36.0
azure-storage-blob==1.5.0
azure-storage-common==1.4.2
azure-storage-file==1.4.0
azure-storage-nspkg==3.1.0
azure-storage-queue==1.4.0
msrest==0.6.9
msrestazure==0.6.1

@cmcmarrow cmcmarrow added the Pending-Discussion The issue or pull request needs more discussion before it can be closed or merged label Sep 30, 2019
@cmcmarrow cmcmarrow added this to the Blocked milestone Sep 30, 2019
@cmcmarrow cmcmarrow added the v2019.2.1 unsupported version label Sep 30, 2019
@Akm0d Akm0d added the info-needed waiting for more info label Sep 30, 2019
@cskowronnek
Copy link
Author

@nicholasmhughes
I've updated my python packages to the same versions you use. You're right I've set ssh_password and I'm using Linux. Stil no success.

Here is my profile:

azure-es-node-test:
  provider: azurearm
  image: Canonical|UbuntuServer|18.04-LTS|latest
  size: Standard_B4ms
  location: westeurope
  resource_group: ELK
  network_resource_group: RG-INFRA
  network: VNET-1
  subnet: VNET-1-Subnet-1
  ssh_username: username
  ssh_keyfile: /etc/salt/cloud.profiles.d/cs.key
  ssh_publickeyfile: /etc/salt/cloud.profiles.d/cs.pub
  ssh_password: SUPERSECRET
  admin_password: SUPERSECRET
  public_ip: False
  bootstrap_interface: private
  volumes:
    - disk_size_gb: 512
      caching: ReadWrite
      managed_disk:
        storage_account_type: Standard_LRS

  cleanup_disks: True
  cleanup_vhds: True
  cleanup_data_disks: True
  cleanup_interfaces: True

@nicholasmhughes
Copy link
Collaborator

Try disable_password_authentication: True in your profile.

@cskowronnek
Copy link
Author

@nicholasmhughes That does the trick. Thanks. I think the documentation should be updated.

@nicholasmhughes
Copy link
Collaborator

Awesome. Glad that worked. I'll make a note to look at the docs and see if I have time to make things more clear.

@stale
Copy link

stale bot commented Jan 7, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
info-needed waiting for more info Pending-Discussion The issue or pull request needs more discussion before it can be closed or merged stale v2019.2.1 unsupported version
Projects
None yet
Development

No branches or pull requests

4 participants