Created attachment 706316 [details] cc.log nc.log console.log Description of problem: euca-get-console-output does not show the console output of an instance running on the cloud. It is hung forever and has to be manually killed by doing Ctrl+C Version-Release number of selected component (if applicable): python-eucadmin-3.2.1-2.fc18.noarch eucalyptus-gl-3.2.1-2.fc18.x86_64 eucalyptus-3.2.1-2.fc18.x86_64 eucalyptus-admin-tools-3.2.1-2.fc18.noarch eucalyptus-nc-3.2.1-2.fc18.x86_64 euca2ools-2.1.3-1.fc18.noarch eucalyptus-walrus-3.2.1-2.fc18.x86_64 eucalyptus-common-java-3.2.1-2.fc18.x86_64 eucalyptus-sc-3.2.1-2.fc18.x86_64 eucalyptus-cc-3.2.1-2.fc18.x86_64 eucalyptus-cloud-3.2.1-2.fc18.x86_64 eucalyptus-axis2-clients-3.2.1-2.fc18.x86_64 eucalyptus-console-3.2.1-2.fc18.x86_64 How reproducible: The steps to reproduce the problem are given below Steps to Reproduce: 1. Run an instance on the cloud , wait for it to go into running state 2. Run euca-get-console-output <instance id> Actual results: Command is hung , doing nothing, has to be killed manually by doing Ctrl+C Expected results: Console output for the instance specified should be shown on the terminal Additional info: The following is observed on the NCs nc.log 2013-03-06 18:26:30 DEBUG 000014184 doDescribeInstances | [i-F0C641FA] Extant pub=10.104.3.50 priv=192.168.33.232 mac=D0:0D:F0:C6:41:FA vlan=137 net=40 plat=linux vols=vol-4B1B4325:A 2013-03-06 18:26:35 INFO 000014286 doGetConsoleOutput | [i-F0C641FA] console output requested 2013-03-06 18:26:35 ERROR 000014286 doGetConsoleOutput | [i-F0C641FA] cannot locate instance 2013-03-06 18:26:35 ERROR 000014286 ncGetConsoleOutputMarsha | [i-F0C641FA] failed error=1 So the NC believes the instance is not running? But just before that it was able to describeInstance it. One strange thing that happens is euca-get-console-output <instance ID> --debug works, without any problem and expected output is shown with some other debug level output from the command. Attaching cc.log , nc.log and console output from --debug for reference. Please let me know if there are any questions. Cheers! Deependra
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.