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

Issue with running knife job output --channel stdout on chef-client v14 #62

Open
muntaserq opened this issue May 1, 2018 · 3 comments
Open

Issue with running knife job output --channel stdout on chef-client v14 #62

muntaserq opened this issue May 1, 2018 · 3 comments
Labels
Type: Bug Doesn't work as expected.

Comments

@muntaserq
Copy link

muntaserq commented May 1, 2018 •
edited
Loading

We have upgrade to chef-client 14.0.190 and knife job output is failing on the following error:

knife job output --channel stdout $jobId $node
knife : ERROR: The object you are looking for could not be found
At S:\Sourcecode\****\*****\******\........
 ...       $standardError = knife job output --channel stderr $jobId $node
     CategoryInfo          : NotSpecified: (ERROR: The obje...ld not be found:String) [], RemoteException
     FullyQualifiedErrorId : NativeCommandError
 
Response: <HTML><HEAD><TITLE>404 Not Found</TITLE></HEAD><BODY><H1>Not Found</H1>The requested document was not found on this 
server.<P><HR><ADDRESS>mochiweb+webmachine web server</ADDRESS></BODY></HTML>

Has anything changed in this command? We are sure the jobId is correct.
@anniehedgpeth
Copy link

anniehedgpeth commented May 2, 2018 •
edited
Loading

(@muntaserq and I are working on the same project.)

Is it possible that knife-push needs to be updated with Chef 14?

knife job output gives us a 404 from the API on our nodes that we updated to Chef 14.0.190, but it's fine when we downgrade back to 12.18.31.

chef-server 12.10.0
push-jobs-client_2.1.4

@teknofire
Copy link

Just as a follow up, we investigated this some more on the client node and it turns out that the output was not being sent to the chef server because the output size was too large. The only indication that this was happening was a single entry in the push-jobs client logs that stated: Command output too long. Will not be sent to server.

This is the check that is happening https://github.com/chef/opscode-pushy-client/blob/master/lib/pushy_client/protocol_handler.rb#L421-L424

@tas50 tas50 added the Type: Bug Doesn't work as expected. label Dec 22, 2018
@voroniys
Copy link

voroniys commented May 1, 2019

I have the same issue. And this is quite serious issue as it makes push jobs unusable, since most of the commands produce output bigger, than max output size.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type: Bug Doesn't work as expected.
Milestone
No milestone
Development

No branches or pull requests
5 participants
@teknofire @tas50 @voroniys @muntaserq @anniehedgpeth