Deploying 2-nic results in startup-script onboard failure retrieving MAC

JeffGiroux commented 2 years ago

Do you already have an issue opened with F5 support?

GitHub Issues are consistently monitored by F5 staff, but should be considered as best-effort only and you should not expect to receive the same level of response as provided by F5 Support. Please open a case with F5 if this is a critical issue.

Description

Deploying 2-nic and the stack is running forever on the bigip child stack. When I view EC2 instances, it shows up and running. All though, when I SSH and check logs I see a failed onboard script.

Also, "fetch" is spelled wrong in the runtime init logs :)

2022-02-15T23:49:05.796Z [9216]: info: Resolving parameters
2022-02-15T23:49:06.170Z [9216]: info: Interface:1.1
2022-02-15T23:49:06.172Z [9216]: info: MAC adddress is not populated on 1.1 BIGIP interface. Trying to re-fecth interface data.
 Left attempts: 99
2022-02-15T23:49:06.175Z [9216]: info: Interface:1.1
2022-02-15T23:49:06.176Z [9216]: info: MAC adddress is not populated on 1.1 BIGIP interface. Trying to re-fecth interface data.
 Left attempts: 99
2022-02-15T23:49:06.181Z [9216]: info: Interface:1.2
2022-02-15T23:49:06.182Z [9216]: error: Cannot read property 'macAddress' of undefined
2022-02-15T23:49:06.182Z [9216]: info: Sending F5 Teem report for failure case.
2022-02-15T23:49:07.635Z [9216]: info: {"id":"1b8e2fec-c24a-c3d4-b13550422d66","product":"BIG-IP","cpuCount":8,"diskSize":10240
0,"memoryInMb":31376,"version":"16.1.0","nicCount":2,"regKey":"XUNNE-BZUUM-ZQLHB-LSYYL-TLUQXZW","platformId":"Z100","hostname":
"ip-10-0-1-11.us-west-2.compute.internal","management":"10.0.1.11/24","provisionedModules":{"ltm":"nominal"},"installedPackages
":{},"environment":{"pythonVersion":"Python 2.7.5","pythonVersionDetailed":"2.7.5 (default, Jun 22 2021, 22:47:51) \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"}}}
2022-02-15T23:49:15.862Z [9216]: info: F5 Teem report was successfully sent for failure case.
2022-02-15T23:49:15.863Z [9216]: info: Cannot read property 'macAddress' of undefined
2022-02-15T23:49:16.183Z [9216]: info: Interface:1.1
2022-02-15T23:49:16.183Z [9216]: info: MAC adddress is not populated on 1.1 BIGIP interface. Trying to re-fecth interface data.
 Left attempts: 98
2022-02-15T23:49:16.190Z [9216]: info: Interface:1.1
2022-02-15T23:49:16.190Z [9216]: info: MAC adddress is not populated on 1.1 BIGIP interface. Trying to re-fecth interface data.
 Left attempts: 98
+ [[ 1 -eq 0 ]]
++ date +%Y-%m-%dT%H:%M:%S.%3NZ
+ echo '2022-02-15T15:49:17.869Z : Startup Script Finish'
2022-02-15T15:49:17.869Z : Startup Script Finish
+ rm -f /tmp/6337.tmp

As for parameters, I'm using the repo's as-is 3nic payg without any modifications. https://f5-cft-v2.s3.amazonaws.com/f5-aws-cloudformation-v2/v1.1.0.0/examples/quickstart/bigip-configurations/runtime-init-conf-3nic-payg.yaml

Template

https://github.com/F5Networks/f5-aws-cloudformation-v2/tree/main/examples/quickstart

Severity Level

2

JeffGiroux commented 2 years ago

After submitting the ticket, I realized I was trying to deploy a 2nic BIG-IP but the runtime init config parameter was still pointing to the 3nic URL. This makes since why the MAC address failed as the lookup would not have matched. I redeployed and this time I pointed my runtime init parameter to the 2nic.

  {
    "ParameterKey": "bigIpRuntimeInitConfig",
    "ParameterValue": "https://f5-cft-v2.s3.amazonaws.com/f5-aws-cloudformation-v2/v1.1.0.0/examples/quickstart/bigip-configurations/runtime-init-conf-2nic-payg.yaml"
  },

Doc suggestion: if changing numNics then make a note in README to also update the runtime init conf file to match your number of desired NICs as well.

shyawnkarim commented 2 years ago

Thanks for reporting this needed update to our documentation. We are now tracking this with internal ID ESECLDTPLT-2995.

Additionally, I've created a separate bug ticket, ESECLDTPLT-2996, to address the misspelling in the logs. Nice catch.

JeffGiroux commented 2 years ago

After more README digging, you in fact already have this warning for users in the readme. See below. As a result, I'm not sure any further documentation is needed regarding numNics and changing runtime config file name.

By default, this solution deploys a 3NIC BIG-IP using the example `runtime-init-conf-3nic-payg.yaml` runtime-init config file.

To deploy a **1NIC** instance:
  1. Update the **bigIpRuntimeInitConfig** input parameter to reference a corresponding `1nic` config file (for example, runtime-init-conf-1nic-payg.yaml )
  2. Update the **numNics** input parameter to **1**

To deploy a **2NIC** instance:
  1. Update the **bigIpRuntimeInitConfig** input parameter to reference a corresponding `2nic` config file (for example, runtime-init-conf-2nic-payg.yaml )
  2. Update the **numNics** input parameter to **2**

shyawnkarim commented 2 years ago

Ok, leaving story in place to use spellcheck. ;-)

Thanks for update.

shyawnkarim commented 2 years ago

Closing.

This ticket was completed with Release 2.2.0.0.

F5Networks / f5-aws-cloudformation-v2