DO Provider returns 404 on salt-cloud -d, but destroys successfully

[zlanich]

Relevant Cloud: https://github.com/saltstack/salt/blob/bdafa60e6a9cd13adf0ada803ed8fde8a81fae3e/salt/cloud/clouds/digital_ocean.py

Setup

do.conf

do:
  driver: digital_ocean
  personal_access_token: <api_key>
  ssh_key_file: /etc/salt/pki/cloud/do.pem
  ssh_key_names: some,keys
  script: bootstrap-salt
  script_args: -P git v2016.3.1

Profiles

base:
  provider: do
  image: ubuntu-16-04-x64
  size: 512mb
  location: nyc1
  private_networking: True
  ipv6: True

web:
  extends: base
  minion:
    grains:
      role: webserver
      env: prod

Map

web:
  - web1

Steps to Reproduce Issue

salt-cloud -l debug -d 'web1'

Logs

Master Log

2016-07-27 02:01:25,827 [salt.utils.verify][WARNING ][17703] Insecure logging configuration detected! Sensitive data may be logged.
2016-07-27 02:01:25,828 [salt.cloud.cli   ][INFO    ][17703] salt-cloud starting
2016-07-27 02:01:25,925 [salt.utils.lazy  ][DEBUG   ][17703] Could not LazyLoad parallels.avail_sizes
2016-07-27 02:01:25,926 [salt.utils.lazy  ][DEBUG   ][17703] LazyLoaded parallels.avail_locations
2016-07-27 02:01:25,926 [salt.utils.lazy  ][DEBUG   ][17703] LazyLoaded proxmox.avail_sizes
2016-07-27 02:01:25,927 [salt.utils.lazy  ][DEBUG   ][17703] Could not LazyLoad saltify.destroy
2016-07-27 02:01:25,928 [salt.utils.lazy  ][DEBUG   ][17703] Could not LazyLoad saltify.avail_sizes
2016-07-27 02:01:25,929 [salt.utils.lazy  ][DEBUG   ][17703] Could not LazyLoad saltify.avail_images
2016-07-27 02:01:25,929 [salt.utils.lazy  ][DEBUG   ][17703] Could not LazyLoad saltify.avail_locations
2016-07-27 02:01:25,930 [salt.utils.lazy  ][DEBUG   ][17703] LazyLoaded rackspace.reboot
2016-07-27 02:01:25,930 [salt.utils.lazy  ][DEBUG   ][17703] LazyLoaded openstack.list_locations
2016-07-27 02:01:25,931 [salt.utils.lazy  ][DEBUG   ][17703] LazyLoaded rackspace.list_locations
2016-07-27 02:01:25,931 [salt.utils.lazy  ][DEBUG   ][17703] Could not LazyLoad digital_ocean.optimize_providers
2016-07-27 02:01:25,932 [salt.cloud       ][DEBUG   ][17703] The 'digital_ocean' cloud driver is unable to be optimized.
2016-07-27 02:01:26,028 [salt.utils.lazy  ][DEBUG   ][17710] Could not LazyLoad parallels.avail_sizes
2016-07-27 02:01:26,030 [salt.utils.lazy  ][DEBUG   ][17710] LazyLoaded parallels.avail_locations
2016-07-27 02:01:26,030 [salt.utils.lazy  ][DEBUG   ][17710] LazyLoaded proxmox.avail_sizes
2016-07-27 02:01:26,031 [salt.utils.lazy  ][DEBUG   ][17710] Could not LazyLoad saltify.destroy
2016-07-27 02:01:26,031 [salt.utils.lazy  ][DEBUG   ][17710] Could not LazyLoad saltify.avail_sizes
2016-07-27 02:01:26,032 [salt.utils.lazy  ][DEBUG   ][17710] Could not LazyLoad saltify.avail_images
2016-07-27 02:01:26,033 [salt.utils.lazy  ][DEBUG   ][17710] Could not LazyLoad saltify.avail_locations
2016-07-27 02:01:26,033 [salt.utils.lazy  ][DEBUG   ][17710] LazyLoaded rackspace.reboot
2016-07-27 02:01:26,034 [salt.utils.lazy  ][DEBUG   ][17710] LazyLoaded openstack.list_locations
2016-07-27 02:01:26,034 [salt.utils.lazy  ][DEBUG   ][17710] LazyLoaded rackspace.list_locations
2016-07-27 02:01:26,175 [salt.loaded.int.clouds.digital_ocean][DEBUG   ][17710] https://api.digitalocean.com/v2/droplets/?page=1&per_page=200
2016-07-27 02:02:53,313 [salt.cloud       ][INFO    ][17703] Destroying in non-parallel mode.
2016-07-27 02:02:53,318 [salt.utils.event ][DEBUG   ][17703] MasterEvent PUB socket URI: /var/run/salt/master/master_event_pub.ipc
2016-07-27 02:02:53,319 [salt.utils.event ][DEBUG   ][17703] MasterEvent PULL socket URI: /var/run/salt/master/master_event_pull.ipc
2016-07-27 02:02:53,321 [salt.transport.ipc][DEBUG   ][17703] Initializing new IPCClient for path: /var/run/salt/master/master_event_pull.ipc
2016-07-27 02:02:53,327 [salt.utils.event ][DEBUG   ][17703] Sending event - data = {'_stamp': '2016-07-27T06:02:53.326761', 'name': u'web1', 'event': 'destroying instance'}
2016-07-27 02:02:53,487 [salt.loaded.int.clouds.digital_ocean][DEBUG   ][17703] https://api.digitalocean.com/v2/droplets/?page=1&per_page=200
2016-07-27 02:02:53,644 [salt.loaded.int.clouds.digital_ocean][DEBUG   ][17703] https://api.digitalocean.com/v2/droplets/20678675/
2016-07-27 02:02:53,645 [salt.loaded.int.clouds.digital_ocean][DEBUG   ][17703] Deleting DNS records for web1.

Console Error

Error: There was an error destroying machines: An error occurred while querying DigitalOcean. HTTP Code: 404  Error: '{"id":"not_found","message":"The resource you were accessing could not be found."}'

Versions Report (same for Master & Minion)

Salt Version:
           Salt: 2016.3.1

Dependency Versions:
           cffi: Not Installed
       cherrypy: 3.5.0
       dateutil: 2.4.2
          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: Not Installed
       pycrypto: 2.6.1
         pygit2: Not Installed
         Python: 2.7.12 (default, Jul  1 2016, 15:12:24)
   python-gnupg: Not Installed
         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
        machine: x86_64
        release: 4.4.0-31-generic
         system: Linux
        version: Ubuntu 16.04 xenial

[Ch3LL]

@zlanich this is a duplicate of #33452 which has been fixed by #34605 . This fix should be coming out with 2016.3.2, which is currently in the QA phase.

[zlanich]

Thank you! I looked around & must have missed that other Issue.

Best Regards,

Zach Lanich
Business Owner, Entrepreneur, Creative
Owner/Lead Developer
weCreate LLC
www.WeCreate.com

On Jul 27, 2016, at 3:36 PM, Megan Wilhite notifications@github.com wrote:

@zlanich this is a duplicate of #33452 which has been fixed by #34605 . This fix should be coming out with 2016.3.2, which is currently in the QA phase.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.