-
Notifications
You must be signed in to change notification settings - Fork 45
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
f5-bigip-runtime-init error: Error getting token 400 #34
Comments
Interface 1.1 is only mapped once, it is just logging the same information twice. It appears that you are getting the 400 when trying to make a request to the /mgmt/tm/sys/license endpoint, which indicates the issue is getting the token from BIG-IP REST API, not Azure. For your last question, yes, it is by design. When you pass bigIpPasswordSecretValue it will create a new secret as documented here: https://github.com/F5Networks/f5-azure-arm-templates-v2/tree/main/examples/failover#prerequisites |
Thanks for response, I'll notice when ARM script is done that I'm not able to logon to F5 with password set for parameter bigIpPasswordSecretValue This is how I today have it configured. "bigIpPasswordSecretId": { |
If runtime init did not succeed in applying the DO config for any reason, then you would not be able to login using that password. The getting of the auth token for BIG-IP happens before the DO config, so that would not be the issue. Can you share the entire sanitized output of /var/log/cloud/startup-script.log? |
I'm not able after what's have been configured able to login with my given credential. Sound like a potential reason why accessing license end point. Another with worth to mention is I'm keeping my secret key each time I'm re-deploy other with is fails with object already exist, and object in Azure cant be purged. Device 1
Device 2
[azureuser@localhost:NO LICENSE:Standalone] ~ # cat of /var/log/cloud/bigIpRuntimeInit.log
|
Hi @DahlPatric, the templates don't really support redeployment very well. If you have a failed deployment, the best bet is to delete the previous deployment and try again. In this case the behavior you're seeing is expected; since the first deployment created the key vault and secret, on the second deployment you would need to provide the existing secret ID, not the secret value. The two logs you provided seem to be from different runs. The runtime init log shows that the config file failed YAML linting. Can you completely remove any failed deployments you have, then try again and share the results (including the logs and the template parameters you used)? |
Hi! Removed all objects except from Key vault secret that I'm now reference to in script.
Re-run script again and it still fails. Same place as before. run runtime-init manually:
|
Can you share the full template parameters? Is bigIpPasswordSecretId the secret created from a previous run? What did you use for bigIpUserAssignManagedIdentity? These templates have not been tested in Azure China, so the best course of action would be to create an RFE for that. I'll ask someone to reach out to you directly for more information. |
Hi @DahlPatric, as Mike mentioned the templates are not tested or supported in Azure China. There is no plan to support this region. Let me know if you have any comments or concerns. |
@G-gonzalezjimenez
|
Describe the bug
Runtime init script end with "Error getting token 400"
Interface:1.1 seams to be mapped twice could this be related to 400 error message?
There is also some license issues.
Current behavior
2024-02-21T15:23:58.551Z [32141]: info: Resolving parameters
2024-02-21T15:23:58.606Z [32141]: info: Interface:1.2
2024-02-21T15:23:58.607Z [32141]: info: MAC address found for 1.2: 00:17:fa:07:9f:09
2024-02-21T15:23:58.607Z [32141]: info: Local interface 2 MAC address 0017fa079f09 matches Azure network interface 2 MAC address 0017fa079f09
2024-02-21T15:23:58.613Z [32141]: info: Interface:mgmt
2024-02-21T15:23:58.614Z [32141]: info: MAC address found for mgmt: 00:17:fa:07:9e:df
2024-02-21T15:23:58.615Z [32141]: info: Local interface 0 MAC address 0017fa079edf matches Azure network interface 0 MAC address 0017fa079edf
2024-02-21T15:23:58.621Z [32141]: info: Interface:1.1
2024-02-21T15:23:58.621Z [32141]: info: MAC address found for 1.1: 00:17:fa:07:9a:eb
2024-02-21T15:23:58.622Z [32141]: info: Local interface 1 MAC address 0017fa079aeb matches Azure network interface 1 MAC address 0017fa079aeb
2024-02-21T15:23:58.628Z [32141]: info: Interface:1.1
2024-02-21T15:23:58.628Z [32141]: info: MAC address found for 1.1: 00:17:fa:07:9a:eb
2024-02-21T15:23:58.629Z [32141]: info: Local interface 1 MAC address 0017fa079aeb matches Azure network interface 1 MAC address 0017fa079aeb
2024-02-21T15:23:58.758Z [32141]: error: Error getting token 400
2024-02-21T15:23:58.758Z [32141]: info: Sending F5 Teem report for failure case.
2024-02-21T15:23:59.013Z [32141]: warn: Problem with getting data from /mgmt/tm/sys/license endpoint. Leaving regKey with default value
2024-02-21T15:23:59.014Z [32141]: info: {"id":"ba9d9528-e875-994c-95725ff36b09","product":"BIG-IP","cpuCount":8,"diskSize":86016,"memoryInMb":32176,"version":"16.1.4.2","nicCount":3,"platformId":"Z100","hostname":"bigip1","management":"10.45.136.69/26","provisionedModules":{"ltm":"nominal"},"installedPackages":{},"environment":{"pythonVersion":"Python 2.7.5","pythonVersionDetailed":"2.7.5 (default, Dec 1 2023, 09:40:19) \n[GCC 4.8.5 20150623 (Red Hat 4.8.5-16)]","nodeVersion":"v6.9.1","libraries":{"ssh":"OpenSSH_7.4p1, OpenSSL 1.0.2u-fips 20 Dec 2019"}}}
2024-02-21T15:23:59.270Z [32141]: error: Device is not licensed yet
Your Environment
cat /config/cloud/secret_id
BigIpSecret/
cat /config/cloud/vault_url
https://f5-kv.vault.azure.cn
cat /config/cloud/license_key
XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
"bigIpPasswordSecretId": {
"value": "https://f5-kv.vault.azure.cn/secrets/BigIpSecret/"
},
"bigIpPasswordSecretValue": {
"value": ""
},
Been switch between using either bigIpPasswordSecretValue Only or as now last time bigIpPasswordSecretId.
What I notice is that if i'm using bigIpPasswordSecretValue Azure Secrets object sill get's created, or is this per design?
The text was updated successfully, but these errors were encountered: