Issues with AWS Marketplace Offerings about cp4d-deployment HOT 14 CLOSED

OK so I was able to login to https://cpd-dm.apps.cp4d463.dm-cp4d-40.mettleci.cloud/zen/
using username "admin" and the same password I set in the Cloudformation template for the Cluster admin "ocadmin"

Although that is not the 'normal' behaviour.

from cp4d-deployment.

Hi @Alan111S ,
Thanks for bringing this up, Regarding the issues.

1. The cloud pak for data admin user password is similar to openshift user password. The info is in the user guide:
   https://ibm-mkpl-cp4d.s3.amazonaws.com/ibm-cloud-pak-for-data-on-aws-marketplace.pdf

2. Regarding the datastage - we do have seperate marketplace offering:
   https://aws.amazon.com/marketplace/pp/prodview-s42oa5unsg3tu?sr=0-2&ref_=beagle&applicationId=AWSMPContessa
   and also the ImagePullBackOff error is not expected , could you please share the install log from the s3 bucket to review.

cc: @anujsharma23

from cp4d-deployment.

Hi @shankarpentyala07

Regarding the first issue, I can get the initial admin password of the cluster either by:-
oc extract secret/admin-user-details --keys=initial_admin_password --to=- or cpd-cli manage get-cpd-instance-details --cpd_instance_ns=dm --get_admin_initial_credentials=true

That is not the problem. The problem is that I'm unable to login to the CP4D Web Interface because the admin user is Disabled. The error I get is something Incorrect user or password. I spent a long time messing with passwords before I finally realised the admin user was not enabled.

I have to run a command to specifically enable the admin user, like this:- export NAMESPACE=dm oc exec -it -n $NAMESPACE $(oc get pod -n $NAMESPACE -l component=usermgmt | tail -1 | cut -f1 -d\ ) -- bash -c "/usr/src/server-src/scripts/manage-user.sh --enable-user admin"

Then it works

from cp4d-deployment.

Thanks for the info re DataStage being a seperate Marketplace offering - I didn't realise that.

Regards the second issue - it's not really a DataStage problem.

The problem is because a pre-requisite step for installing Cloudpak mentioned in Item Number 7 Updating the global image pull secret from this page https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=installing-preparing-your-cluster is not being performed by your scripts.

from cp4d-deployment.

One more thing - I looked at the Cloudformation template for DataStage on Marketplace https://aws.amazon.com/marketplace/pp/prodview-s42oa5unsg3tu

The link to the template for New VPC is pointing to the template for the Existing VPC. So there is nowhere to download the template for deploying DataStage to a new VPC.

from cp4d-deployment.

Attaching Install Logs from S3 Bucket
cpd-trace.log
cpd-bootstrap.log

from cp4d-deployment.

Hi @shankarpentyala07

Regarding the first issue, I can get the initial admin password of the cluster either by:- oc extract secret/admin-user-details --keys=initial_admin_password --to=- or cpd-cli manage get-cpd-instance-details --cpd_instance_ns=dm --get_admin_initial_credentials=true

That is not the problem. The problem is that I'm unable to login to the CP4D Web Interface because the admin user is Disabled. The error I get is something Incorrect user or password. I spent a long time messing with passwords before I finally realised the admin user was not enabled.

I have to run a command to specifically enable the admin user, like this:- export NAMESPACE=dm oc exec -it -n $NAMESPACE $(oc get pod -n $NAMESPACE -l component=usermgmt | tail -1 | cut -f1 -d\ ) -- bash -c "/usr/src/server-src/scripts/manage-user.sh --enable-user admin"

Then it works

Hi @Alan111S , I did built a cluster and recheck , I was able to login to cloud pak for data using the openshift password .Could you please recheck .

Thanks for the info re DataStage being a seperate Marketplace offering - I didn't realise that.

Regards the second issue - it's not really a DataStage problem.

The problem is because a pre-requisite step for installing Cloudpak mentioned in Item Number 7 Updating the global image pull secret from this page https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=installing-preparing-your-cluster is not being performed by your scripts.

We do update global pulll-secret. From the bootstrap log , I see add-cred-to-global-pull-secret is executed. For reference , below is the log:

