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.

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

dscreate should be more verbose #4875

Closed
mreynolds389 opened this issue Aug 16, 2021 · 1 comment
Closed

dscreate should be more verbose #4875

mreynolds389 opened this issue Aug 16, 2021 · 1 comment
Assignees
Labels
CLI CLI tools lib389 Involves lib389 librabry
Milestone

Comments

@mreynolds389
Copy link
Contributor

Issue Description

dscreate can sometimes stall, or hang. It would be nice to know that it's making progress, and at what stage it is in. Right now it more or less just says "starting" and "finished". Adding just a few of the installer steps to the output would be nice.

@mreynolds389 mreynolds389 added the needs triage The issue will be triaged during scrum label Aug 16, 2021
@mreynolds389 mreynolds389 self-assigned this Aug 25, 2021
mreynolds389 added a commit to mreynolds389/389-ds-base that referenced this issue Aug 26, 2021
Description:  Previously the installer would basically say
              "Starting" and "Finished".  If a step would
              run into a problem it is difficult to narrow
              down what is going wrong.  So add a little more
              output during the installation.

relates: 389ds#4875

Reviewed by: firstyear & spichugi(Thanks!!)
mreynolds389 added a commit that referenced this issue Aug 26, 2021
Description:  Previously the installer would basically say
              "Starting" and "Finished".  If a step would
              run into a problem it is difficult to narrow
              down what is going wrong.  So add a little more
              output during the installation.

relates: #4875

Reviewed by: firstyear & spichugi(Thanks!!)
mreynolds389 added a commit that referenced this issue Aug 26, 2021
Description:  Previously the installer would basically say
              "Starting" and "Finished".  If a step would
              run into a problem it is difficult to narrow
              down what is going wrong.  So add a little more
              output during the installation.

relates: #4875

Reviewed by: firstyear & spichugi(Thanks!!)
mreynolds389 added a commit that referenced this issue Aug 26, 2021
Description:  Previously the installer would basically say
              "Starting" and "Finished".  If a step would
              run into a problem it is difficult to narrow
              down what is going wrong.  So add a little more
              output during the installation.

relates: #4875

Reviewed by: firstyear & spichugi(Thanks!!)
mreynolds389 added a commit that referenced this issue Aug 26, 2021
Description:  Previously the installer would basically say
              "Starting" and "Finished".  If a step would
              run into a problem it is difficult to narrow
              down what is going wrong.  So add a little more
              output during the installation.

relates: #4875

Reviewed by: firstyear & spichugi(Thanks!!)
@mreynolds389
Copy link
Contributor Author

6e21d41..d86a6a8 389-ds-base-2.0 -> 389-ds-base-2.0
38e1e26..a91c1f5 389-ds-base-1.4.4 -> 389-ds-base-1.4.4
a9c4884..234d78d 389-ds-base-1.4.3 -> 389-ds-base-1.4.3

@mreynolds389 mreynolds389 added this to the 1.4.3 milestone Aug 26, 2021
@mreynolds389 mreynolds389 added CLI CLI tools lib389 Involves lib389 librabry and removed needs triage The issue will be triaged during scrum labels Aug 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLI CLI tools lib389 Involves lib389 librabry
Projects
None yet
Development

No branches or pull requests

1 participant