Changing name in devspace.yaml after devspace dev causing container to fail

[sreepathy-tl]

What happened?
I followed https://www.devspace.sh/docs/getting-started/initialize-project Chaning name in the devspace.yaml and exiting and re-logging to devspace dev terminal crashes the container.

Container logs is empty. Apache error logs too do not have any errors.

What did you expect to happen instead?
Apache service should not have failed.

How can we reproduce the bug? (as minimally and precisely as possible)

• Follow steps for quick start php: https://www.devspace.sh/docs/getting-started/initialize-project
• After devspace dev prompt is ready and browser opens, change name in devspace.yaml to devspace-quickstart-php-v3
• Type exit to exit from devpsace dev terminal
• Run devspace dev again, it fails to restart apache service.
• It will reach the devspace dev prompt again, but browser page will not load since apache is down.
• After multiple attempts, devspace dev might start apache again

My devspace.yaml:

version: v2beta1
name: devspace-quickstart-php-v3

# This is a list of `pipelines` that DevSpace can execute (you can define your own)
pipelines:
  # This is the pipeline for the main command: `devspace dev` (or `devspace run-pipeline dev`)
  dev:
    run: |-
      run_dependencies --all       # 1. Deploy any projects this project needs (see "dependencies")
      create_deployments --all     # 2. Deploy Helm charts and manifests specfied as "deployments"
      start_dev app                # 3. Start dev mode "app" (see "dev" section)
  # You can run this pipeline via `devspace deploy` (or `devspace run-pipeline deploy`)
  deploy:
    run: |-
      run_dependencies --all                            # 1. Deploy any projects this project needs (see "dependencies")
      build_images --all -t $(git describe --always)    # 2. Build, tag (git commit hash) and push all images (see "images")
      create_deployments --all                          # 3. Deploy Helm charts and manifests specfied as "deployments"

# This is a list of `images` that DevSpace can build for this project
# We recommend to skip image building during development (devspace dev) as much as possible
images:
  app:
    image: my-image-registry.tld/username/app
    dockerfile: ./Dockerfile

# This is a list of `deployments` that DevSpace can create for this project
deployments:
  app:
    # This deployment uses `helm` but you can also define `kubectl` deployments or kustomizations
    helm:
      # We are deploying this project with the Helm chart you provided
      chart:
        name: component-chart
        repo: https://charts.devspace.sh
      # Under `values` we can define the values for this Helm chart used during `helm install/upgrade`
      # You may also use `valuesFiles` to load values from files, e.g. valuesFiles: ["values.yaml"]
      values:
        containers:
          - image: my-image-registry.tld/username/app
        service:
          ports:
            - port: 80

# This is a list of `dev` containers that are based on the containers created by your deployments
dev:
  app:
    # Search for the container that runs this image
    imageSelector: my-image-registry.tld/username/app
    # Replace the container image with this dev-optimized image (allows to skip image building during development)
    devImage: ghcr.io/loft-sh/devspace-containers/php:8-apache
    # Sync files between the local filesystem and the development container
    sync:
      - path: ./
        uploadExcludeFile: .dockerignore
    # Open a terminal and use the following command to start it
    terminal:
      command: ./devspace_start.sh
    # Inject a lightweight SSH server into the container (so your IDE can connect to the remote dev env)
    ssh:
      enabled: true
    # Make the following commands from my local machine available inside the dev container
    proxyCommands:
      - command: devspace
      - command: kubectl
      - command: helm
      - command: git
    # Forward the following ports to be able access your application via localhost
    ports:
      - port: 7000:80
    # Open the following URLs once they return an HTTP status code other than 502 or 503
    open:
      - url: http://localhost:7000

# Use the `commands` section to define repeatable dev workflows for this project 
commands:
  migrate-db:
    command: |-
      echo 'This is a cross-platform, shared command that can be used to codify any kind of dev task.'
      echo 'Anyone using this project can invoke it via "devspace run migrate-db"'

# Define dependencies to other projects with a devspace.yaml
# dependencies:
#   api:
#     git: https://...  # Git-based dependencies
#     tag: v1.0.0
#   ui:
#     path: ./ui        # Path-based dependencies (for monorepos)

...

Local Environment:

• DevSpace Version: 6.1.1
• Operating System: mac
• ARCH of the OS: AMD64 Kubernetes Cluster:
• Cloud Provider: other - used rancher desktop
• Kubernetes Version:

  clientVersion:
  buildDate: "2022-08-17T18:54:23Z"
  compiler: gc
  gitCommit: 95ee5ab382d64cfe6c28967f36b53970b8374491
  gitTreeState: clean
  gitVersion: v1.24.4
  goVersion: go1.18.5
  major: "1"
  minor: "24"
  platform: darwin/amd64
  kustomizeVersion: v4.5.4
  serverVersion:
  buildDate: "2022-08-25T03:45:26Z"
  compiler: gc
  gitCommit: c3f830e9b9ed8a4d9d0e2aa663b4591b923a296e
  gitTreeState: clean
  gitVersion: v1.24.4+k3s1
  goVersion: go1.18.1
  major: "1"
  minor: "24"
  platform: linux/amd64

  Anything else we need to know?
  Stability issue

/kind bug

[bagulm123]

Hi @sreepathy-tl,

Thanks for reporting the issue.

The current behaviour is happening due to below error,

Restarting Apache httpd web server: apache2 failed!

I couldn't really relate the change in name and the issue behaviour with each others. The workaround for that is to restart the apache2 manually using below command.

apache2ctl restart

or

/etc/init.d/apache2 restart

I am further looking into it to get the root cause of the error.

[sreepathy-tl]

Thanks @mahendrabagul. Issue sorted out after following your instructions on slack.