Hide Forgot
Created attachment 541115 [details] ss Description of problem: start instances.. go to monitor -> grid view see screenshot [root@dhcp231-79 ~]# rpm -qa | grep aeolus rubygem-arel-2.0.10-0.aeolus.el6.noarch rubygem-aeolus-image-0.2.0-1.el6.noarch rubygem-rack-mount-0.7.1-3.aeolus.el6.noarch aeolus-configure-2.4.0-1.el6.noarch rubygem-aeolus-cli-0.2.0-1.el6.noarch aeolus-conductor-0.7.0-2.el6.noarch aeolus-conductor-doc-0.7.0-2.el6.noarch rubygem-ZenTest-4.3.3-2.aeolus.el6.noarch aeolus-conductor-daemons-0.7.0-2.el6.noarch aeolus-all-0.7.0-2.el6.noarch [root@dhcp231-79 ~]#
Created attachment 541116 [details] ss2
It looks like your one instance is stopped, but in the list view you're filtering on "non-stopped instances". By default we filter out stopped instances -- showing running, pending, and failed. If you change the filter to show 'stopped' instances, you should see the instance in the list -- at least I'm seeing that on the development 'master' branch right now. Let me know if the list is working properly for you when taking the filter into account -- if so this is probably not a bug.
ok.. I'll retest this today.. thanks!
indeed.. that was a mistake.. closing[root@qeblade32 ~]# rpm -qa | grep conductor aeolus-conductor-doc-0.7.0-4.el6.noarch aeolus-conductor-daemons-0.7.0-4.el6.noarch aeolus-conductor-0.7.0-4.el6.noarch