-
Notifications
You must be signed in to change notification settings - Fork 928
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
Rundeck execution follow UI splits single steps into multiple sections #347
Comments
this might be a problem capturing stderr output perhaps? would you mind sending me the log file (.txt) from this kind of execution? thanks |
Do you mean the rundeck.log? |
No, i mean the log file for the execution, it should be in RDECK_BASE/var/logs/rundeck/PROJECT/GROUP/JOB/ID.txt , where ID is the execution ID number |
Ah, right - sure, I have sent this to you in a private email. Cheers. |
I see, it looks like the node context is not recorded for those odd lines, So i think this bug has to do with stderr output not keeping the right Node On Tue, Apr 9, 2013 at 12:37 PM, Andy Steady [email protected]:
|
Seems logical and explains why this is also seen when doing wgets. |
Hi, |
Hi Andy, I was able to reproduce the issue, but I have not had a chance to fix it On Thu, May 9, 2013 at 11:21 AM, Andy Steady [email protected]:
|
simple test script described in #195 |
need to verify fixed in 1.6-dev |
When a single step in a job has a lot of output, rundeck splits what should be a single step in the "annotated" view into multiple steps.
The split appears arbitrary.
A good job to try this with is to create a simple job that executes apt-get update on a debian machine as sudo. A screen shot is attached showing the follow screen of a such a job. Note in the picture that each annotation heading is for the same job step.
The text was updated successfully, but these errors were encountered: