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 2015.8.8 not installing salt minions on new nodes #32183

Closed
llamallama opened this issue Mar 28, 2016 · 10 comments
Closed

Salt Cloud 2015.8.8 not installing salt minions on new nodes #32183

llamallama opened this issue Mar 28, 2016 · 10 comments
Assignees
Labels
Bug broken, incorrect, or confusing behavior Confirmed Salt engineer has confirmed bug/feature - often including a MCVE fixed-pls-verify fix is linked, bug author to confirm fix P2 Priority 2 RIoT Relates to integration with cloud providers, hypervisors, API-based services, etc. Salt-Cloud severity-high 2nd top severity, seen by most users, causes major problems
Milestone

Comments

@llamallama
Copy link

Description of Issue/Question

After upgrading from 2015.8.7 to 2015.8.8, salt-cloud no longer deployments the minions to newly provisioned nodes. My test case is with Linode, but I've heard reports on IRC of the same issue with Digital Ocean on the same salt version.

Setup

Provider:

linode-config:
  apikey: xxxx
  ssh_key_file: /etc/salt/cloud.keys.d/salt_linode_rsa
  password: xxxx
  driver: linode
  minion:
    master: salt
  grains:
    environment: internal
    location: linode
    roles:
      - zabbix-agent
  startup_states: highstate

Profile

linode_1024_GA:
  provider: linode-config
  password: xxxx
  size: Linode 1024
  image: CentOS 7
  location: Atlanta, GA, USA
  private_ip: false
linode_2048_GA:
  provider: linode-config
  password: xxxx
  size: Linode 2048
  image: CentOS 7
  location: Atlanta, GA, USA
  private_ip: false
linode_1024_NJ:
  provider: linode-config
  password: xxxx
  size: Linode 1024
  image: CentOS 7
  location: Newark, NJ, USA
  private_ip: false
linode_2048_NJ:
  provider: linode-config
  password: xxxx
  size: Linode 2048
  image: CentOS 7
  location: Newark, NJ, USA
  private_ip: false
linode_1024_TX:
  provider: linode-config
  password: xxxx
  size: Linode 1024
  image: CentOS 7
  location: Dallas, TX, USA
  private_ip: false
linode_2048_TX:
  provider: linode-config
  password: xxxx
  size: Linode 2048
  image: CentOS 7
  location: Dallas, TX, USA
  private_ip: false

Steps to Reproduce Issue

salt-cloud -p linode_1024_GA cloudtest --keep-tmp

It creates the Linode instance and returns this when completed.

cloudtest:
    ----------
    deployed:
        True
    id:
        1751789
    image:
        CentOS 7
    name:
        cloudtest
    private_ips:
    public_ips:
        - XX.XX.XX.XX
    size:
        Linode 1024
    state:
        Running

I SSHed into the node and salt that salt was not installed and the deployment script never ran. With the --keep-tmp flag, I noticed that the pem files did get placed but not deploy.sh.

Versions Report

Salt Version:
           Salt: 2015.8.8

Dependency Versions:
         Jinja2: 2.7.2
       M2Crypto: 0.21.1
           Mako: Not Installed
         PyYAML: 3.11
          PyZMQ: 14.7.0
         Python: 2.7.5 (default, Nov 20 2015, 02:00:19)
           RAET: Not Installed
        Tornado: 4.2.1
            ZMQ: 4.0.5
           cffi: Not Installed
       cherrypy: Not Installed
       dateutil: Not Installed
          gitdb: Not Installed
      gitpython: Not Installed
          ioflo: Not Installed
        libgit2: Not Installed
        libnacl: Not Installed
   msgpack-pure: Not Installed
 msgpack-python: 0.4.6
   mysql-python: Not Installed
      pycparser: Not Installed
       pycrypto: 2.6.1
         pygit2: Not Installed
   python-gnupg: Not Installed
          smmap: Not Installed
        timelib: Not Installed

System Versions:
           dist: centos 7.2.1511 Core
        machine: x86_64
        release: 4.4.0-x86_64-linode63
         system: CentOS Linux 7.2.1511 Core
@llamallama
Copy link
Author

I got this to work by running
salt-cloud --update-bootstrap

I guess the deploy script somehow got removed during the update.

@iggy
Copy link
Contributor

iggy commented Mar 28, 2016

#28466
#26699

@llamallama
Copy link
Author

Reopening since this was not supposed to happen.

@llamallama llamallama reopened this Mar 28, 2016
@jfindlay jfindlay added Bug broken, incorrect, or confusing behavior Packaging Related to packaging of Salt, not Salt's support for package management. Salt-Cloud severity-high 2nd top severity, seen by most users, causes major problems P2 Priority 2 Platform Relates to OS, containers, platform-based utilities like FS, system based apps labels Mar 28, 2016
@jfindlay jfindlay added this to the Approved milestone Mar 28, 2016
@jfindlay
Copy link
Contributor

@llamallama, @iggy, thanks for reporting.

@rallytime
Copy link
Contributor

#31172 and #32105 might address this.

@frogunder
Copy link
Contributor

I have not been able to replicate this.
I updated from 2015.8.7 to 2015.8.8.
When I created a new cloud, the bootstrap script in /etc/salt/cloud.deploy.d ran and salt got installed on the new cloud.

Provider:

linode:
  apikey: xxxx
  password: xxxx
  location: Fremont, CA, USA
  provider: linode

Profile:

linode_cent7:
  provider: linode
  size: Linode 2048
  image: CentOS 7

@iggy
Copy link
Contributor

iggy commented Mar 30, 2016

The issue is if you don't have the script in /etc/salt/cloud.deploy.d. It's supposed to fetch from elsewhere and that seems to fail under certain circumstances.

@frogunder
Copy link
Contributor

Tested again without a script in /etc/salt/cloud.deploy.d.
I can confirm this is an error, like it is described above.

In 2015.8.7

[INFO    ] Rendering deploy script: /usr/lib/python2.7/site-packages/salt/cloud/deploy/bootstrap-salt.sh

Salt gets installed.


In 2015.8.8

It do not render the deploy script
Salt do not get installed.

@jfindlay jfindlay added the Confirmed Salt engineer has confirmed bug/feature - often including a MCVE label Mar 30, 2016
@meggiebot meggiebot added fixed-pls-verify fix is linked, bug author to confirm fix and removed fixed-pls-verify fix is linked, bug author to confirm fix labels Mar 30, 2016
@meggiebot
Copy link

#32105 was merged on the head of the branch, but our internal testing is still showing issues. We are investigating further.

@meggiebot meggiebot modified the milestones: B -1, Approved Mar 31, 2016
@meggiebot meggiebot added TEAM RIoT RIoT Relates to integration with cloud providers, hypervisors, API-based services, etc. and removed Packaging Related to packaging of Salt, not Salt's support for package management. Platform Relates to OS, containers, platform-based utilities like FS, system based apps labels Mar 31, 2016
@Ch3LL
Copy link
Contributor

Ch3LL commented Mar 31, 2016

I have verified that this is fixed at the head of 2015.8. #32105 fixes this issue.

@Ch3LL Ch3LL added the fixed-pls-verify fix is linked, bug author to confirm fix label Mar 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior Confirmed Salt engineer has confirmed bug/feature - often including a MCVE fixed-pls-verify fix is linked, bug author to confirm fix P2 Priority 2 RIoT Relates to integration with cloud providers, hypervisors, API-based services, etc. Salt-Cloud severity-high 2nd top severity, seen by most users, causes major problems
Projects
None yet
Development

No branches or pull requests

9 participants