Unable to access AI-native features page and configure the models .

Summary

When accessing the AI-native features page, the GraphQL query getAiFeatureSetting returns a 500 error:

"exception.class":"FrozenError"
"exception.message":"can't modify frozen Hash: {:code_generations=>0, :code_completions=>1, :duo_chat=>2, ...}"

Stack trace shows the error occurs at:

- ee/app/models/ai/feature_setting.rb:79:in 'allowed_features'
- Using except! on a frozen hash

The allowed_features method in Ai::FeatureSetting is attempting to modify a frozen hash when Premium license is detected.

Steps to reproduce

  1. Deploy GitLab 18.2.1-ee with Premium license
  2. Configure Duo self-hosted models
  3. Navigate to Admin → GitLab Duo → Configure Duo Self-Hosted → Ai-native features
  4. Observe 500 error

Example Project

What is the current bug behavior?

The allowed_features method in Ai::FeatureSetting is attempting to modify a frozen hash when Premium license is detected. As a result, cannot access AI Feature Settings UI

What is the expected correct behavior?

User should be able to access the Ai-native features page as expected.

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

 - GitLab Version: 18.2.1-ee
 - License Type: Premium
 - Self-Hosted Model: Claude-3 via LiteLLM

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Workaround

Option 1 :User can update AI feature settings via Rails console.

Option 2 : Enable Use models and features in GitLab Duo Self-Hosted option under Admin area GitLab Duo-> Configuration

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.

Edited by Vidhya Hariharan