Open amolari opened 4 years ago
This issue is being tracked internally with Jira bug VECLOUD-1079.
Hi amolari, we are attempting to reproduce this issue. Could you provide me some info on the iso that you used in the run: Big-IP version: Build number: was it an EHF:
Hi @f5-dimov BIGIP-14.1.2.8-0.0.7.iso no EHF. Note: same observation with previous 14.1.2.3, 14.1.2.6 and 14.1.2.7 versions.
We determined that this issue is in the BIG-IP product ISO. This issue is being tracked via the BIG-IP product bug BZ964217.
Product bugs are fixed based on severity and visibility. GitHub issues do not get linked to product bugs. Related Support cases are linked to product bugs and raise the product bug priority. If you create a support case, please reference the product bug ID so that it can be properly linked.
Is your feature request related to a problem? Please describe. We generate AWS AMIs with this tool. The instances then boot with timezone PDT. We see that in various system logs (such as /var/log/daemon.log). It switches to local time when NTP get synchronized. That means, our logging (cloug-init, cfn-* files,...) start with a PDT time.
Describe the solution you'd like From a more universal perspective, could the generated instances boot with timezone UTC?
Additional context