Merge ~chad.smith/cloud-init:fix/opennebula-exclude-epochseconds into cloud-init:master
Proposed by
Chad Smith
Status: | Merged |
---|---|
Approved by: | Chad Smith |
Approved revision: | ed4e35e2965e67d14d5f814ead85eb2e69f49ceb |
Merge reported by: | Server Team CI bot |
Merged at revision: | not available |
Proposed branch: | ~chad.smith/cloud-init:fix/opennebula-exclude-epochseconds |
Merge into: | cloud-init:master |
Diff against target: |
15 lines (+3/-1) 1 file modified
cloudinit/sources/DataSourceOpenNebula.py (+3/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ryan Harper | Approve | ||
Server Team CI bot | continuous-integration | Approve | |
Review via email:
|
Commit message
opennebula: also exclude epochseconds from changed environment vars
In addition to EPOCHREALTIME there is also an EPOCHSECONDS environment
variable that OpenNebula needs to exclude as it is expected to change.
This commit supplements the other exclusion in commit
d1a2fe7307e9cf2
Without this fix, unittests will intermittently fail if
parse_shell_config is run across a timing boundary where the
EPOCHSECONDS changes mid-test.
LP: #1813641
To post a comment you must log in.
Newer bash (5.0) has these new variables, BASH_ARGV0, EPOCHSECONDS, and EPOCHREALTIME.
I don't think that the datasource invokes bash differently, nor do I think the config they source would be setting it; however; it is mutable, so maybe we want to also exclude that as well?