How bad can a bug get? an empirical analysis of software failures in the OpenStack cloud computing platform
Open accessThe DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
Cloud management systems provide abstractions and APIs for programmatically configuring cloud infrastructures. Unfortunately, residual software bugs in these systems can potentially lead to high-severity failures, such as prolonged outages and data losses. In this paper, we investigate the impact of failures in the context widespread OpenStack cloud management system, by performing fault injection and by analyzing the impact of the resulting failures in terms of fail-stop behavior, failure detection through logging, and failure propagation across components. The analysis points out that most of the failures are not timely detected and notified; moreover, many of these failures can silently propagate over time and through components of the cloud management system, which call for more thorough run-time checks and fault containment.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Reliability and Availability of Cloud Computing
Bauer, E., & Adams, R. (2012) · doi:10.1002/9781118393994 · Cited by 228
Cited by
A Survey on Automated Log Analysis for Reliability Engineering
He, S., He, P., Chen, Z., Yang, T., Su, Y., & Lyu, M. R. (2022) · ACM Computing Surveys · doi:10.1145/3460345 · Cited by 334
RCAEval: A Benchmark for Root Cause Analysis of Microservice Systems with Telemetry Data
Pham, L., Zhang, H., Ha, H., Salim, F., & Zhang, X. (2025) · Companion Proceedings of the ACM on Web Conference 2025 · doi:10.1145/3701716.3715290 · Cited by 72
ChangeRCA: finding root causes from software changes in large online systems
Yu, G., Chen, P., He, Z., Yan, Q., Luo, Y., Li, F., & Zheng, Z. (2024) · Proceedings of the ACM on Software Engineering · doi:10.1145/3643728 · Cited by 9
syslrn: learning what to monitor for efficient anomaly detection
Sanvito, D., Siracusano, G., Santhanam, S., Gonzalez, R., & Bifulco, R. (2022) · Proceedings of the 2nd European Workshop on Machine Learning and Systems · doi:10.1145/3517207.3526979 · Cited by 4
Metadata
- Authors
- Cotroneo, D., De Simone, L., Liguori, P., Natella, R., & Bidokhti, N.
- Venue
- Proceedings of the 2019 27th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering
- Publisher
- ACM
- Published
- 2019-08-12
- Pages
- 200-211
- OpenAlex
- W2962622685
- Cited by
- 78
- References
- 1
- FWCI
- 6.23
- Type
- conference paper
- Language
- en
- Open access
- green
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: How bad can a bug get? an empirical analysis of software failures in the OpenStack cloud computing platform. https://app.cochat.ai/papers/10.1145/3338906.3338916
- The paper
- Cotroneo, D., De Simone, L., Liguori, P., Natella, R., & Bidokhti, N. (2019). How bad can a bug get? an empirical analysis of software failures in the OpenStack cloud computing platform. Proceedings of the 2019 27th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software Engineering. https://doi.org/10.1145/3338906.3338916
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.