You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Launchpad user Chad Smith(chad.smith) wrote on 2019-01-28T18:50:22.044156+00:00
Just like recent BUG: #1813383 bash on disco now exposed EPOCHSECONDS environment variable as well as EPOCHREALTIME.
OpenNebula datasource inspects all bash environment variables in order to surfaces variables which have changed across bash env invocations. Since EPOCHREALTIME and EPOCHSECONDS are both known to increase across environment queries, OpenNebula needs to exclude both of these values from
potential lists of changed environment variables to avoid false positives.
Launchpad user Chad Smith(chad.smith) wrote on 2019-05-10T18:08:04.594456+00:00
This bug is believed to be fixed in cloud-init in version 19.1. If this is still a problem for you, please make a comment and set the state back to New
This bug was originally filed in Launchpad as LP: #1813641
Launchpad details
Launchpad user Chad Smith(chad.smith) wrote on 2019-01-28T18:50:22.044156+00:00
Just like recent BUG: #1813383 bash on disco now exposed EPOCHSECONDS environment variable as well as EPOCHREALTIME.
OpenNebula datasource inspects all bash environment variables in order to surfaces variables which have changed across bash env invocations. Since EPOCHREALTIME and EPOCHSECONDS are both known to increase across environment queries, OpenNebula needs to exclude both of these values from
potential lists of changed environment variables to avoid false positives.
This intermittent bug caused a FTBFS for cloud-init in disco:
https://launchpadlibrarian.net/408452856/buildlog_ubuntu-disco-amd64.cloud-init_18.5-17-gd1a2fe73-0ubuntu1_BUILDING.txt.gz
The text was updated successfully, but these errors were encountered: