C
A practical addition: verify every supporting service, not just the Infra Server hosts. Chef Infra Server stores node objects and Ohai data in PostgreSQL and indexes them in OpenSearch, while cookbooks may live in bookshelf or external object storage; pin all of those to a Canadian region and document it. For backups, encrypt client-side before writing to Canadian storage, keep the encryption keys under Canadian control, and include a restore test in the retention process. Also check optional…
C
I'm planning a Chef Infra Server setup for a few Canadian clients, and some of them need personal data and system details kept in Canada because of PIPEDA, plus stricter public-sector rules in BC and Quebec. Here's the checklist I'm working from. I'd like to hear what others would add. Run the Infra Server on hosts physically located in Canada, and confirm the provider's region in writing. Keep the PostgreSQL data, search index and cookbook storage on the same Canadian hosts or region. Back up…
C
One thing worth deciding early is whether pwsh_package should shell out to pwsh -NoProfile -NonInteractive or call the package cmdlets in-process. Shelling out keeps behavior close to the existing powershell_package and lets you pass options like -Scope and -AllowClobber consistently, but make sure stderr and exit codes are surfaced clearly. If you publish it, documenting the supported PowerShell versions and how it handles module paths on macOS and Linux would make it easier for others to…
C
One thing to verify: the generated key_url still points at the same keyserver host over HTTPS, so if the IPv6 route to that host is broken at the TCP level, apt_repository may still fail when fetching the key. If the explicit key location works in your environment, the difference may be in the HTTP client used for explicit keys rather than the HKP path. Testing that location directly would confirm whether the workaround truly bypasses the IPv6 issue.
C
The 2026 chef-zero node-file DACL issue sounds unrelated to the vboxsf/network-share error. The original failure looks like Chef trying to read a Windows security descriptor via GetNamedSecurityInfo on a share that doesn't expose ACLs; hence "Incorrect function" while cmd mkdir works. A practical workaround is to create the directory with an execute resource (cmd /c mkdir) and use a guard, or otherwise avoid Chef managing ownership/ACL on that path.
C
The stack trace points at your local knife plugin, so separate that from Workstation 26 itself: temporarily move ~/.chef/plugins/knife/compliance.rb aside and run knife --help. If compliance disappears, it was likely never a built-in Workstation command—your migration is to package the plugin with its html-table dependency, or have it shell out to InSpec's HTML reporter if available, rather than keeping Workstation 25. I can't confirm Chef's roadmap; that part needs Chef support.
C
The socket-directory detail may be the key. If the upgrade's Sqitch runner connects through the default PostgreSQL socket while your cluster listens under /var/opt/opscode/postgresql/13/data, it could inspect a different database or registry and still report 'migrations to run: none'. Your manual deploy worked because you set PGHOST explicitly. Worth checking the upgrade logs for the PGHOST/socket it used and whether the default socket path points at another cluster. Capture that plus sqitch…
C
That stack trace is coming from your own plugin (`~/.chef/plugins/knife/compliance.rb`, line 12), not from knife itself. It does `require 'html/table'`, which comes from the `html-table` gem, and that gem simply isn't in the Ruby that Workstation 26 ships. Workstation 26 is now built on Habitat packages (`/hab/pkgs/core/ruby3_4/...`), so it has its own isolated Ruby and gem path. Any extra gems you had installed into the old `/opt/chef-workstation/embedded` Ruby didn't carry over after the…
C
We are delighted to announce the availability of Chef Automate 4.13.535. Security Updated the PostgreSQL 13 tuxcare patch to 1.0.1 to address the following CVEs: CVE-2026-6473 CVE-2026-6475 CVE-2026-6471 Updated NGINX to 1.31.4 LTS-2024 to address CVE-2026-9256, which fixes an ngx_http_rewrite_module vulnerability triggered by overlapping regex capture groups. Updated the OpenSearch tuxcare patch to 1.0.4 (1.3.20.tuxcare.1.0.4) to address the following CVEs in the bundled Apache CXF library:…
C
We are delighted to announce the availability of Chef Infra Client 19.4.46. Improvements Removed the experimental tag and warning message when running Chef Infra Client in Agentless Mode. (#16088) Deferred loading stringio in chef-utils until transport connections are opened in Agentless Mode, reducing gem load time by ~43% across all standard executions. (#16335) The chef_client_config resource now accepts two new properties: directory_specs lets you configure permissions (owner, group, mode,…
C
We are delighted to announce the availability of version 1.7.4 of Chef 360 Platform. Chef 360 Platform 1.7.4 introduces Courier job drafts and step reordering, adds metadata-driven dynamic configuration for interpreters, delivers a local execution mode for the Courier Runner, and resolves bugs affecting the DSM UI, device registration, and cookbook imports. Prerequisites Before upgrading to Chef 360 Platform 1.7.4, you must be running at least version 1.7.1. For more information, see the…
C
We are delighted to announce the availability of Chef InSpec 7.3.4. Bug fixes The oracledb_session resource now correctly parses query output from both sqlcl and sqlplus. Previously, an unsuppressed banner in sqlcl output and output that wasn't formatted as CSV in sqlplus broke result parsing. (#8010) The oracledb_session resource now correctly returns values for every column in multi-column query results. Previously, comma replacement altered CSV delimiters before parsing, and row flattening…
C
We are delighted to announce the availability of Chef InSpec 7.2.1. Bug fixes The --auto-install-gems flag now correctly falls back to install the Docker and Podman resource pack gems for bare resource names, such as docker and podman, in addition to sub-resources such as docker_container and podman_volume. Previously, running a profile with a bare docker or podman resource and --auto-install-gems raised an undefined method error, because the fallback pattern matching required at least one…
C
Thanks. We did check the PostgreSQL side in more detail and found something more specific than the {chef_sql,ping,throw,pang} status. PostgreSQL logs showed repeated failures like: SELECT value FROM kvpair WHERE key = $1 with: ERROR: relation "kvpair" does not exist We verified that the table was indeed missing: select schemaname, tablename from pg_tables where tablename='kvpair'; returned: 0 rows The upgraded package contains: /opt/opscode/embedded/servic…
C
That {chef_sql,ping,throw,pang} pattern is interesting — have you checked the actual erchef logs to see what's blowing up with the SQL connection attempt? The status endpoint tells you something's failing but not really what. Since it's fully reproducible with the same data and secrets, it does feel like something in the code path between 91 and 114 rather than your setup.
C
Update: Findings from further investigation (15.10.114 / 15.10.125) After additional troubleshooting, I wanted to share what we observed in our environment in case it helps others. Environment Upgrade path: Chef Infra Server 15.10.91 -> Chef Infra Server 15.10.114 and later: Chef Infra Server 15.10.91 -> Chef Infra Server 15.10.125 Both upgrades completed successfully and reported: [Infra Server Upgrade] - Latest PostgreSQL Database Migration Available: 1.37 [Infra Server Upgrade] - PostgreSQL…
C
We are delighted to announce the availability of Chef Automate 4.13.520. Security Resolved multiple security vulnerabilities across Chef Automate core services. Fixed a potential SQL injection vulnerability to ensure input sanitization and secure query execution. Bug fixes The chef-automate package-cleanup command now correctly preserves required Automate HA management packages during cleanup. Previously, it built the package whitelist only from actively running Habitat services, causing…
C
We are delighted to announce the availability of Chef Infra Server 15.10.125. Security Removed stale Rack and REXML gem directories that could be left on disk by the package manager during upgrades. chef-server-ctl reconfigure now removes gem versions below the required minimum versions. This addresses the following CVEs, which could be flagged during vulnerability scans even though the affected gems were not actively loaded: CVE-2025-61772 (Rack multipart denial-of-service, fixed in Rack 3.2.2…
C
We are delighted to announce the availability of Chef Habitat Builder 20260820! Summary We've promoted this release to the on-prem-base channel and is the recommended version for new and existing Chef Habitat On-Prem Builder deployments. It includes changes from several releases that were previously published to the base channel, including major version upgrades to the bundled MinIO and PostgreSQL packages and an updated Habitat Supervisor. Note: If you're upgrading an existing Chef Habitat…
C
This is a actual bug, as the output to the user should not be a stacktrace. When ChefUtils.windows? is true, chef-zero's own local-mode data store (chef/chef_fs/file_system/repository/nodes_dir.rb#create_child) unconditionally tries to set an owner/DACL on every node file it creates. There's no flag to turn this off, so you'll get a crash. I wrote the bug up as: * Local mode Windows stacktrace: node file DACL write fails · Issue #16309 · chef/chef · GitHub
C
As a workaround for the limitation with the fragile GPG/HKP path, I implemented a helper function that I can use: def ppa_key_url(ppa) owner, name = ppa.delete_prefix('ppa:').split('/', 2) lp_uri = URI("https://launchpad.net/api/1.0/~#{owner}/+archive/ubuntu/#{name}") response = Net::HTTP.get_response(lp_uri) raise "lessons: could not resolve signing key for #{ppa} from Launchpad (HTTP #{response.code})" unless response.is_a?(Net::HTTPSuccess) fingerprint =…
C
The powershell_package is really nice and I want to use it, but alas, it is ONLY for Windows. powershell_package 'psake' do action :install options '-Scope CurrentUser -AllowClobber' skip_publisher_check true end I use psake for my test harness on macOS and Unbuntu with pwsh. So I added a resource and implemented my own cross platform version: pwsh_package 'psake' do action :install options '-Scope CurrentUser -AllowClobber' skip_publisher_check true end
C
Description Chef's apt_repository resource does not provide behavioral parity with Ubuntu's add-apt-repository command when configuring Launchpad PPAs. When adding a PPA, apt_repository attempts to retrieve the repository signing key through the GPG/HKP keyserver path using keyserver.ubuntu.com. On a system where IPv6 routing to keyserver.ubuntu.com is broken or unavailable, the key retrieval attempts the non-functional IPv6 route and does not successfully fall back to the working IPv4 path. In…
C
We are delighted to announce the availability of version 1.7.3 of Chef 360 Platform. Chef 360 Platform 1.7.3 adds InSpec profile support through the Automate Connector, introduces a backup upload workflow for large file migrations, provides configurable replica scaling for the Automate Connector in on-premises deployments, and resolves bugs affecting login and node enrollment. Prerequisites Before upgrading to Chef 360 Platform 1.7.3, you must be running at least version 1.7.1. For more…
C
We are delighted to announce the availability of version 5.3.7 of Chef Supermarket. This release remediates security vulnerabilities across dependent packages in Chef Supermarket. Dependencies Upgraded Ruby from 3.1.2 to 3.1.5. Upgraded Rack from 2.2.20 to 2.2.23 in Supermarket and Omnibus; upgraded Fieri engine from 3.2.4 to 3.2.6. Pinned Puma to 5.6.9. Upgraded WEBrick from 1.9.1 to 1.9.2 in Supermarket and Omnibus. Security Upgraded Rack from v2.2.20 to v2.2.23 (Supermarket/Omnibus) and…
C
We are delighted to announce the availability of version 4.13.516 of Chef Automate. New features Adds audit log retention workflows, including retention for requested logs. Adds an audit-log download endpoint with support for HTTP range requests. Improvements Adds request_log_rotation_type configuration for erchef, bifrost, and bookshelf. Updates Chef Infra Server to 15.10.114. Updates OpenSearch TuxCare build to 1.3.20.tuxcare.1.0.3. Updates PostgreSQL TuxCare build to 13.23.tuxcare.1.0.1. Bug…
C
in order to escalate it to engineering for a bug fix we need a support ticket and may need to investigate it further with support. I haven't seen this issue reported by any other users so we may need to verify if it's an actual bug or a side case based on environment or something else.
C
I can submit the support ticket, but I don't think I need to raise it because everything went fine after I downgraded. I didn't even restore the Database. I'm pretty sure the new version has some issues; post it here as a bug report for your reference.
C
are you able to submit a support ticket for this issue?
C
Appreciate the confirmation, @Steven.Z.