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

Update the version of chef-server in Automate #2652

Closed
lbakerchef opened this issue Jul 20, 2021 · 10 comments
Closed

Update the version of chef-server in Automate #2652

lbakerchef opened this issue Jul 20, 2021 · 10 comments
Assignees

Comments

@lbakerchef
Copy link
Contributor

Latest greatest is 14.6.32.

chef/automate#5371

@PrajaktaPurohit
Copy link
Contributor

#2775

@jashaik
Copy link
Contributor

jashaik commented Sep 14, 2021

14.9.23 release should resolve all the chef-server issues in Automate environment. Yet to create a PR in automate.

@vinay-satish
Copy link
Contributor

There are two PR created in the automate repository. Each PR is pointing to two different channels in the habitat builder.
Since the automate will no longer will not be using stable channel, the PR chef/automate#5726 is closed.
Automate will be using the new refresh channels for it deployment. The PR pointing to refresh channel is - chef/automate#5772

@PrajaktaPurohit
Copy link
Contributor

Blocked. Currently fails in dependency resolution for core/glibc and core/linux-headers. https://buildkite.com/chef/chef-automate-main-verify-private/builds/18338#8564bacc-6dce-4457-a01a-3de0f5282a6a/689-1048

@PrajaktaPurohit
Copy link
Contributor

To update to 14.10, the header test for x-ops-api-info header test will need to be skipped. #2815 does not include the change to make x-pos-api-info configurable in automate.

@vinay-satish
Copy link
Contributor

Also as part of this, we need to add --skip=headers while running pedant. #2815 (comment)

@vinay-satish
Copy link
Contributor

The latest chef-server has the pg13, but automate is still not updated yet. The changes for the current latest 14.10.23 are ready in the PR - chef/automate#6183

@vinay-satish
Copy link
Contributor

vinay-satish commented Nov 30, 2021

  1. Dependencies issue - The automate component dependencies were moved to stable2021-q2 from stable channel of the habitat. chef-server component dependencies were still using stable channel, because of this we had the dependency issue. - RESOLVED 12/09
  2. The automate pipeline is failing because the erchef and nginx components are CRITICAL, but working in dev environment. - IN PROGRESS
  3. Data collector issue (A2_HA)- The data_collector is enabled Automatically in the automate-cs-oc-erchef but the URL is not working so CS is sending the status as fail due to CS is not able to send the data to the defined URL in configuration. We can disable the data collector. Moving it to automate repo as this is not a chef server issue. - LB config issue in automate. RESOLVED.
  4. chef-server-ctl issue - We are not able to run chef-server-ctl commands in the dev environment. getting the following error - Could not find rake-13.0.6 in any of the sources Run bundle install' to install missing gems.. Bundle install is failing with the error bash: bundle: command not found. - RESOLVED
  5. a1 migration failures with bifrost (https://buildkite.com/chef/chef-automate-main-verify-private/builds/19634#a6317d56-b69b-4298-afa4-4059a0747150)

@jashaik
Copy link
Contributor

jashaik commented Dec 20, 2021

Status -
Upgrade migration is failing in the automate after updating the CS version.
Pipeline - https://buildkite.com/chef/chef-automate-main-verify-private/builds/19525#054129b7-9376-4041-9da3-d68d39d8ac1b

This is failing with sqitch error.
Dec 10 06:51:00 a1-migration.test hab[4747]: pg-sidecar-service.default(O): Cannot find change 4168bd129204d3c9137179a5e52173ffa07476bc (cookbook_versions_cookbook_id_index @1.0.4) in /hab/pkgs/chef/oc_erchef/14.11.1/20211124104838/schema/baseline/sqitch.plan
Dec 10 06:51:00 a1-migration.test hab[4747]: automate-pg-gateway.default(O): 127.0.0.1:36610 [10/Dec/2021:06:51:00.380] postgresql automate_postgresql/127.0.0.1 1/0/29 4488 SD 65/65/64/64/0 0/0
Dec 10 06:51:00 a1-migration.test hab[4747]: pg-sidecar-service.default(O): time="2021-12-10T06:51:00Z" level=error msg="failed to deploy sqitch" action=deploy_sqitch conn_info="postgresql://automate@127.0.0.1:10145/<database>?sslmode=verify-ca&sslcert=/hab/svc/automate-postgresql/config/server.crt&sslkey=/hab/svc/automate-postgresql/config/server.key&sslrootcert=/hab/svc/automate-postgresql/config/root.crt" db=automate-cs-oc-erchef db_database=postgres error="exit status 2" sqitch_dir=/hab/pkgs/chef/oc_erchef/14.11.1/20211124104838/schema/baseline user=automate

These are not creating the issues in the fresh install but failing in the upgrade It seems.
need investigate more on this.

@jashaik
Copy link
Contributor

jashaik commented Jan 4, 2022

chef/automate#6183

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants