Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: [root@dell-pe1950-02 templates]# service iwhd stop [ OK ] iwhd daemon: [ OK ] Expected results: It should display: [root@dell-pe1950-02 templates]# service iwhd stop Stopping iwhd daemon: [ OK ] Additional info: [root@dell-pe1950-02 templates]# rpm -qa | grep iwhd iwhd-0.98.15.z3-2.el6.x86_64
ERROR: TargetImageNotFound => Could not find TargetImage all [root@qeblade30 ce]# /etc/init.d/iwhd stop [ OK ] iwhd daemon: [ OK ] [root@qeblade30 ce]# /etc/init.d/iwhd start waiting for mongod to listen on localhost:27017[ OK ] Starting iwhd daemon: [ OK ] [root@qeblade30 ce]# rpm -q iwhd iwhd-1.2-3.el6.x86_64 [root@qeblade30 ce]#
So, what, this is a regression? Wes?
Wes, which RHEL version have you used ? [root@qeblade22 ~]# /etc/init.d/iwhd stop Stopping iwhd daemon: [ OK ] [root@qeblade22 ~]# /etc/init.d/iwhd start waiting for mongod to listen on localhost:27017 [ OK ] Starting iwhd daemon: [ OK ] [root@qeblade22 ~]# rpm -q iwhd iwhd-1.1-2.el6.x86_64
adding ce-sprint-next bugs to ce-sprint
This issue is still reproducible. [root@hp-bl480c-01 ~]# service iwhd stop [ OK ] iwhd daemon: [ OK ] [root@hp-bl480c-01 ~]# /etc/init.d/iwhd stop [ OK ] iwhd daemon: [ OK ] # rpm -qa | grep iwhd iwhd-1.2-3.el6.x86_64 # cat /etc/issue Red Hat Enterprise Linux Server release 6.1 (Santiago) #rpm -qa | grep aeolus aeolus-conductor-0.8.0-8.el6.noarch rubygem-aeolus-cli-0.3.0-4.el6.noarch aeolus-configure-2.5.0-5.el6.noarch aeolus-conductor-daemons-0.8.0-8.el6.noarch rubygem-aeolus-image-0.3.0-3.el6.noarch aeolus-all-0.8.0-8.el6.noarch aeolus-conductor-doc-0.8.0-8.el6.noarch
(In reply to comment #6) > This issue is still reproducible. > > [root@hp-bl480c-01 ~]# service iwhd stop > [ OK ] iwhd daemon: [ OK ] > > [root@hp-bl480c-01 ~]# /etc/init.d/iwhd stop > [ OK ] iwhd daemon: [ OK ] > > # rpm -qa | grep iwhd > iwhd-1.2-3.el6.x86_64 Hi Aziza (or anyone who can reproduce), Thanks for the report. However, so far, I am unable to reproduce that. I.e., I always see this: $ service mongod start Starting mongod: [ OK ] $ service iwhd start; service iwhd stop waiting for mongod to listen on localhost:27017 [ OK ] Starting iwhd daemon: [ OK ] Stopping iwhd daemon: [ OK ] If you can still reproduce it, please tell me what type of terminal emulator you are using and what "echo $TERM" prints. FTR, I'm using roxterm and TERM is xterm-256color. Oh, and your shell. I've tried with both zsh and bash. Also, assuming you can still reproduce the problem, please run the "service iwhd stop" under "script" so I can see what ANSI terminal escapes the init script is generating for you. I.e., run "script", then run your "service iwhd stop" command, then hit Control-D and attach the "typescript" log file that it has just created.
This looks like we need a retest.
Test passed (http://hudson.rhq.lab.eng.bos.redhat.com:8080/hudson/user/koca/my-views/view/All/job/ImageFactory-KocaTesting2/351/console). I'm not able to reproduce. #rpm -qa | grep 'aeolus\|imagefactory-\|oz-\|iwhd' aeolus-conductor-0.13.2-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch iwhd-1.5-2.el6.x86_64 imagefactory-1.0.0rc11-1v11candidate3.el6cf.noarch imagefactory-jeosconf-ec2-fedora-1.0.0rc11-1v11candidate3.el6cf.noarch imagefactory-jeosconf-ec2-rhel-1.0.0rc11-1v11candidate3.el6cf.noarch aeolus-conductor-doc-0.13.2-1.el6cf.noarch aeolus-all-0.13.2-1.el6cf.noarch aeolus-configure-2.8.2-1.el6cf.noarch rubygem-aeolus-cli-0.3.3-1.el6_3.noarch oz-0.8.0-6.el6cf.noarch aeolus-conductor-daemons-0.13.2-1.el6cf.noarch Finished: SUCCESS I will keep trying to reproduce it and if I'm not success I will move bug to VERIFIED.
As another data point, I can repro this problem: >> service iwhd start; service iwhd stop waiting for mongod to listen on localhost:27017[ OK ] Starting iwhd daemon: [ OK ] [ OK ] iwhd daemon: [ OK ] >> [root@qeblade39 nodes]# service iwhd start;/etc/init.d/iwhd stop waiting for mongod to listen on localhost:27017[ OK ] Starting iwhd daemon: [ OK ] [ OK ] iwhd daemon: [ OK ] rpms tested: >> rpm -qa |grep aeolus aeolus-configure-2.8.6-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch rubygem-aeolus-cli-0.7.1-1.el6cf.noarch aeolus-conductor-0.13.8-1.el6cf.noarch aeolus-conductor-daemons-0.13.8-1.el6cf.noarch aeolus-conductor-doc-0.13.8-1.el6cf.noarch aeolus-all-0.13.8-1.el6cf.noarch >> rpm -qa |grep iwh iwhd-1.5-2.el6.x86_64
I am also able to reproduce the issue Attaching o/p of commands requested by Jim at comment 7 service iwhd stop [ OK ] iwhd daemon: [ OK ] echo $TERM xterm attached typescript file observed on the host :ibm-dx360m4-01.rhts.eng.bos.redhat.com rpm -qa | grep aeolus aeolus-conductor-doc-0.13.14-1.el6cf.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-all-0.13.14-1.el6cf.noarch aeolus-conductor-0.13.14-1.el6cf.noarch rubygem-aeolus-cli-0.7.2-1.el6cf.noarch aeolus-configure-2.8.7-1.el6cf.noarch aeolus-conductor-daemons-0.13.14-1.el6cf.noarch [root@ibm-dx360m4-01 home]# rpm -qa | grep iwhd iwhd-1.5-2.el6.x86_64
Created attachment 618502 [details] typescript
Thanks, Rehana, I am unable to reproduce that using an xterm, TERM=xterm on F17, so it is probably F16-specific. I've also just verified that it works properly on RHEL 6.3. Considering how much has changed with start/stop and initscripts since then, and that F16 is not going to be a reasonable portability target for long (we're in F18 alpha), I am tempted to say this can be closed with something like "NO LONGER MATTERS". However, if this is an issue with RHEL6, then maybe it does matter, even though it's just a formatting glitch.
I'm reproducing this, connecting from F17 using both screen and xterm, to a RHEL6.3 host [root@qeblade22 ~]# echo $TERM xterm [root@qeblade22 ~]# service iwhd restart [ OK ] iwhd daemon: [ OK ] waiting for mongod to listen on localhost:27017[ OK ] Starting iwhd daemon: [ OK ] [root@qeblade22 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.3 (Santiago)
I missed to mention that the observation was made on Rhel6.2 machine observed on the host :ibm-dx360m4-01.rhts.eng.bos.redhat.com
Closing this out, triage meeting declares this isn;t worth the any effort and iwhd is going away in the near future