Back to bug 2114501
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Mudit Agarwal | 2022-08-03 05:37:34 UTC | CC | kramdoss, muagarwa | |
| Flags | needinfo?(kramdoss) | |||
| gowtham | 2022-08-03 05:52:58 UTC | CC | gshanmug | |
| gowtham | 2022-08-03 05:56:04 UTC | Assignee | nthomas | gshanmug |
| gowtham | 2022-08-03 05:56:15 UTC | Status | NEW | ASSIGNED |
| gowtham | 2022-08-03 08:02:26 UTC | Severity | urgent | medium |
| Mudit Agarwal | 2022-08-03 08:40:16 UTC | Flags | needinfo?(kramdoss) | |
| gowtham | 2022-08-03 09:08:20 UTC | Target Release | --- | ODF 4.12.0 |
| RHEL Program Management | 2022-08-03 09:08:27 UTC | Target Release | ODF 4.12.0 | --- |
| Aman Agrawal | 2022-08-03 09:51:03 UTC | Flags | needinfo?(gshanmug) | |
| Mudit Agarwal | 2022-08-03 10:25:13 UTC | Flags | needinfo?(gshanmug) | |
| Mudit Agarwal | 2022-08-03 13:47:45 UTC | Flags | needinfo?(amagrawa) | |
| gowtham | 2022-08-03 15:35:42 UTC | Assignee | gshanmug | tjeyasin |
| Aman Agrawal | 2022-08-03 18:11:27 UTC | Flags | needinfo?(amagrawa) | |
| Mudit Agarwal | 2022-08-04 07:16:06 UTC | Flags | needinfo?(gshanmug) | |
| Blocks | 2094357 | |||
| Doc Type | If docs needed, set a value | Known Issue | ||
| gowtham | 2022-08-04 10:44:03 UTC | Doc Text | Cause: DRList page is using sync interval value to display the replication type. if it is 0 means it is considering replication type as Sync(synchronous) for the regional clusters. Consequence: The user might confuse, Because the backend is considering Async, and UI is displaying it as Sync. Workaround (if any): Need to fetch Ceph Fsid from DRCluster CR status to decide sync or async Result: |
|
| gowtham | 2022-08-04 10:45:36 UTC | Doc Text | Cause: DRList page is using sync interval value to display the replication type. if it is 0 means it is considering replication type as Sync(synchronous) for the regional clusters. Consequence: The user might confuse, Because the backend is considering Async, and UI is displaying it as Sync. Workaround (if any): Need to fetch Ceph Fsid from DRCluster CR status to decide sync or async Result: | Cause: DRPolicyList page is using sync interval value to display the replication type. if it is 0 means it is considering replication type as Sync(synchronous) for the regional clusters also. Consequence: The user might confuse, Because the backend is considering Async, But UI is showing it as Sync type. Workaround (if any): Need to fetch Ceph Fsid from DRCluster CR status to decide sync or async Result: |
| Olive Lakra | 2022-08-10 15:32:16 UTC | Doc Text | Cause: DRPolicyList page is using sync interval value to display the replication type. if it is 0 means it is considering replication type as Sync(synchronous) for the regional clusters also. Consequence: The user might confuse, Because the backend is considering Async, But UI is showing it as Sync type. Workaround (if any): Need to fetch Ceph Fsid from DRCluster CR status to decide sync or async Result: | * *User is able to set value zero minutes as Sync schedule while creating DR Policy and it reports 'Sync' as Replication policy and gets validated on a Regional-DR setup* + The `DRPolicyList` page uses the `sync` interval value to display the replication type. If it is set to zero then the replication type is considered as Sync(synchronous) for the metro as well as regional clusters. This issue confuses the users because the backend is considering `Async`even when the user interface shows it as `Sync` scheduling type. + Workaround: Need to fetch Ceph Fsid from DRCluster CR status to decide sync or async |
| CC | olakra | |||
| Olive Lakra | 2022-08-18 11:31:06 UTC | Doc Text | * *User is able to set value zero minutes as Sync schedule while creating DR Policy and it reports 'Sync' as Replication policy and gets validated on a Regional-DR setup* + The `DRPolicyList` page uses the `sync` interval value to display the replication type. If it is set to zero then the replication type is considered as Sync(synchronous) for the metro as well as regional clusters. This issue confuses the users because the backend is considering `Async`even when the user interface shows it as `Sync` scheduling type. + Workaround: Need to fetch Ceph Fsid from DRCluster CR status to decide sync or async | .User is able to set value zero minutes as Sync schedule while creating DR Policy and it reports 'Sync' as Replication policy and gets validated on a Regional-DR setup The `DRPolicyList` page uses the `sync` interval value to display the replication type. If it is set to zero then the replication type is considered as Sync(synchronous) for the metro as well as regional clusters. This issue confuses the users because the backend is considering `Async`even when the user interface shows it as `Sync` scheduling type. Workaround: Need to fetch Ceph `Fsid` from DRCluster CR status to decide `sync` or `async`. |
| Olive Lakra | 2022-08-23 13:42:33 UTC | Doc Text | .User is able to set value zero minutes as Sync schedule while creating DR Policy and it reports 'Sync' as Replication policy and gets validated on a Regional-DR setup The `DRPolicyList` page uses the `sync` interval value to display the replication type. If it is set to zero then the replication type is considered as Sync(synchronous) for the metro as well as regional clusters. This issue confuses the users because the backend is considering `Async`even when the user interface shows it as `Sync` scheduling type. Workaround: Need to fetch Ceph `Fsid` from DRCluster CR status to decide `sync` or `async`. | .User is able to set the value to zero minutes as the Sync schedule while creating DR Policy and it reports 'Sync' as Replication policy and gets validated on a Regional-DR setup The `DRPolicyList` page uses the `sync` interval value to display the replication type. If it is set to zero then the replication type is considered as Sync(synchronous) for the metro as well as regional clusters. This issue confuses the users because the backend is considering `Async`even when the user interface shows it as `Sync` scheduling type. Workaround: Need to fetch Ceph `Fsid` from DRCluster CR status to decide `sync` or `async`. |
| gowtham | 2022-08-24 15:14:39 UTC | Assignee | tjeyasin | gshanmug |
| gowtham | 2022-09-27 06:37:12 UTC | Assignee | gshanmug | tjeyasin |
| Mudit Agarwal | 2022-09-29 03:24:34 UTC | Doc Type | Known Issue | Bug Fix |
| Doc Text | .User is able to set the value to zero minutes as the Sync schedule while creating DR Policy and it reports 'Sync' as Replication policy and gets validated on a Regional-DR setup The `DRPolicyList` page uses the `sync` interval value to display the replication type. If it is set to zero then the replication type is considered as Sync(synchronous) for the metro as well as regional clusters. This issue confuses the users because the backend is considering `Async`even when the user interface shows it as `Sync` scheduling type. Workaround: Need to fetch Ceph `Fsid` from DRCluster CR status to decide `sync` or `async`. | |||
| Sanjal Katiyar | 2022-10-11 07:14:38 UTC | Assignee | tjeyasin | skatiyar |
| CC | skatiyar | |||
| Chandan | 2022-10-11 07:17:49 UTC | CC | ckumar | |
| Sanjal Katiyar | 2022-10-14 11:21:27 UTC | Status | ASSIGNED | POST |
| Link ID | Github red-hat-storage/odf-console/pull/493 | |||
| krishnaram Karthick | 2022-10-17 11:00:37 UTC | QA Contact | tdesala | amagrawa |
| RHEL Program Management | 2022-10-17 11:00:48 UTC | Target Release | --- | ODF 4.12.0 |
| OpenShift BugZilla Robot | 2022-10-19 09:25:22 UTC | Link ID | Github red-hat-storage/odf-console/pull/506 | |
| OpenShift BugZilla Robot | 2022-10-19 09:25:23 UTC | Link ID | Github red-hat-storage/odf-console/pull/505 | |
| OpenShift BugZilla Robot | 2022-10-19 12:56:24 UTC | Status | POST | MODIFIED |
| Mudit Agarwal | 2022-10-21 05:21:33 UTC | Fixed In Version | 4.12.0-79 | |
| Status | MODIFIED | ON_QA | ||
| Aman Agrawal | 2022-11-03 13:55:51 UTC | Status | ON_QA | VERIFIED |
| Sunil Kumar Acharya | 2022-12-08 12:55:57 UTC | Flags | needinfo?(skatiyar) | |
| Red Hat Bugzilla | 2022-12-31 20:00:26 UTC | CC | olakra | |
| Red Hat Bugzilla | 2022-12-31 20:04:23 UTC | QA Contact | amagrawa | |
| Red Hat Bugzilla | 2023-01-01 00:45:31 UTC | CC | nthomas | |
| Red Hat Bugzilla | 2023-01-01 05:42:59 UTC | CC | jefbrown | |
| Red Hat Bugzilla | 2023-01-01 08:30:07 UTC | CC | ckumar | |
| Red Hat Bugzilla | 2023-01-01 08:32:37 UTC | CC | kramdoss | |
| Alasdair Kergon | 2023-01-04 04:36:15 UTC | QA Contact | amagrawa | |
| Alasdair Kergon | 2023-01-04 04:51:30 UTC | CC | ckumar | |
| Alasdair Kergon | 2023-01-04 04:59:18 UTC | CC | jefbrown | |
| Alasdair Kergon | 2023-01-04 05:07:00 UTC | CC | kramdoss | |
| Alasdair Kergon | 2023-01-04 05:23:51 UTC | CC | nthomas | |
| Alasdair Kergon | 2023-01-04 05:25:54 UTC | CC | olakra | |
| Erin Donnelly | 2023-01-06 18:43:09 UTC | Flags | needinfo?(amagrawa) | |
| Blocks | 2107226 | |||
| CC | edonnell | |||
| Aman Agrawal | 2023-01-07 15:20:45 UTC | Flags | needinfo?(amagrawa) | needinfo?(skatiyar) |
| Sanjal Katiyar | 2023-01-09 15:31:39 UTC | Flags | needinfo?(skatiyar) needinfo?(skatiyar) | needinfo+ needinfo+ |
| Doc Text | Cause: User was allowed to enter any value for "Sync schedule". Consequence: User was able to add "0" as well for "async" replication policy. Fix: Introduced an number input which will not allow a value lower than 1 Result: It should work correctly now. |
|||
| Sunil Kumar Acharya | 2023-01-09 15:35:57 UTC | CC | sheggodu | |
| Flags | needinfo+ needinfo+ | |||
| Erin Donnelly | 2023-01-12 16:38:07 UTC | Doc Text | Cause: User was allowed to enter any value for "Sync schedule". Consequence: User was able to add "0" as well for "async" replication policy. Fix: Introduced an number input which will not allow a value lower than 1 Result: It should work correctly now. | .`async` replication can no longer be set to `0` Previously, you could enter any value for `Sync schedule`. This meant you could set `async` replication to `0`, which caused an error. With this update, a number input has been introduced that does not allow a value lower than 1. `async` replication now works correctly. |
| Red Hat Bugzilla | 2023-01-31 23:39:14 UTC | CC | madam | |
| Rejy M Cyriac | 2023-02-08 14:06:28 UTC | Resolution | --- | CURRENTRELEASE |
| Status | VERIFIED | CLOSED | ||
| Last Closed | 2023-02-08 14:06:28 UTC | |||
| Elad | 2023-08-09 16:46:41 UTC | CC | odf-bz-bot |
Back to bug 2114501