SaltStack Support

SaltStack Enterprise 6.1.0 - Download & Installation Instructions

SaltStack Enterprise 6.1.0 was released on November 19th, 2019.

For Downloads and Installation instructions please go to the following link and use your SaltStack Support Portal credentials.

Evaluation Period is 14 Days

SaltStack Enterprise (SSE) has a native licensing mechanism.

An installation of SSE without a License Key-File (LKF) is an Evaluation-Installation. The evaluation period of SSE without a LKF is 14 days.

At day 14, an installation of SSE that does not have a LKF applied to it will stop running.

Upon the application of a LKF to an Evaluation-Installation of SSE, the configured Evaluation-Installation will resume operation as a Licensed instance of SSE for the period defined in the LKF.

Use of the SecOps module requires a new license. If you would like a trial of the SaltStack for SecOps capabilities please reach out to your SaltStack sales person or SaltStack Support.

 

Key Known Issues

  1. If the Postgres DB is not set to use UTF-8, sorting will not be consistent across the application.
  2. Salt-run jobs do not work with the route_cmd method.
  3. Non-scheduled jobs will capture the job execution time in the master time zone. Scheduled jobs will capture job execution time in UTC.  To sync these times, the master time zone must be set to UTC or there will be a discrepancy between jobs run at the same time on a schedule vs. from the command line.
  4. Scheduled jobs display in the web console only if scheduled within the next 12 weeks.
  5. Job return numbers may differ from target numbers based on current key state and grain data.
  6. SaltStack Enterprise console is supported on Chrome version 72 and later, and FireFox version 63 and later.
  7. SaltStack SecOps requires Salt version 2018.3.3 or later for Linux or Unix minions, and 2019.2.0 or higher for Windows minions.
  8. It is recommended SaltStack SecOps assessments and remediations are run weekly or biweekly for target groups greater than 1,000 minions. If run more frequently, the results table will quickly consume all available disk space.
  9. If the master plugin is configured incorrectly or raas is down, the Salt Master might appear to not be receiving commands. However, in this case the master is receiving commands but responding slowly.
  10. Compound targeting with grains does not work if the grain filter value contains spaces. To use compound targeting with grains, do one of the following:
    • Use the G@ glob matcher but replace spaces with wildcard characters (*) For example, change G@osfinger:CentOS Linux-7 to G@osfinger:CentOS*Linux-7.
    • Use the P@ Perl-compatible regular expression (PCRE) matcher but replace spaces with \s to match whitespace. For example, change P@osfinger:CentOS Linux-7 to P@osfinger:CentOS\sLinux-7.
  11. In some cases, SecOps Compliance assessments results might show a negative count of minions returned.
  12. In the Web Console, SecOps Vulnerability does not show any minions included in a newly-created policy until you have run the first assessment.

Important Documents

Related articles