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

Rundeck execution follow UI splits single steps into multiple sections #347

Closed
andysteady opened this issue Apr 2, 2013 · 10 comments
Closed
Assignees
Labels
Milestone

Comments

@andysteady
Copy link

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.
Screenshot from 2013-04-02 22:59:37

@gschueler
Copy link
Member

this might be a problem capturing stderr output perhaps?

would you mind sending me the log file (.txt) from this kind of execution? thanks

@andysteady
Copy link
Author

Do you mean the rundeck.log?

@gschueler
Copy link
Member

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

@andysteady
Copy link
Author

Ah, right - sure, I have sent this to you in a private email. Cheers.

@gschueler
Copy link
Member

I see, it looks like the node context is not recorded for those odd lines,
which appear to be at a different log level. I think they are coming from
stderr.

So i think this bug has to do with stderr output not keeping the right Node
context information when record in the logs.

On Tue, Apr 9, 2013 at 12:37 PM, Andy Steady [email protected]:

Ah, right - sure, I have sent this to you in a private email. Cheers.


Reply to this email directly or view it on GitHubhttps://github.com//issues/347#issuecomment-16135111
.

@ghost ghost assigned gschueler Apr 9, 2013
@andysteady
Copy link
Author

Seems logical and explains why this is also seen when doing wgets.
Its strange how common, defacto tools such as apt-get and wget seem to send some progress information to stderr.
Anyway, if possible, I would like to vote for this issue :)

@andysteady
Copy link
Author

Hi,
Has there been any progress on this one? I'd be happy to help test it.
Cheers,
Andy

@gschueler
Copy link
Member

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]:

Hi,
Has there been any progress on this one? I'd be happy to help test it.
Cheers,
Andy


Reply to this email directly or view it on GitHubhttps://github.com//issues/347#issuecomment-17680489
.

@gschueler
Copy link
Member

simple test script described in #195

@gschueler
Copy link
Member

need to verify fixed in 1.6-dev

gschueler added a commit that referenced this issue Aug 2, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants