F5Networks / f5-google-gdm-templates-v2

Google Deployment Templates for quickly deploying BIG-IP services in Google Cloud Platform
5 stars 13 forks source link

Quickstart BIGIP - Unable to login #25

Open akayaz opened 2 months ago

akayaz commented 2 months ago

Describe the bug

I've followed the provided documentation and successfully deployed the quickstart template in my GCP project. But I cannot login into the management instance. I've followed the steps outlined, and i've been trying with admin/ as per the readme but it doesn't work. Also I cannot authenticate using SSH to the instance, the when I provide the value equivalent to as a password, authentication fails as well

What is the default admin password for the management console and what are the steps to get the right password to login into the console or ssh?

Expected behavior

login to the BIG IP Web ui using admin /

Current behavior

Unable to login into the BIG IP Web UI using admin /

mikeshimkus commented 2 months ago

@akayaz You should be able to login via SSH using key authentication. Google Cloud should copy all the public keys in your project to the instance. Once in, can you share the contents of the files in /var/log/cloud/?

akayaz commented 2 months ago

Thanks @mikeshimkus I was able to login via SSH using cloudshell; here is the content of the /var/log/cloud image

mikeshimkus commented 2 months ago

@akayaz Can you share the contents of all those log files, please?

akayaz commented 2 months ago

Here are the files @mikeshimkus There are only 2 as the startup-script-pre-nic-swap.log is empty

bigIpRuntimeInit.log startup-script-post-swap-nic.log

mikeshimkus commented 2 months ago

The logs indicate onboarding finished successfully. You should have been able to login using admin and the instance ID as the password. Did that not work?

akayaz commented 2 months ago

@mikeshimkus unfortunately it's not working. I've tried with the following : gcloud deployment-manager manifests describe --deployment=yaz-f5-quickstart --format="value(layout)" | yq '.resources[0].outputs[] | select(.name | contains("bigIpInstanceId")).finalValue'

but also gcloud deployment-manager manifests describe --deployment=yaz-f5-quickstart --format="value(layout)" | yq '.resources[0].outputs[] | select(.name | contains("bigIpInstanceName")).finalValue' as per the readme

None is working and the login keep failing

Is there a way to reset the password ?

mikeshimkus commented 2 months ago

Yes, if you are in with the SSH key you can use the standard tmsh commands to reset passwords: https://my.f5.com/manage/s/article/K13121

This is the lookup for instance ID from metadata. If you view the instance metadata from the GCP console, does the value match what you get from the deployment outputs?

` - name: BIGIP_PASSWORD type: url value: http://169.254.169.254/computeMetadata/v1/instance/id headers:

akayaz commented 2 months ago

The value doesn't seem to match; this is what I can see in the console as the Instance ID:

image
akayaz commented 2 months ago

thanks @mikeshimkus I've followed the documentation and reset the password using the tmsh tool. This is something that should be added in the readme in case anyone face the same issue

mikeshimkus commented 2 months ago

Did either the value from the command or the one from metadata work with admin? Seems like a bug if not.

curtkersey commented 23 hours ago

Hello @mikeshimkus , I am seeing the same issue -- not able to login as user admin or quickstart after deploying using the instance ID as the password. I was able to login via admin user using SSH key. I checked, and the value for bigIpInstanceId in output is the same as the instance ID via the curl command to view metadata.

From output command:

From curl command: % curl http://169.254.169.254/computeMetadata/v1/instance/id -H "Metadata-Flavor: Google"
1207348076324492689

I am adding the log files from my deployment.

I have done it several times - same result each time. Let me know if there is any more data that you need.

bigIpRuntimeInit.log startup-script-post-swap-nic.log