chef / chef/chef-server

CINC server installation fails on Al2023

Open
#4,086 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Status: Untriaged
Dominant language
Erlang
Stars
303
Forks
211
Avg merge
1d 8h
Merged PRs (30d)
5

Description

Chef Server Version

15.10.33
15.9.27
15.10.12

Platform Details

Amazon Linux 2023

Configuration

Standalone

Scenario

We have cinc server (v 14) running on AL2 and as AL2 is reaching its EOL we are trying to upgrade to AL2023, but while running cinc-server-ctl reconfigure command post installing cinc rpm we are getting the following error with nginx installation
we have tried installing multiple different versions of cinc but getting same error with all of them, it looks like the infra-server recipes are not updated properly as per its compatiblity with AL2023, i still see recipe yum-epel in the infra server recipes which is not compatible with AL2023. Also runit service again is not compatible with AL2023.

`Recipe: infra-server::nginx
* component_runit_service[nginx] action restart
* service[nginx] action nothing (skipped due to action :nothing)
* runit_service[nginx] action restart

    ================================================================================
    Error executing action `restart` on resource 'runit_service[nginx]'
    ================================================================================

    Mixlib::ShellOut::ShellCommandFailed
    ------------------------------------
    Expected process to exit with [0], but received '1'
    ---- Begin output of /opt/cinc-project/embedded/bin/sv restart /opt/cinc-project/service/nginx ----
    STDOUT: fail: /opt/cinc-project/service/nginx: unable to change to service directory: file does not exist
    STDERR:
    ---- End output of /opt/cinc-project/embedded/bin/sv restart /opt/cinc-project/service/nginx ----
    Ran /opt/cinc-project/embedded/bin/sv restart /opt/cinc-project/service/nginx returned 1`
Steps to Reproduce

dnf install -y cinc-server.rpm
cinc-server-ctl reconfigure

Expected Result

cinc server installation successful

Actual Result

`Recipe: infra-server::nginx
* component_runit_service[nginx] action restart
* service[nginx] action nothing (skipped due to action :nothing)
* runit_service[nginx] action restart

    ================================================================================
    Error executing action `restart` on resource 'runit_service[nginx]'
    ================================================================================

    Mixlib::ShellOut::ShellCommandFailed
    ------------------------------------
    Expected process to exit with [0], but received '1'
    ---- Begin output of /opt/cinc-project/embedded/bin/sv restart /opt/cinc-project/service/nginx ----
    STDOUT: fail: /opt/cinc-project/service/nginx: unable to change to service directory: file does not exist
    STDERR:
    ---- End output of /opt/cinc-project/embedded/bin/sv restart /opt/cinc-project/service/nginx ----
    Ran /opt/cinc-project/embedded/bin/sv restart /opt/cinc-project/service/nginx returned 1`

`

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.

Research direction

Start by reproducing the failure with dnf install -y cinc-server.rpm followed by cinc-server-ctl reconfigure on Amazon Linux 2023. Read the infra-server::nginx recipe and the referenced yum-epel and runit service setup; done means the CINC server reconfiguration completes successfully and nginx can be restarted.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, nginx
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.