Test spin up v13.1.0.1 in Openstack and as my environment only have single NIC, the on-boarding uses port 8443 as the management interface – similar with AWS.
The onboard scripts seem like hard-coded on port 443. Tried to put 127.0.0.1:8443 in the onboard.js but if you check the logs blow, it automatically append :443 at the end.
fbchan
commented
6 years ago
Test spin up v13.1.0.1 in Openstack and as my environment only have single NIC, the on-boarding uses port 8443 as the management interface – similar with AWS.
The onboard scripts seem like hard-coded on port 443. Tried to put 127.0.0.1:8443 in the onboard.js but if you check the logs blow, it automatically append :443 at the end.
[root@host-10-0-125-14:NO LICENSE:Standalone] cloud # /config/cloud/onboard.sh 2018-01-12T03:08:12.174Z info: /config/cloud/f5-cloud-libs/scripts/onboard.js called with /usr/bin/f5-rest-node /config/cloud/f5-cloud-libs/scripts/onboard.js -o /var/log/onboard.log --no-reboot --log-level verbose --host 127.0.0.1:8443 --user admin --password --port 443 --hostname sg-bigip.com --global-setting hostname:sg-bigip.com --set-root-password --ping www.f5.com 30 15 2018-01-12T03:08:12.180Z info: Using host-name option to override global-settings hostname 2018-01-12T03:08:12.196Z info: Onboard starting. 2018-01-12T03:08:12.201Z info: Initializing BIG-IP. 2018-01-12T03:08:12.204Z info: Waiting for BIG-IP to be ready. 2018-01-12T03:08:12.867Z verbose: tryUntil error: getaddrinfo ENOTFOUND 127.0.0.1:8443 127.0.0.1:8443:443 tries left: 2018-01-12T03:08:12.869Z verbose: Max tries reached. 2018-01-12T03:08:12.870Z verbose: tryUntil error: getaddrinfo ENOTFOUND 127.0.0.1:8443 127.0.0.1:8443:443 tries left: 90 2018-01-12T03:08:23.186Z verbose: tryUntil error: getaddrinfo ENOTFOUND 127.0.0.1:8443 127.0.0.1:8443:443 tries left: 2018-01-12T03:08:23.187Z verbose: Max tries reached. 2018-01-12T03:08:23.188Z verbose: tryUntil error: getaddrinfo ENOTFOUND 127.0.0.1:8443 127.0.0.1:8443:443 tries left: 89