fb-install-katello.bats.tap

1..14
ok 1 stop puppet agent (if installed)
ok 2 clean after puppet (if installed)
ok 3 make sure puppet not configured to other pm
ok 4 enable haveged (el7 only)
ok 5 run the installer
ok 6 run the installer once again
ok 7 wait 10 seconds
ok 8 check web app is up
ok 9 wake up puppet agent
ok 10 check web app is still up
not ok 11 install CLI (hammer)
# (from function `tPackageInstall' in file os_helper.bash, line 90,
#  in test file fb-install-katello.bats, line 90)
#   `tPackageInstall foreman-cli' failed
# net.ipv6.conf.default.disable_ipv6 = 1
# net.ipv6.conf.all.disable_ipv6 = 1
# Loaded plugins: fastestmirror
# Cleaning repos: base candlepin-koji centos-sclo-rh centos-sclo-sclo epel extras
#               : foreman foreman-plugins katello-client-koji katello-koji
#               : pulp-koji puppetlabs-deps puppetlabs-products updates
# Cleaning up everything
# Cleaning up list of fastest mirrors
# Loaded plugins: fastestmirror
# http://yum.theforeman.org/nightly/el7/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: yum.theforeman.org; Name or service not known"
# Trying other mirror.
# 
# 
#  One of the configured repositories failed (Foreman nightly),
#  and yum doesn't have enough cached data to continue. At this point the only
#  safe thing yum can do is fail. There are a few ways to work "fix" this:
# 
#      1. Contact the upstream for the repository and get them to fix the problem.
# 
#      2. Reconfigure the baseurl/etc. for the repository, to point to a working
#         upstream. This is most often useful if you are using a newer
#         distribution release than is supported by the repository (and the
#         packages for the previous distribution release still work).
# 
#      3. Run the command with the repository temporarily disabled
#             yum --disablerepo=foreman ...
# 
#      4. Disable the repository permanently, so yum won't use it by default. Yum
#         will then just ignore the repository until you permanently enable it
#         again or use --enablerepo for temporary usage:
# 
#             yum-config-manager --disable foreman
#         or
#             subscription-manager repos --disable=foreman
# 
#      5. Configure the failing repository to be skipped, if it is unavailable.
#         Note that yum will try to contact the repo. when it runs most commands,
#         so will have to try and fail each time (and thus. yum will be be much
#         slower). If it is a very temporary problem though, this is often a nice
#         compromise:
# 
#             yum-config-manager --save --setopt=foreman.skip_if_unavailable=true
# 
# failure: repodata/repomd.xml from foreman: [Errno 256] No more mirrors to try.
# http://yum.theforeman.org/nightly/el7/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: yum.theforeman.org; Name or service not known"
ok 12 check smart proxy is registered
ok 13 check host is registered
ok 14 Zzzz.... (120 sec)