splunk / splunk/docker-splunk

Upgrade 7.2.6 -> 7.3.0 fails

Open
#209 16 comments 0 reactions 3 assignees View on GitHub

@jmeixensperger is already working on this.

Since Jun 28, 2019.

Dominant language
Python
Stars
549
Forks
277
Avg merge
3d 9h
Merged PRs (30d)
2

Description

Expect
I should be able to upgrade from 7.2.6 to 7.3.0 tags

Observed
Upgrades fail with permission denied when performing stat on {{ splunk_home}}/etc/auth/splunk.secret

Repro Steps

  1. docker-compose up -d
  2. docker-compose logs splunkenterprise --follow
  3. Wait for splunkweb to be available
  4. change image tag in compose to ":7.3.0" or ":edge"
  5. add env var SPLUNK_UPGRADE="true"
  6. docker-compose up -d
  7. docker-compose logs splunkenterprise

Docker Compose File

# docker run splunk/enterprise:7.0.3
# Options on how to review the EULA and accept it: 
# 1. docker run -it splunk/enterprisetrial:7.0.3
# 2. Add the following environment variable: SPLUNK_START_ARGS=--accept-license
# e.g., docker run -e "SPLUNK_START_ARGS=--accept-license" splunk/enterprisetrial 

# Support for Docker Compose v3, https://docs.docker.com/compose/overview/
version: '3'
volumes:
  opt-splunk-etc:
  opt-splunk-var:
services:
  splunkenterprise:
    #build: .
    hostname: splunkenterprise
    image: splunk/splunk:7.2.6
    image: splunk/splunk:7.3.0
    #image: splunk/splunk:edge
    environment:
      SPLUNK_START_ARGS: --accept-license --answer-yes
      DEBUG: "true"
      ANSIBLE_EXTRA_FLAGS: "-vvvv"
      SPLUNK_PASSWORD: 'icanhazpasswd'
      # SPLUNK_UPGRADE: "true"
      SPLUNK_ENABLE_LISTEN: 9997
      SPLUNK_ADD: tcp 1514
    volumes:
      - opt-splunk-etc:/opt/splunk/etc
      - opt-splunk-var:/opt/splunk/var
    ports:
      - "8000:8000"
      - "9997:9997"
      - "8088:8088"
      - "1514:1514"

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.