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

Keep getting: "message":"undefined #149

Open
hrdina28 opened this issue Oct 13, 2024 · 1 comment
Open

Keep getting: "message":"undefined #149

hrdina28 opened this issue Oct 13, 2024 · 1 comment

Comments

@hrdina28
Copy link

hrdina28 commented Oct 13, 2024

Description

Hello,

I am having issues with as follows:
{
"class": "Cloud_Failover",
"environment": "aws",
"controls": {
"class": "Controls",
"logLevel": "silly"
},
"externalStorage": {
"scopingName": "jlo-4"
}
}
curl -su admin: -X POST -d @cfe.json http://localhost:8100/mgmt/shared/cloud-failover/declare | jq .
{
"message": "undefined -> Also see cloud docs link for more help: https://clouddocs.f5.com/products/extensions/f5-cloud-failover/latest/userguide/troubleshooting.html"
}
Sun, 13 Oct 2024 12:16:30 GMT - fine: [f5-cloud-failover] HTTP Request - POST /declare
Sun, 13 Oct 2024 12:16:30 GMT - fine: [f5-cloud-failover] Successfully validated declaration
Sun, 13 Oct 2024 12:16:30 GMT - info: [f5-cloud-failover] Global logLevel set to 'silly'
Sun, 13 Oct 2024 12:16:30 GMT - finest: [f5-cloud-failover] Modifying existing data group f5-cloud-failover-state with body {"name":"f5-cloud-failover-state","type":"string","records":[{"name":"state","data":"eyJjb25maWciOnsiY2xhc3MiOiJDbG91ZF9GYWlsb3ZlciIsImVudmlyb25tZW50IjoiYXdzIiwiY29udHJvbHMiOnsiY2xhc3MiOiJDb250cm9scyIsImxvZ0xldmVsIjoic2lsbHkifSwiZXh0ZXJuYWxTdG9yYWdlIjp7InNjb3BpbmdOYW1lIjoiamxvLTQifSwic2NoZW1hVmVyc2lvbiI6IjIuMS4zIn19"}]}
Sun, 13 Oct 2024 12:16:33 GMT - info: [f5-cloud-failover] Successfully wrote Failover trigger scripts to filesystem
Sun, 13 Oct 2024 12:16:34 GMT - finest: [f5-cloud-failover] Device initialization complete
Sun, 13 Oct 2024 12:16:34 GMT - finest: [f5-cloud-failover] Fetched proxy settings:
Sun, 13 Oct 2024 12:16:34 GMT - finest: [f5-cloud-failover] {"protocol":"http","host":"172.31.1.246","port":"8888","username":"","password":"********"}
Sun, 13 Oct 2024 12:16:59 GMT - finest: socket 456 closed
Sun, 13 Oct 2024 12:17:25 GMT - finest: socket 457 opened
Sun, 13 Oct 2024 12:17:30 GMT - finest: socket 457 closed
Sun, 13 Oct 2024 12:17:43 GMT - finest: socket 458 opened
Sun, 13 Oct 2024 12:17:48 GMT - finest: socket 458 closed
Sun, 13 Oct 2024 12:18:03 GMT - finest: socket 459 opened
Sun, 13 Oct 2024 12:18:08 GMT - finest: socket 459 closed
Sun, 13 Oct 2024 12:18:18 GMT - finest: socket 460 opened

Based on tcpdump I am seeing traffic leaving my proxy, FIN send from AWS. Strange is that bucket is empty. I would expect something to be there. I modified IAM role to allow full access to S3, but nothing.
Any tips?
I used the CFT template.

Thank you

Best regards

Environment information

For bugs, enter the following information:

  • Cloud Failover Extension Version: 2.1.3
  • BIG-IP version: 17.1.1
  • Cloud provider: AWS

Severity Level

Severity: 2

@hrdina28
Copy link
Author

hrdina28 commented Oct 14, 2024

Seems to be problem with proxy hadling:
While trying: curl -v -x http://172.31.1.246:8888 -X HEAD https://jlo-4.s3.amazonaws.com/ I am getting response 403. So correct.
While CFE generates:
image
Its not using CONNECT command to proxy. Is that valid?

image

Mon, 14 Oct 2024 08:38:09 GMT - fine: [f5-cloud-failover] HTTP Request - POST /declare
Mon, 14 Oct 2024 08:38:09 GMT - fine: [f5-cloud-failover] Successfully validated declaration
Mon, 14 Oct 2024 08:38:09 GMT - info: [f5-cloud-failover] Global logLevel set to 'silly'
Mon, 14 Oct 2024 08:38:09 GMT - finest: [f5-cloud-failover] Modifying existing data group f5-cloud-failover-state with body {"name":"f5-cloud-failover-state","type":"string","records":[{"name":"state","data":"eyJjb25maWciOnsiY2xhc3MiOiJDbG91ZF9GYWlsb3ZlciIsImVudmlyb25tZW50IjoiYXdzIiwiY29udHJvbHMiOnsiY2xhc3MiOiJDb250cm9scyIsImxvZ0xldmVsIjoic2lsbHkifSwiZXh0ZXJuYWxTdG9yYWdlIjp7InNjb3BpbmdOYW1lIjoiamxvLTQifSwiZmFpbG92ZXJSb3V0ZXMiOnsiZW5hYmxlZCI6dHJ1ZSwic2NvcGluZ1RhZ3MiOnsiZjVfY2xvdWRfZmFpbG92ZXJfbGFiZWwiOiJiaWdpcF9oaWdoX2F2YWlsYWJpbGl0eV9zb2x1dGlvbiJ9LCJzY29waW5nQWRkcmVzc1JhbmdlcyI6W3sicmFuZ2UiOiIxOTIuMTY4LjAuMC8yNCJ9XSwicm91dGVUYWJsZUlkIjoicnRiLTBkZDVlZDY3In0sInNjaGVtYVZlcnNpb24iOiIyLjEuMyJ9fQ=="}]}
Mon, 14 Oct 2024 08:38:12 GMT - info: [f5-cloud-failover] Successfully wrote Failover trigger scripts to filesystem
Mon, 14 Oct 2024 08:38:13 GMT - finest: [f5-cloud-failover] Device initialization complete
Mon, 14 Oct 2024 08:38:13 GMT - finest: [f5-cloud-failover] Fetched proxy settings:
Mon, 14 Oct 2024 08:38:13 GMT - finest: [f5-cloud-failover] {"protocol":"http","host":"172.31.1.246","port":"8888","username":"","password":"********"}
Mon, 14 Oct 2024 08:38:18 GMT - finest: socket 463 closed

Thank you

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

1 participant