[
https://issues.apache.org/jira/browse/VCL-609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430472#comment-13430472
]
Andy Kurth commented on VCL-609:
--------------------------------
Yes, the first error looks like the one I encountered except the exit status
was 1 or 2 for me if I recall correctly. I encountered this on an XP image I
tried to load on a fresh 2.3 install last week. I don't think it was hitting
run_ssh_command, but the local command on the management node was returning a
non-zero status. I'm not sure why. There was no error in the output and the
cat command succeeded. The reservation failed because it was hitting the
'return;' line below before looping through the output:
# Retrieve the contents of /etc/hosts using cat
my ($exit_status, $output) = run_command('cat /etc/hosts', 1);
if (defined $exit_status && $exit_status == 0) {
notify($ERRORS{'DEBUG'}, 0, "retrieved contents of /etc/hosts on this
management node, contains " . scalar @$output . " lines");
}
elsif (defined $exit_status) {
notify($ERRORS{'WARNING'}, 0, "failed to cat /etc/hosts on this management
node, exit status: $exit_status, output:\n" . join("\n", @$output));
return;
}
> Reservations fail if cat command returns non-zero exit status when retrieving
> contents of /etc/hosts on management node
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: VCL-609
> URL: https://issues.apache.org/jira/browse/VCL-609
> Project: VCL
> Issue Type: Bug
> Components: vcld (backend)
> Affects Versions: 2.3
> Reporter: Andy Kurth
> Assignee: Andy Kurth
> Priority: Minor
> Fix For: 2.3.1
>
>
> The get_computer_private_ip_address subroutine in Datastructure.pm retrieves
> the contents of /etc/hosts on the management node using the cat command.
> Occasionally this command returns a non-zero exit status even though the
> contents were retrieved causing the subroutine to return null unnecessarily.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
