Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve error handling when replica has not been initialized #5789

Closed
mreynolds389 opened this issue Jun 5, 2023 · 1 comment
Closed

Improve error handling when replica has not been initialized #5789

mreynolds389 opened this issue Jun 5, 2023 · 1 comment
Assignees
@mreynolds389
Labels
needs triage The issue will be triaged during scrum

Comments

@mreynolds389
Copy link
Contributor

Issue Description

When a replica has not been initialized we get odd/vague errors in the logs and by ds-replcheck, making it hard to understand what is wrong. We can improve the logging and CLI tools to better handle these situations

See also:
@mreynolds389 mreynolds389 added the needs triage The issue will be triaged during scrum label Jun 5, 2023
@mreynolds389 mreynolds389 self-assigned this Jun 5, 2023
@mreynolds389 mreynolds389 changed the title Improve error handling when replica has not been initialized yet Improve error handling when replica has not been initialized Jun 5, 2023
@mreynolds389 mreynolds389 mentioned this issue Jun 6, 2023
Merged
mreynolds389 added a commit to mreynolds389/389-ds-base that referenced this issue Jun 8, 2023
@mreynolds389
Issue 5789 - Improve ds-replcheck error handling
6073d28 
Description:  When replication is not fully configured the tool outputs vague
              messages.  These should be cleaned up to indicate that
              replication was not initialized.  Also added healthcheck.

Relates: 389ds#5789

Reviewed by: tbordaz, spichugi, progier (Thanks!!!)
mreynolds389 added a commit that referenced this issue Jun 8, 2023
@mreynolds389
Issue 5789 - Improve ds-replcheck error handling
a30a9e0 
Description:  When replication is not fully configured the tool outputs vague
              messages.  These should be cleaned up to indicate that
              replication was not initialized.  Also added healthcheck.

Relates: #5789

Reviewed by: tbordaz, spichugi, progier (Thanks!!!)
mreynolds389 added a commit that referenced this issue Jun 8, 2023
@mreynolds389
Issue 5789 - Improve ds-replcheck error handling
8a40743 
Description:  When replication is not fully configured the tool outputs vague
              messages.  These should be cleaned up to indicate that
              replication was not initialized.  Also added healthcheck.

Relates: #5789

Reviewed by: tbordaz, spichugi, progier (Thanks!!!)
mreynolds389 added a commit that referenced this issue Jun 8, 2023
@mreynolds389
Issue 5789 - Improve ds-replcheck error handling
b7ed55e 
Description:  When replication is not fully configured the tool outputs vague
              messages.  These should be cleaned up to indicate that
              replication was not initialized.  Also added healthcheck.

Relates: #5789

Reviewed by: tbordaz, spichugi, progier (Thanks!!!)
mreynolds389 added a commit that referenced this issue Jun 8, 2023
@mreynolds389
Issue 5789 - Improve ds-replcheck error handling
498debf 
Description:  When replication is not fully configured the tool outputs vague
              messages.  These should be cleaned up to indicate that
              replication was not initialized.  Also added healthcheck.

Relates: #5789

Reviewed by: tbordaz, spichugi, progier (Thanks!!!)
mreynolds389 added a commit that referenced this issue Jun 8, 2023
@mreynolds389
Issue 5789 - Improve ds-replcheck error handling
f8622f6 
Description:  When replication is not fully configured the tool outputs vague
              messages.  These should be cleaned up to indicate that
              replication was not initialized.  Also added healthcheck.

Relates: #5789

Reviewed by: tbordaz, spichugi, progier (Thanks!!!)
mreynolds389 added a commit that referenced this issue Jun 8, 2023
@mreynolds389
Issue 5789 - Improve ds-replcheck error handling
4c16b43 
Description:  When replication is not fully configured the tool outputs vague
              messages.  These should be cleaned up to indicate that
              replication was not initialized.  Also added healthcheck.

Relates: #5789

Reviewed by: tbordaz, spichugi, progier (Thanks!!!)
@mreynolds389
Copy link
Contributor Author

5f9b4d6..8a40743 389-ds-base-2.3 -> 389-ds-base-2.3
1eeaedf..b7ed55e 389-ds-base-2.2 -> 389-ds-base-2.2
b4865f1..498debf 389-ds-base-2.1 -> 389-ds-base-2.1
c0b8a21..f8622f6 389-ds-base-2.0 -> 389-ds-base-2.0
468c4f0..4c16b43 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

lab-at-nohl pushed a commit to lab-at-nohl/cockpit-389-ds-containerproxy that referenced this issue May 9, 2024
@mreynolds389
Issue 5789 - Improve ds-replcheck error handling
2d1490b 
Description:  When replication is not fully configured the tool outputs vague
              messages.  These should be cleaned up to indicate that
              replication was not initialized.  Also added healthcheck.

Relates: 389ds/389-ds-base#5789

Reviewed by: tbordaz, spichugi, progier (Thanks!!!)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mreynolds389 mreynolds389

Labels
needs triage The issue will be triaged during scrum
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mreynolds389