Description of problem: While creating multi capsules, one capsule failed to start mongodb service. Hence capsule creation failed. But hammer capsule list shows failed capsule ssh -l root vmcapsule191 'capsule-installer --parent-fqdn "perfc-380g8-01.perf.lab.eng.rdu.redhat.com"\ --register-in-foreman "true"\ --foreman-oauth-key "BTbbF8PfPh8vpywsckpY3QajHkPS5Rx9"\ --foreman-oauth-secret "rGrLEh6pz2TTuw7K94G7LN2rGQkAHQsU"\ --pulp-oauth-secret "esn4RwiLMar8YahZy25Xs6LeijuXYv8i"\ --certs-tar "/root/vmcapsule191.perf.lab.eng.rdu.redhat.com-certs.tar"\ --puppet "true"\ --puppetca "true"\ --pulp "true"' snippet of failure ---- [31m Could not start Service[mongodb]: Execution of '/usr/share/katello-installer/modules/service_wait/bin/service-wait start mongod' returned 1: Redirecting to /bin/systemctl start mongod.service [0mError: Could not start Service[mongodb]: Execution: 272/379, 71%, 3.5/s, elapsed: 00:03:06, ETA: 00:00:30 [31m /Stage[main]/Mongodb::Server::Service/Service[mongodb]/ensure: change from stopped to running failed: Could not start Service[mongodb]: Execution of '/usr/share/katello-installer/modules/service_wait/bin/service-wait start mongod' returned 1: Redirecting to /bin/systemctl start mongod.service ----- Ex:As shown in above log, Mongodb failed to start Hence capsule install fails. snippet of error. --- Notice: /Stage[main]/Foreman_proxy::Register/Forem: 378/379, 99%, 0.0/s, elapsed: 00:07:08 Debug: Stored state in 1.11 seconds : 378/379, 99%, 0.0/s, elapsed: 00:07:09 [32mDone [0m: 379/379, 100%, 0.0/s, elapsed: 00:07:16 [32mDone [0m: 379/379, 100%, 0.0/s, elapsed: 00:07:16 [1m[31mSomething went wrong![0m Check the log for ERROR-level output The full log is at [1m[36m/var/log/capsule-installer/capsule-installer.log[0m Build step 'Execute shell' marked build as failure Finished: FAILURE --- In-spite of failure, "hammer capsule list" list this capsule (vmcapsule191) snippet of capsule list: --- 177 | vmcapsule190.perf.lab.eng.rdu.redhat.com | https://vmcapsule190.perf.lab.eng.rdu.redhat.com:9090 178 | vmcapsule191.perf.lab.eng.rdu.redhat.com | https://vmcapsule191.perf.lab.eng.rdu.redhat.com:9090 176 | vmcapsule192.perf.lab.eng.rdu.redhat.com | https://vmcapsule192.perf.lab.eng.rdu.redhat.com:9090 ----- As shown in above list, vmcapsule191 is listed. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Start capsule install. For some reson if mongodb not started, then also its listed. 2. 3. Actual results: capsule should list "hammer capsule list" when specific capsule install failed. Expected results: It shouldnt list when capsule install failed. Additional info:
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.