Back to bug 2130450

Who When What Removed Added
Kotresh HR 2022-09-28 07:37:15 UTC Status NEW ASSIGNED
Target Release 5.3z1 6.0
Kotresh HR 2022-09-28 07:55:07 UTC Assignee vshankar khiremat
Red Hat One Jira (issues.redhat.com) 2022-09-28 08:23:20 UTC Link ID Red Hat Issue Tracker RHCEPH-5374
Veera Raghava Reddy 2022-10-02 20:14:22 UTC CC tserlin
Flags needinfo?(khiremat)
Flags needinfo?(hyelloji)
Flags needinfo?(vereddy)
CC hyelloji, vereddy
Flags needinfo?(hyelloji) needinfo?(vereddy)
Hemanth Kumar 2022-10-03 05:37:23 UTC QA Contact hyelloji amk
Kotresh HR 2022-10-03 07:56:35 UTC Status ASSIGNED POST
Flags needinfo?(khiremat)
Veera Raghava Reddy 2022-10-03 15:01:13 UTC Status POST MODIFIED
Fixed In Version ceph-17.2.3-45.el9cp
CC amk
Flags needinfo?(amk)
Flags needinfo?(amk)
errata-xmlrpc 2022-10-03 15:03:03 UTC Status MODIFIED ON_QA
Masauso Lungu 2022-10-05 08:44:42 UTC Blocks 2126050
CC mlungu
Flags needinfo?(khiremat)
Docs Contact mlungu
Pasi Karkkainen 2022-10-05 09:01:18 UTC CC pasik
Masauso Lungu 2022-10-05 18:16:52 UTC Blocks 2126050
Amarnath 2022-10-06 03:07:20 UTC Status ON_QA ASSIGNED
Kotresh HR 2022-10-06 11:11:35 UTC Flags needinfo?(khiremat)
Masauso Lungu 2022-10-07 08:39:22 UTC Flags needinfo?(khiremat)
Masauso Lungu 2022-10-10 21:18:37 UTC Flags needinfo?(khiremat)
Kotresh HR 2022-10-11 10:16:27 UTC Flags needinfo?(khiremat) needinfo?(khiremat)
Doc Type If docs needed, set a value Bug Fix
Doc Text Cause:
The config file is being written directly without using the temporary file. This involved truncating the existing config file and writing the config data.

Consequence:
When the disk is full, this leads to empty config file as the truncate is successful but writing new config data fails with no space error. This would lead to the failure of all the operations on corresponding subvolume.

Fix:
The config data is written to temporary config file and renamed to original config file. This would avoid truncating the original config file.

Result:
The disk full scenarios doesn't corrupt the config file.
Masauso Lungu 2022-10-11 10:46:01 UTC Blocks 2126050
Masauso Lungu 2022-10-16 23:08:39 UTC Flags needinfo?(khiremat)
Doc Text Cause:
The config file is being written directly without using the temporary file. This involved truncating the existing config file and writing the config data.

Consequence:
When the disk is full, this leads to empty config file as the truncate is successful but writing new config data fails with no space error. This would lead to the failure of all the operations on corresponding subvolume.

Fix:
The config data is written to temporary config file and renamed to original config file. This would avoid truncating the original config file.

Result:
The disk full scenarios doesn't corrupt the config file.
.The disk full scenario does not corrupt the configuration file anymore

Previously, the configuration files were being written directly to the disk without using the temporary files, which involved truncating the existing configuration file and writing the configuration data. This led to the empty configuration files when the disk was full as the truncate was successful, however writing new configuration data failed without `no space` error. Additionally, it led to the failure of all the operations on corresponding subvolumes.

With this fix, the configuration data is written to a temporary configuration file and renamed to the original configuration file and prevents truncating the original configuration file.
Kotresh HR 2022-10-17 09:04:18 UTC Flags needinfo?(khiremat) needinfo?(mlungu)
Masauso Lungu 2022-10-17 15:18:42 UTC Doc Text .The disk full scenario does not corrupt the configuration file anymore

Previously, the configuration files were being written directly to the disk without using the temporary files, which involved truncating the existing configuration file and writing the configuration data. This led to the empty configuration files when the disk was full as the truncate was successful, however writing new configuration data failed without `no space` error. Additionally, it led to the failure of all the operations on corresponding subvolumes.

With this fix, the configuration data is written to a temporary configuration file and renamed to the original configuration file and prevents truncating the original configuration file.
.The disk full scenario does not corrupt the configuration file anymore

Previously, the configuration files were being written directly to the disk without using the temporary files, which involved truncating the existing configuration file and writing the configuration data. This led to the empty configuration files when the disk was full as the truncate was successful, however writing new configuration data failed with `no space` error. Additionally, it led to the failure of all the operations on corresponding subvolumes.

With this fix, the configuration data is written to a temporary configuration file and renamed to the original configuration file and prevents truncating the original configuration file.
Flags needinfo?(mlungu)
Kotresh HR 2022-10-18 09:22:24 UTC Flags needinfo?(amk)
Greg Farnum 2022-10-19 14:12:59 UTC CC gfarnum
Status ASSIGNED MODIFIED
Amarnath 2022-11-02 14:01:37 UTC Status MODIFIED ON_QA
Flags needinfo?(amk)
Status ON_QA VERIFIED
Red Hat Bugzilla 2022-12-31 19:12:20 UTC Assignee khiremat vshankar
Red Hat Bugzilla 2022-12-31 19:50:45 UTC CC hyelloji
Red Hat Bugzilla 2023-01-01 05:39:42 UTC CC tserlin
Red Hat Bugzilla 2023-01-01 08:28:28 UTC CC amk
QA Contact amk
Red Hat Bugzilla 2023-01-01 08:47:24 UTC CC vereddy
Red Hat Bugzilla 2023-01-01 08:49:34 UTC Assignee vshankar nobody
Alasdair Kergon 2023-01-04 04:36:31 UTC QA Contact amk
Alasdair Kergon 2023-01-04 04:42:47 UTC Assignee nobody khiremat
Alasdair Kergon 2023-01-04 04:45:34 UTC CC amk
Alasdair Kergon 2023-01-04 04:57:17 UTC CC hyelloji
Alasdair Kergon 2023-01-04 06:29:04 UTC CC vereddy
Red Hat Bugzilla 2023-01-09 08:29:54 UTC CC ceph-eng-bugs
Alasdair Kergon 2023-01-09 19:43:36 UTC CC ceph-eng-bugs
errata-xmlrpc 2023-03-20 18:58:27 UTC Status VERIFIED CLOSED
Resolution --- ERRATA
Last Closed 2023-03-20 18:58:27 UTC
errata-xmlrpc 2023-03-20 18:59:18 UTC Link ID Red Hat Product Errata RHBA-2023:1360

Back to bug 2130450