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

stderr and stdstatus is never correctly reported while running startscript #482

Closed
kmathur2 opened this issue May 19, 2021 · 0 comments · Fixed by #483
Closed

stderr and stdstatus is never correctly reported while running startscript #482

kmathur2 opened this issue May 19, 2021 · 0 comments · Fixed by #483
Assignees
@kmathur2
Labels
Priority: Blocker

Comments

@kmathur2
Copy link
Member

I think in the pursuit of fixing the stdout to go to /opt/guestconfig/configure.stdout, we broke configure.stderr and configure.status due to which member status never correctly reports config errors. We need to fix the appPrepConfigRunCmd to correctly report all 3 configure.stdout, configure.stderr and configure.status.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kmathur2 kmathur2

Labels
Priority: Blocker
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix appPrepConfigRunCmd to report stderr and status kmathur2/kubedirector
1 participant
@kmathur2