Created attachment 1034674 [details] capsule-installer log attached Description of problem: Cannot setup capsule using capsule-installer in snap7 Version-Release number of selected component (if applicable): # rpm -qa | grep foreman foreman-compute-1.7.2.26-1.el6_6sat.noarch ruby193-rubygem-foreman-redhat_access-0.1.0-1.el6_6sat.noarch rubygem-hammer_cli_foreman-0.1.4.13-1.el6_6sat.noarch foreman-vmware-1.7.2.26-1.el6_6sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el6_6sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch foreman-postgresql-1.7.2.26-1.el6_6sat.noarch foreman-libvirt-1.7.2.26-1.el6_6sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.7-1.el6_6sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el6_6sat.noarch rubygem-hammer_cli_foreman_docker-0.0.3.6-1.el6_6sat.noarch foreman-selinux-1.7.2.13-1.el6_6sat.noarch foreman-debug-1.7.2.26-1.el6_6sat.noarch foreman-ovirt-1.7.2.26-1.el6_6sat.noarch foreman-gce-1.7.2.26-1.el6_6sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.15-1.el6_6sat.noarch foreman-proxy-1.7.2.5-1.el6_6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el6_6sat.noarch intel-s3e3432-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch ruby193-rubygem-foreman_docker-1.2.0.14-1.el6_6sat.noarch intel-s3e3432-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch intel-s3e3432-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch foreman-1.7.2.26-1.el6_6sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el6_6sat.noarch How reproducible: everytime Steps to Reproduce: 1.# capsule-installer --parent-fqdn "intel-s3e3432-01.rhts.eng.bos.redhat.com" --register-in-foreman "true" --foreman-oauth-key "LAhVo8sgFyLQ9CQcgLAHR8cfhgmGdBEc" --foreman-oauth-secret "ng8YqMmZwwrz6SwPrMSKb34q2xsFpWzf" --pulp-oauth-secret "BjhTy9ACrCvHD4PpbdgXSX4M4kDVp37f" --certs-tar "/root/hp-z600-01.rhts.eng.bos.redhat.com-certs.tar" --puppet "true" --puppetca "true" --pulp "true" tar -xzf /root/hp-z600-01.rhts.eng.bos.redhat.com-certs.tar returned 2 instead of one of [0] /Stage[main]/Capsule/Certs::Tar_extract[/root/hp-z600-01.rhts.eng.bos.redhat.com-certs.tar]/Exec[extract /root/hp-z600-01.rhts.eng.bos.redhat.com-certs.tar]/returns: change from notrun to 0 failed: tar -xzf /root/hp-z600-01.rhts.eng.bos.redhat.com-certs.tar returned 2 instead of one of [0] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[hp-z600-01.rhts.eng.bos.redhat.com]: Failed to call refresh: missing param 'id' in parameters /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[hp-z600-01.rhts.eng.bos.redhat.com]: missing param 'id' in parameters Installing Done [100%] [] Something went wrong! Check the log for ERROR-level output The full log is at /var/log/capsule-installer/capsule-installer.log 2. 3. Actual results: setting up capsule failed Expected results: setting up capsule installed successfully Additional info: capsule-installer.log attached
did you create the cert on the parent satellite and then copy it over to the capsule target? There was a bug written up long, long ago that we need to do more validation in installer when there is an issue with finding the cert (if someone fat-fingers, or the cert is missing, etc.), and I suspect this is the case here, but maybe not. Please respond indicating whether you've actually generated the cert on parent satellite and copied it over.
FWIW, I think an error code of "2" in linux generally means "File Not Found" > tar -xzf /root/hp-z600-01.rhts.eng.bos.redhat.com-certs.tar returned 2 instead of one of [0] So I bet the cert isn't there.
Hi, I will setup the capsule again and check throughly whether the certs.tar is copied or not Thanks
Can we close this out? This looks like user error as we are seeing success in later snaps