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.

Sign up for GitHub

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

Jump to bottom

WA installation failed in Test Env with below logs #707

Open
ytheja31 opened this issue May 6, 2024 · 6 comments
Open

WA installation failed in Test Env with below logs #707

ytheja31 opened this issue May 6, 2024 · 6 comments
Labels
invalid This doesn't seem right

Comments

@ytheja31
Copy link

ytheja31 commented May 6, 2024

Describe the bug
Watson Assistance installation is failed

To Reproduce
While installing the watson-assistance using cloud-pak-deployer on AWS environment, installation is failed with below message.

module.cpd[0].null_resource.setup_instance_toplogy: Provisioning with 'local-exec'...

module.cpd[0].null_resource.setup_instance_toplogy (local-exec): Executing: ["/bin/sh" "-c" "echo "Setup Instance Topolgy to install cpfs and setup configmap for the Namespacescope operator" &&\n./installer-files/cpd/cpd-cli manage setup-instance-topology --release=4.8.3 --cpd_operator_ns=cpd-operator --cpd_instance_ns=cpd-instance --license_acceptance=true\n"]

module.cpd[0].null_resource.setup_instance_toplogy (local-exec): Setup Instance Topolgy to install cpfs and setup configmap for the Namespacescope operator

module.cpd[0].null_resource.setup_instance_toplogy (local-exec): [INFO] 2024-05-04T02:04:32.224677Z Checking architecture: amd64

module.cpd[0].null_resource.setup_instance_toplogy (local-exec): [INFO] 2024-05-04T02:04:32.224731Z Checking podman or docker

module.cpd[0].null_resource.setup_instance_toplogy (local-exec): [INFO] 2024-05-04T02:04:32.279736Z Dockerexe: podman

module.cpd[0].null_resource.setup_instance_toplogy (local-exec): [INFO] 2024-05-04T02:04:32.364277Z Container olm-utils-play-v2 is running already. Image: icr.io/cpopen/cpd/olm-utils-v2:latest

module.cpd[0].null_resource.setup_instance_toplogy (local-exec): [INFO] 2024-05-04T02:04:32.436114Z Processing subcommand setup-instance-topology

module.cpd[0].null_resource.setup_instance_toplogy (local-exec): [INFO] 2024-05-04T02:04:32.436180Z Run command: podman exec -it olm-utils-play-v2 setup-instance-topology --release=4.8.3 --cpd_operator_ns=cpd-operator --cpd_instance_ns=cpd-instance --license_acceptance=true

module.cpd[0].null_resource.setup_instance_toplogy (local-exec): running pre-validation routines (if any) for pre_setup_instance_topology..

module.cpd[0].null_resource.setup_instance_toplogy (local-exec): Sat May 4 02:04:32 UTC 2024

module.cpd[0].null_resource.setup_instance_toplogy (local-exec): [✘] No storage class defined for CommonService CR. Please specify --block_storage_class=

module.cpd[0].null_resource.setup_instance_toplogy (local-exec): [ERROR] 2024-05-04T02:04:32.973254Z cmd.Run() failed with exit status 1

module.cpd[0].null_resource.setup_instance_toplogy (local-exec): [ERROR] 2024-05-04T02:04:32.973317Z Command exception: The setup-instance-topology command failed (exit status 1). You may find output and logs in the /home/ec2-user/cp4d-deployment-master/selfmanaged-openshift/aws/cpd-cli-workspace/olm-utils-workspace/work directory.

module.cpd[0].null_resource.setup_instance_toplogy (local-exec): [ERROR] 2024-05-04T02:04:32.974710Z RunPluginCommand:Execution error: exit status 1

module.cpd[0].null_resource.setup_instance_toplogy (local-exec):

╷

│ Error: local-exec provisioner error

│

│ with module.cpd[0].null_resource.setup_instance_toplogy,

│ on cpd/cpd.tf line 85, in resource "null_resource" "setup_instance_toplogy":

│ 85: provisioner "local-exec" {

│

│ Error running command 'echo "Setup Instance Topolgy to install cpfs and

│ setup configmap for the Namespacescope operator" &&

│ ./installer-files/cpd/cpd-cli manage setup-instance-topology

│ --release=4.8.3 --cpd_operator_ns=cpd-operator

│ --cpd_instance_ns=cpd-instance --license_acceptance=true

│ ': exit status 1. Output: Setup Instance Topolgy to install cpfs and setup

│ configmap for the Namespacescope operator

│ [INFO] 2024-05-04T02:04:32.224677Z Checking architecture: amd64

│ [INFO] 2024-05-04T02:04:32.224731Z Checking podman or docker

│ [INFO] 2024-05-04T02:04:32.279736Z Dockerexe: podman

│ [INFO] 2024-05-04T02:04:32.364277Z Container olm-utils-play-v2 is running

│ already. Image: icr.io/cpopen/cpd/olm-utils-v2:latest

│ [INFO] 2024-05-04T02:04:32.436114Z Processing subcommand

│ setup-instance-topology

│ [INFO] 2024-05-04T02:04:32.436180Z Run command: podman exec -it

│ olm-utils-play-v2 setup-instance-topology --release=4.8.3

│ --cpd_operator_ns=cpd-operator --cpd_instance_ns=cpd-instance

│ --license_acceptance=true

│ running pre-validation routines (if any) for pre_setup_instance_topology..

│ Sat May 4 02:04:32 UTC 2024

│

│ [✘] No storage class defined for CommonService CR. Please specify

│ --block_storage_class=

│ [ERROR] 2024-05-04T02:04:32.973254Z cmd.Run() failed with exit status

│ 1

│ [ERROR] 2024-05-04T02:04:32.973317Z Command exception: The

│ setup-instance-topology command failed (exit status 1). You may find output

│ and logs in the

│ /home/ec2-user/cp4d-deployment-master/selfmanaged-openshift/aws/cpd-cli-workspace/olm-utils-workspace/work

│ directory.

│ [ERROR] 2024-05-04T02:04:32.974710Z RunPluginCommand:Execution

│ error: exit status 1

=========================================================================

Expected behavior
WA should install successfully.

Desktop (please complete the following information):
AWS environment - self-managed and ROSA openshift
@luigimolinaro
Copy link
Contributor

Could you please share information about storage being used in this installation ?

@fketelaars
Copy link
Collaborator

fketelaars commented May 6, 2024 via email

@ytheja31
Copy link
Author

ytheja31 commented May 6, 2024

Instance type- t3.large
EBS volume size -50 GB
EBS volume type - gp3

@ytheja31
Copy link
Author

ytheja31 commented May 6, 2024 via email

@ytheja31
Copy link
Author

ytheja31 commented May 6, 2024

Hi Team,
Can any one please suggest on above comment, it is high priority one. In dev 4.8.3 version was installed successfully.

@fketelaars
Copy link
Collaborator

The issue below was solved 3 weeks ago. Make sure you pull the latest changes from GitHub and build the deployer image. Then try again.

│ [✘] No storage class defined for CommonService CR. Please specify

│ --block_storage_class=

│ [ERROR] 2024-05-04T02:04:32.973254Z cmd.Run() failed with exit status

@fketelaars fketelaars added the invalid This doesn't seem right label May 6, 2024
@IBM IBM deleted a comment from ytheja31 May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
invalid This doesn't seem right
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@luigimolinaro @fketelaars @ytheja31