GitLab operator upgrade stuck in Preparing state

How to Use GitLab Upgrade
1

:hugs: Please help fill in this template with all the details to help others help you more efficiently. Use formatting blocks for code, config, logs and ensure to remove sensitive data.

Problem to solve

GitLab operator upgrade stuck in Preparing state.

Describe your question in as much detail as possible:
I had an GitLab operator on OpenShift in version 1.2.1 with an error message: “Helm Chart 7.5.1 not found, Please use one of the following: 8.2.1, 8.1.3, 8.0.5”
I changed the Helm Chart version in the operator gitlab object to 8.0.5.
Now, my operator is stuck in pending state. I can’t change anything in the configuration anymore. The log of the controller of the operator displays a message “Internal error occurred”.
I tried to put the 7.5.1 version back in the gitlab object but it is denied.
What can I do to improve my situation?

  • What are you seeing, and how does that differ from what you expect to see?
    I should get a GitLab operator Ready status.

  • Consider including screenshots, error messages, and/or other helpful visuals

Steps to reproduce

Which troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?

Configuration

Provide screenshots from the GitLab UI showing relevant configuration, if applicable.
On self-managed instances, add the relevant configuration settings or changes.

Versions

GitLab operator: 1.2.1 on OpenShift v4.14.41

Please add an x whether options apply, and add the version information.

  • Self-managed
  • GitLab.com SaaS
  • Dedicated

Versions

  • GitLab (Web: /help or self-managed system information sudo gitlab-rake gitlab:env:info):
    GitLab operator: 1.2.1 on OpenShift v4.14.41

Helpful resources

  1. Check the FAQ for helpful documentation, issues/bugs/feature proposals, and troubleshooting tips.
  2. Before opening a new topic, make sure to search for keywords in the forum search
  3. Check the GitLab project for existing issues. If you encounter a bug, please create a bug report issue.
  4. Review existing troubleshooting docs.

Thanks for taking the time to be thorough in your request, it really helps! :blush: