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

CI Deploy - Operator deploy - Missing StorageCluster UI Workflow #467

Open
penguinpages opened this issue Aug 24, 2024 · 3 comments
Open

Comments

@penguinpages
Copy link

OCP 4.16.8

ODF Operator GUI install you get: OpenShift Data Foundation and Client -> "Create StorageSystem" prompt as next step.

When you start to create storage you get wizard to offer more advanced options such as use of existing disk, or VMFS CSI, etc..

If you take deployment and build into YAML for CI, and run deploy it installs fine and again prompts for "Create StorageSystem" but only has simple YAML workflow option of kind "flashsystemcluster.odf.ibm.com/v1alpha1" vs "storagecluster.ocs.openshift.io/v1"

CI Result
image

GUI Result
image

Questions:

  1. What CRD or deploy component is missing in workflow is missing that removes the deployment where more advanced storage options appear correctly?
  2. When searching in UI for operator two options appear . But descriptions the same.

Ex: Operators -> Operator Hub
-- ODF -> RedHat ----> 4.17
image

-- ODF -> Openshift data Foundation --->
image

Seems to be a lot of querks with ODF deployment UI. And also, for shops with lots of deploy automation, what needs to be is documentation and or help on how to do this via CI.

@iamniting
Copy link
Member

Hi @penguinpages You will be able to see the missing workflow only if you refresh the browser and newly installed console plugin is triggered.

You are seeing 2 of them because you have a custom catalog source created in your cluster.

cc @SanjalKatiyar pls keep me honest here.

@SanjalKatiyar
Copy link
Contributor

Hi @penguinpages You will be able to see the missing workflow only if you refresh the browser and newly installed console plugin is triggered.

That's correct.
@penguinpages please follow the official documentation for more details (for UI install): https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.16/html/deploying_openshift_data_foundation_on_vmware_vsphere/deploy-using-dynamic-storage-devices-vmware#installing-openshift-data-foundation-operator-using-the-operator-hub_cloud-storage

If operator is installed via CLI:
Either apply https://github.com/red-hat-storage/odf-console/blob/release-4.16/test-prow-e2e.sh#L93-L98 manually,
OR,
Go to OCP console, "Installed Operators > Operator details (ODF) > Console plugin (right side section of details page)" and enable the plugin.
Screenshot 2024-08-26 at 12 57 29 PM

After that a pop-up with a message, "Web console update is available" will appears on the user interface. Click "Refresh web console" from this pop-up for the console changes to reflect.

This flow has been in place since ODF 4.9 release.

@SanjalKatiyar
Copy link
Contributor

Script: https://github.com/red-hat-storage/odf-console/blob/release-4.16/test-prow-e2e.sh is also how we install and dev test ODF e2e, if your end goal is to set up a CI pipeline you can take reference from here.

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

3 participants