�[0m�[1mmodule.cpd[0].null_resource.login_cluster: Creation complete after 1m43s [id=2544093640001771114]�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Creating...�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Provisioning with 'local-exec'...�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0] (local-exec):�[0m �[0m(output suppressed due to sensitive value in config)
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0] (local-exec):�[0m �[0m(output suppressed due to sensitive value in config)
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0] (local-exec):�[0m �[0m(output suppressed due to sensitive value in config)
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0] (local-exec):�[0m �[0m(output suppressed due to sensitive value in config)
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0] (local-exec):�[0m �[0m(output suppressed due to sensitive value in config)
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0] (local-exec):�[0m �[0m(output suppressed due to sensitive value in config)
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0] (local-exec):�[0m �[0m(output suppressed due to sensitive value in config)
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0] (local-exec):�[0m �[0m(output suppressed due to sensitive value in config)
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0] (local-exec):�[0m �[0m(output suppressed due to sensitive value in config)
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0] (local-exec):�[0m �[0m(output suppressed due to sensitive value in config)
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0] (local-exec):�[0m �[0m(output suppressed due to sensitive value in config)
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0] (local-exec):�[0m �[0m(output suppressed due to sensitive value in config)
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [10s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [20s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [30s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [40s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [50s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [1m0s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [1m10s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [1m20s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [1m30s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [1m40s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [1m50s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [2m0s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [2m10s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [2m20s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [2m30s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [2m40s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [2m50s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [3m0s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [3m10s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [3m20s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [3m30s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [3m40s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [3m50s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [4m0s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [4m10s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [4m20s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [4m30s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [4m40s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [4m50s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Still creating... [5m0s elapsed]�[0m�[0m
�[0m�[1mmodule.cpd[0].null_resource.configure_global_pull_secret[0]: Creation complete after 5m1s [id=4185688590919790730]�[0m

It would be helpful to view output of below command to prior datastage install

oc get secret/pull-secret \
  -n openshift-config \
  --template='{{index .data ".dockerconfigjson" | base64decode}}' 

One more thing - I looked at the Cloudformation template for DataStage on Marketplace https://aws.amazon.com/marketplace/pp/prodview-s42oa5unsg3tu

The link to the template for New VPC is pointing to the template for the Existing VPC. So there is nowhere to download the template for deploying DataStage to a new VPC.

Thanks a lot for bringing this up. I will work with marketplace team to get it updated.

from cp4d-deployment.

You said:- Hi @Alan111S , I did built a cluster and recheck , I was able to login to cloud pak for data using the openshift password .Could you please recheck .

I'm trying to login to here:- https://cpd-dm.apps.cp4d463.dm-cp4d-40.mettleci.cloud/zen/

Using username 'admin' and password obtained using:-
[root@ip-10-0-130-58 ec2-user]# oc extract secret/admin-user-details --keys=initial_admin_password --to=- # initial_admin_password lzywEqsHSN05 [root@ip-10-0-130-58 ec2-user]#
From the screenshot, you can see it is not working

from cp4d-deployment.

@Alan111S I have deleted the pull-secret output since it contains creds and I see the pull-secret has cp.icr.io registry creds updated in it.

The cloud pak for data password is same as your openshift password.Please try logging into cloud pak for data with admin /openshift username password you supplied when creating stack.

This info can be also found from the outputs section in the stack.
Please refer step 6. Login to Cloud Pak for Data web client in below user gudie.
https://ibm-mkpl-cp4d.s3.amazonaws.com/ibm-cloud-pak-for-data-on-aws-marketplace.pdf

from cp4d-deployment.

You wrote "The cloud pak for data password is same as your openshift password."

No, that's not correct. The openshift user I have set as "ocadmin" and I have set the password as a parameter in the CF template.

I can use the ocadmin user to login to the Openshift console here:- https://console-openshift-console.apps.cp4d463.dm-cp4d-40.mettleci.cloud/dashboards/

But I can't use ocadmin to login to https://cpd-dm.apps.cp4d463.dm-cp4d-40.mettleci.cloud/zen/ (see previous screenshot). You need to use 'admin' and get the initial admin password.

As far as I know, that has never been possible and I have built CP4D Versions 3.01, 3.5, 4.0, 4.01, 4.02 and 4.5 as well as this 4.6.3.

If this is still unclear, maybe we can get on a webex after Easter so I can show you. Or if you believe it should work, you can show me !

from cp4d-deployment.

Sure - I will setup a webex meeting.
What I meant is cloud pak for data credentials are:
Username: admin
Password: same as openshift user ocsadmin password passed to the cft.

from cp4d-deployment.

Thanks for the info re DataStage being a seperate Marketplace offering - I didn't realise that.

Regards the second issue - it's not really a DataStage problem.

The problem is because a pre-requisite step for installing Cloudpak mentioned in Item Number 7 Updating the global image pull secret from this page https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=installing-preparing-your-cluster is not being performed by your scripts.

This turns out to be because I was using my IBM email address as the CPD API Username but it should be "cp".

from cp4d-deployment.

Thanks @Alan111S . Are we good to close this ticket?
I will keep you posted about the datastage refresh of existing vpc pointing to new VPC once its completed by AWS team.

from cp4d-deployment.

@shankarpentyala07 Yes, sure.

from cp4d-deployment.