* Package:    app-admin/github-backup-utils-2.11.2-r1
 * Repository: gentoo
 * Maintainer: wizardedit@gentoo.org williamh@gentoo.org
 * USE:        abi_x86_64 amd64 elibc_glibc kernel_linux test userland_GNU
 * FEATURES:   network-sandbox preserve-libs sandbox test userpriv usersandbox
>>> Unpacking source...
>>> Unpacking github-backup-utils-2.11.2.tar.gz to /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work
>>> Source unpacked in /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work
>>> Preparing source in /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2 ...
 * Applying github-backup-utils-tarball-fix.patch ...
 [ ok ]
 * Applying github-backup-utils-python27.patch ...
 [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2 ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2 ...
>>> Source compiled.
>>> Test phase: app-admin/github-backup-utils-2.11.2-r1
make -j 1 test 
This is github/backup-utils
rsync  version 3.1.3  protocol version 31

==> Running testsuite with GHE_TEST_REMOTE_VERSION=11.10.344
test: ghe-backup-config GHE_DATA_DIR defined ...                   OK
test: ghe-backup-config GHE_CREATE_DATA_DIR disabled ...           OK
test: ghe-backup-config run on GHE appliance ...                   OK
test: ghe-backup-config ssh_host_part ...                          OK
test: ghe-backup-config ssh_port_part ...                          OK
test: ghe-backup-config ghe_parse_remote_version v11.10.x series ... OK
warning: unable to access '/root/config/git/attributes': Permission denied
warning: unable to access '/root/config/git/attributes': Permission denied
test: ghe-backup-config ghe_parse_remote_version v2.x series ...   OK
test: ghe-detect-leaked-ssh-keys check -h displays help message ... OK
test: ghe-detect-leaked-ssh-keys clean snapshot test, no messages ... OK
test: ghe-detect-leaked-ssh-keys leaked keys in current backup ... OK
test: ghe-detect-leaked-ssh-keys leaked keys in old snapshot ...   OK
test: ghe-backup-repositories-rsync first snapshot ...             OK
test: ghe-host-check ...                                           OK
test: ghe-backup-repositories-rsync first snapshot (nw) ...        OK
test: ghe-host-check with host arg ...                             OK
test: ghe-prune-snapshots using default GHE_NUM_SNAPSHOTS ...      OK
test: ghe-prune-snapshots non-numeric GHE_NUM_SNAPSHOTS ...        OK
test: ghe-prune-snapshots with no expired snapshots ...            OK
test: ghe-backup-repositories-rsync subsequent snapshot ...        OK
test: ghe-prune-snapshots with expired snapshots ...               OK
test: ghe-prune-snapshots incomplete snapshot pruning ...          OK
test: ghe-backup-repositories-rsync subsequent snapshot (nw) ...   OK
test: ghe-backup-repositories-rsync __special__ dirs ...           OK
test: ghe-backup-repositories-rsync temp files (nw) ...            OK
test: ghe-ssh simple command works ...                             OK
test: ghe-ssh complex command works ...                            OK
test: ghe-ssh when complex command given to simple form ...        OK
test: ghe-backup first snapshot ...                                OK
test: ghe-backup-repositories-rsync temp files ...                 OK
test: ghe-restore into configured vm ...                           OK
test: ghe-restore logs the benchmark ...                           OK
test: ghe-restore aborts without user verification ...             OK
test: ghe-backup subsequent snapshot ...                           OK
test: ghe-restore accepts user verification ...                    OK
test: ghe-restore -c into unconfigured vm ...                      OK
test: ghe-restore into unconfigured vm ...                         OK
test: ghe-backup logs the benchmark ...                            OK
test: ghe-restore with host arg ...                                OK
test: ghe-restore no host arg or configured restore host ...       OK
test: ghe-restore with no pages backup ...                         OK
test: ghe-restore with tarball strategy ...                        OK
test: ghe-backup with relative data dir path ...                   OK
test: ghe-restore with empty uuid file ...                         OK
test: ghe-restore with no uuid file ...                            OK
test: ghe-restore cluster backup to non-cluster appliance ...      OK
test: ghe-restore no leaked ssh host keys detected ...             OK
test: ghe-backup tarball strategy ...                              OK
test: ghe-backup fails fast when old style run in progress ...     OK
test: ghe-restore with current backup leaked key detection ... ...              FAILED
    + set -e
    + cat
    + tar -cf /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16099/data/current/ssh-host-keys.tar --directory=/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16099/data ssh_host_dsa_key.pub
    +++ which ghe-detect-leaked-ssh-keys
    ++ dirname /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/share/github-backup-utils/ghe-detect-leaked-ssh-keys
    + SHARED_UTILS_PATH=/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/share/github-backup-utils
    + echo 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60
    ++ ghe-restore -v -f localhost
    + exec ssh -p 22 -o ControlMaster=auto -o 'ControlPath="/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/.ghe-sshmux-60ea0191"' -o ControlPersist=10m -o ServerAliveInterval=10 -l admin -o BatchMode=yes localhost -- '[ -f '\''/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16099/remote/data/enterprise/dna.json'\'' -o        -f '\''/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16099/remote/etc/github/configured'\'' ]'
    + exec ssh -p 22 -o ControlMaster=auto -o 'ControlPath="/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/.ghe-sshmux-60ea0191"' -o ControlPersist=10m -o ServerAliveInterval=10 -l admin -o BatchMode=yes localhost -- '[ -f '\''/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16099/remote/etc/github/cluster'\'' ]'
    Error: Snapshot from a GitHub Enterprise cluster cannot be restored to a standalone appliance. Aborting.
    + output='Checking for leaked keys in the backup snapshot that is being restored ...
    * Leaked key found in current backup snapshot.
    * Snapshot file: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16099/data/1/ssh-host-keys.tar
    * Key file: ssh_host_dsa_key.pub
    * Key: 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60
    
    * The current backup contains leaked SSH host keys.
    * Current backup directory: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16099/data/1
    * We strongly recommend rolling your SSH host keys and making a new backup.
    * Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance.
    * (An upgrade may be required)
    
    * One or more older backup snapshots contain leaked SSH host keys.
    * No immediate action is needed but when you use one of these older snapshots for a restore, 
    * please make sure to roll the SSH host keys after restore.
    * Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance.
    * (An upgrade may be required)
    
    Connect localhost:22 OK (v11.10.344)'
    + true
    + echo 'fake ghe-export-ssh-host-keys data'
    + grep -q 'Leaked key found in current backup snapshot'
    + echo Checking for leaked keys in the backup snapshot that is being restored ... alice bob Leaked key found in current backup snapshot. alice bob Snapshot file: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16099/data/1/ssh-host-keys.tar alice bob Key file: ssh_host_dsa_key.pub alice bob Key: 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60 alice bob The current backup contains leaked SSH host keys. alice bob Current backup directory: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16099/data/1 alice bob We strongly recommend rolling your SSH host keys and making a new backup. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' alice bob One or more older backup snapshots contain leaked SSH host keys. alice bob No immediate action is needed but when you use one of these older snapshots for a restore, alice bob please make sure to roll the SSH host keys after restore. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' Connect localhost:22 OK '(v11.10.344)'
    + grep -q 'The snapshot that is being restored contains a leaked SSH host key.'
    + echo Checking for leaked keys in the backup snapshot that is being restored ... alice bob Leaked key found in current backup snapshot. alice bob Snapshot file: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16099/data/1/ssh-host-keys.tar alice bob Key file: ssh_host_dsa_key.pub alice bob Key: 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60 alice bob The current backup contains leaked SSH host keys. alice bob Current backup directory: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16099/data/1 alice bob We strongly recommend rolling your SSH host keys and making a new backup. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' alice bob One or more older backup snapshots contain leaked SSH host keys. alice bob No immediate action is needed but when you use one of these older snapshots for a restore, alice bob please make sure to roll the SSH host keys after restore. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' Connect localhost:22 OK '(v11.10.344)'
    test failed. last command exited with 1
test: ghe-restore fails when restore to an active HA pair ...      OK
test: ghe-restore fails when restore 2.9/2.10 snapshot without audit log migration sentinel file to 2.11 ... OK
test: ghe-restore force restore of 2.9/2.10 snapshot without audit log migration sentinel file to 2.11 ... OK
test: ghe-backup cleans up stale in-progress file ...              OK
test: ghe-backup without manage-password file ...                  OK
test: ghe-backup empty hookshot directory ...                      OK
test: ghe-backup empty git-hooks directory ...                     OK
test: ghe-backup fsck ...                                          OK
test: ghe-backup stores version when not run from a clone ...      OK
test: ghe-backup with leaked SSH host key detection for current backup ... OK
test: ghe-backup with no leaked keys ...                           OK

==> Running testsuite with GHE_TEST_REMOTE_VERSION=2.0.0
test: ghe-backup-config GHE_DATA_DIR defined ...                   OK
test: ghe-backup-config GHE_CREATE_DATA_DIR disabled ...           OK
warning: unable to access '/root/config/git/attributes': Permission denied
test: ghe-backup-config run on GHE appliance ...                   OK
test: ghe-backup-config ssh_host_part ...                          OK
test: ghe-backup-config ssh_port_part ...                          OK
warning: unable to access '/root/config/git/attributes': Permission denied
test: ghe-backup-config ghe_parse_remote_version v11.10.x series ... OK
test: ghe-backup-config ghe_parse_remote_version v2.x series ...   OK
test: ghe-detect-leaked-ssh-keys check -h displays help message ... OK
test: ghe-detect-leaked-ssh-keys clean snapshot test, no messages ... OK
test: ghe-detect-leaked-ssh-keys leaked keys in current backup ... OK
test: ghe-detect-leaked-ssh-keys leaked keys in old snapshot ...   OK
test: ghe-backup-repositories-rsync first snapshot ...             OK
test: ghe-backup-repositories-rsync first snapshot (nw) ...        OK
test: ghe-host-check ...                                           OK
test: ghe-host-check with host arg ...                             OK
test: ghe-prune-snapshots using default GHE_NUM_SNAPSHOTS ...      OK
test: ghe-prune-snapshots non-numeric GHE_NUM_SNAPSHOTS ...        OK
test: ghe-backup-repositories-rsync subsequent snapshot ...        OK
test: ghe-prune-snapshots with no expired snapshots ...            OK
test: ghe-backup-repositories-rsync subsequent snapshot (nw) ...   OK
test: ghe-prune-snapshots with expired snapshots ...               OK
test: ghe-prune-snapshots incomplete snapshot pruning ...          OK
test: ghe-backup-repositories-rsync __special__ dirs ...           OK
test: ghe-backup-repositories-rsync temp files (nw) ...            OK
test: ghe-ssh simple command works ...                             OK
test: ghe-ssh complex command works ...                            OK
test: ghe-ssh when complex command given to simple form ...        OK
test: ghe-backup-repositories-rsync temp files ...                 OK
test: ghe-backup first snapshot ...                                OK
test: ghe-restore into configured vm ...                           OK
test: ghe-restore logs the benchmark ...                           OK
test: ghe-restore aborts without user verification ...             OK
test: ghe-backup subsequent snapshot ...                           OK
test: ghe-restore accepts user verification ...                    OK
test: ghe-backup logs the benchmark ...                            OK
test: ghe-restore -c into unconfigured vm ...                      OK
test: ghe-restore into unconfigured vm ...                         OK
test: ghe-backup with relative data dir path ...                   OK
test: ghe-restore with host arg ...                                OK
test: ghe-restore no host arg or configured restore host ...       OK
test: ghe-backup tarball strategy ...                              OK
test: ghe-backup fails fast when old style run in progress ...     OK
test: ghe-restore with no pages backup ...                         OK
test: ghe-restore with tarball strategy ...                        OK
test: ghe-backup cleans up stale in-progress file ...              OK
test: ghe-restore with empty uuid file ...                         OK
test: ghe-restore with no uuid file ...                            OK
test: ghe-restore cluster backup to non-cluster appliance ...      OK
test: ghe-backup without manage-password file ...                  OK
test: ghe-restore no leaked ssh host keys detected ...             OK
test: ghe-restore with current backup leaked key detection ... ...              FAILED
    + set -e
    + cat
    + tar -cf /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-22371/data/current/ssh-host-keys.tar --directory=/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-22371/data ssh_host_dsa_key.pub
    +++ which ghe-detect-leaked-ssh-keys
    ++ dirname /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/share/github-backup-utils/ghe-detect-leaked-ssh-keys
    + SHARED_UTILS_PATH=/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/share/github-backup-utils
    + echo 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60
    ++ ghe-restore -v -f localhost
    + exec ssh -p 22 -o ControlMaster=auto -o 'ControlPath="/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/.ghe-sshmux-60ea0191"' -o ControlPersist=10m -o ServerAliveInterval=10 -l admin -o BatchMode=yes localhost -- '[ -f '\''/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-22371/remote/data/enterprise/dna.json'\'' -o        -f '\''/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-22371/remote/etc/github/configured'\'' ]'
    + exec ssh -p 22 -o ControlMaster=auto -o 'ControlPath="/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/.ghe-sshmux-60ea0191"' -o ControlPersist=10m -o ServerAliveInterval=10 -l admin -o BatchMode=yes localhost -- '[ -f '\''/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-22371/remote/etc/github/cluster'\'' ]'
    Error: Snapshot from a GitHub Enterprise cluster cannot be restored to a standalone appliance. Aborting.
    + output='Checking for leaked keys in the backup snapshot that is being restored ...
    * Leaked key found in current backup snapshot.
    * Snapshot file: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-22371/data/1/ssh-host-keys.tar
    * Key file: ssh_host_dsa_key.pub
    * Key: 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60
    
    * The current backup contains leaked SSH host keys.
    * Current backup directory: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-22371/data/1
    * We strongly recommend rolling your SSH host keys and making a new backup.
    * Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance.
    * (An upgrade may be required)
    
    * One or more older backup snapshots contain leaked SSH host keys.
    * No immediate action is needed but when you use one of these older snapshots for a restore, 
    * please make sure to roll the SSH host keys after restore.
    * Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance.
    * (An upgrade may be required)
    
    Connect localhost:22 OK (v2.0.0)'
    + true
    + echo 'fake ghe-export-ssh-host-keys data'
    + grep -q 'Leaked key found in current backup snapshot'
    + echo Checking for leaked keys in the backup snapshot that is being restored ... alice bob Leaked key found in current backup snapshot. alice bob Snapshot file: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-22371/data/1/ssh-host-keys.tar alice bob Key file: ssh_host_dsa_key.pub alice bob Key: 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60 alice bob The current backup contains leaked SSH host keys. alice bob Current backup directory: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-22371/data/1 alice bob We strongly recommend rolling your SSH host keys and making a new backup. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' alice bob One or more older backup snapshots contain leaked SSH host keys. alice bob No immediate action is needed but when you use one of these older snapshots for a restore, alice bob please make sure to roll the SSH host keys after restore. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' Connect localhost:22 OK '(v2.0.0)'
    + grep -q 'The snapshot that is being restored contains a leaked SSH host key.'
    + echo Checking for leaked keys in the backup snapshot that is being restored ... alice bob Leaked key found in current backup snapshot. alice bob Snapshot file: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-22371/data/1/ssh-host-keys.tar alice bob Key file: ssh_host_dsa_key.pub alice bob Key: 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60 alice bob The current backup contains leaked SSH host keys. alice bob Current backup directory: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-22371/data/1 alice bob We strongly recommend rolling your SSH host keys and making a new backup. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' alice bob One or more older backup snapshots contain leaked SSH host keys. alice bob No immediate action is needed but when you use one of these older snapshots for a restore, alice bob please make sure to roll the SSH host keys after restore. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' Connect localhost:22 OK '(v2.0.0)'
    test failed. last command exited with 1
test: ghe-restore fails when restore to an active HA pair ...      OK
test: ghe-restore fails when restore 2.9/2.10 snapshot without audit log migration sentinel file to 2.11 ... OK
test: ghe-restore force restore of 2.9/2.10 snapshot without audit log migration sentinel file to 2.11 ... OK
test: ghe-backup empty hookshot directory ...                      OK
test: ghe-backup empty git-hooks directory ...                     OK
test: ghe-backup fsck ...                                          OK
test: ghe-backup stores version when not run from a clone ...      OK
test: ghe-backup with leaked SSH host key detection for current backup ... OK
test: ghe-backup with no leaked keys ...                           OK

==> Running testsuite with GHE_TEST_REMOTE_VERSION=2.2.0
test: ghe-backup-config GHE_DATA_DIR defined ...                   OK
test: ghe-backup-config GHE_CREATE_DATA_DIR disabled ...           OK
warning: unable to access '/root/config/git/attributes': Permission denied
test: ghe-backup-config run on GHE appliance ...                   OK
test: ghe-backup-config ssh_host_part ...                          OK
test: ghe-backup-config ssh_port_part ...                          OK
warning: unable to access '/root/config/git/attributes': Permission denied
test: ghe-backup-config ghe_parse_remote_version v11.10.x series ... OK
test: ghe-backup-config ghe_parse_remote_version v2.x series ...   OK
test: ghe-detect-leaked-ssh-keys check -h displays help message ... OK
test: ghe-detect-leaked-ssh-keys clean snapshot test, no messages ... OK
test: ghe-detect-leaked-ssh-keys leaked keys in current backup ... OK
test: ghe-detect-leaked-ssh-keys leaked keys in old snapshot ...   OK
test: ghe-backup-repositories-rsync first snapshot ...             OK
test: ghe-backup-repositories-rsync first snapshot (nw) ...        OK
test: ghe-host-check ...                                           OK
test: ghe-host-check with host arg ...                             OK
test: ghe-backup-repositories-rsync subsequent snapshot ...        OK
test: ghe-prune-snapshots using default GHE_NUM_SNAPSHOTS ...      OK
test: ghe-prune-snapshots non-numeric GHE_NUM_SNAPSHOTS ...        OK
test: ghe-prune-snapshots with no expired snapshots ...            OK
test: ghe-prune-snapshots with expired snapshots ...               OK
test: ghe-backup-repositories-rsync subsequent snapshot (nw) ...   OK
test: ghe-prune-snapshots incomplete snapshot pruning ...          OK
test: ghe-backup-repositories-rsync __special__ dirs ...           OK
test: ghe-backup-repositories-rsync temp files (nw) ...            OK
test: ghe-ssh simple command works ...                             OK
test: ghe-ssh complex command works ...                            OK
test: ghe-ssh when complex command given to simple form ...        OK
test: ghe-backup-repositories-rsync temp files ...                 OK
test: ghe-backup first snapshot ...                                OK
test: ghe-restore into configured vm ...                           OK
test: ghe-restore logs the benchmark ...                           OK
test: ghe-restore aborts without user verification ...             OK
test: ghe-backup subsequent snapshot ...                           OK
test: ghe-restore accepts user verification ...                    OK
test: ghe-backup logs the benchmark ...                            OK
test: ghe-restore -c into unconfigured vm ...                      OK
test: ghe-restore into unconfigured vm ...                         OK
test: ghe-backup with relative data dir path ...                   OK
test: ghe-restore with host arg ...                                OK
test: ghe-restore no host arg or configured restore host ...       OK
test: ghe-backup tarball strategy ...                              OK
test: ghe-backup fails fast when old style run in progress ...     OK
test: ghe-restore with no pages backup ...                         OK
test: ghe-restore with tarball strategy ...                        OK
test: ghe-backup cleans up stale in-progress file ...              OK
test: ghe-restore with empty uuid file ...                         OK
test: ghe-backup without manage-password file ...                  OK
test: ghe-restore with no uuid file ...                            OK
test: ghe-restore cluster backup to non-cluster appliance ...      OK
test: ghe-restore no leaked ssh host keys detected ...             OK
test: ghe-restore with current backup leaked key detection ... ...              FAILED
    + set -e
    + cat
    + tar -cf /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-424/data/current/ssh-host-keys.tar --directory=/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-424/data ssh_host_dsa_key.pub
    +++ which ghe-detect-leaked-ssh-keys
    ++ dirname /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/share/github-backup-utils/ghe-detect-leaked-ssh-keys
    + SHARED_UTILS_PATH=/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/share/github-backup-utils
    + echo 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60
    ++ ghe-restore -v -f localhost
    + exec ssh -p 22 -o ControlMaster=auto -o 'ControlPath="/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/.ghe-sshmux-60ea0191"' -o ControlPersist=10m -o ServerAliveInterval=10 -l admin -o BatchMode=yes localhost -- '[ -f '\''/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-424/remote/data/enterprise/dna.json'\'' -o        -f '\''/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-424/remote/etc/github/configured'\'' ]'
    + exec ssh -p 22 -o ControlMaster=auto -o 'ControlPath="/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/.ghe-sshmux-60ea0191"' -o ControlPersist=10m -o ServerAliveInterval=10 -l admin -o BatchMode=yes localhost -- '[ -f '\''/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-424/remote/etc/github/cluster'\'' ]'
    Error: Snapshot from a GitHub Enterprise cluster cannot be restored to a standalone appliance. Aborting.
    + output='Checking for leaked keys in the backup snapshot that is being restored ...
    * Leaked key found in current backup snapshot.
    * Snapshot file: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-424/data/1/ssh-host-keys.tar
    * Key file: ssh_host_dsa_key.pub
    * Key: 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60
    
    * The current backup contains leaked SSH host keys.
    * Current backup directory: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-424/data/1
    * We strongly recommend rolling your SSH host keys and making a new backup.
    * Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance.
    * (An upgrade may be required)
    
    * One or more older backup snapshots contain leaked SSH host keys.
    * No immediate action is needed but when you use one of these older snapshots for a restore, 
    * please make sure to roll the SSH host keys after restore.
    * Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance.
    * (An upgrade may be required)
    
    Connect localhost:22 OK (v2.2.0)'
    + true
    + echo 'fake ghe-export-ssh-host-keys data'
    + echo Checking for leaked keys in the backup snapshot that is being restored ... alice bob Leaked key found in current backup snapshot. alice bob Snapshot file: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-424/data/1/ssh-host-keys.tar alice bob Key file: ssh_host_dsa_key.pub alice bob Key: 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60 alice bob The current backup contains leaked SSH host keys. alice bob Current backup directory: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-424/data/1 alice bob We strongly recommend rolling your SSH host keys and making a new backup. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' alice bob One or more older backup snapshots contain leaked SSH host keys. alice bob No immediate action is needed but when you use one of these older snapshots for a restore, alice bob please make sure to roll the SSH host keys after restore. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' Connect localhost:22 OK '(v2.2.0)'
    + grep -q 'Leaked key found in current backup snapshot'
    + echo Checking for leaked keys in the backup snapshot that is being restored ... alice bob Leaked key found in current backup snapshot. alice bob Snapshot file: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-424/data/1/ssh-host-keys.tar alice bob Key file: ssh_host_dsa_key.pub alice bob Key: 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60 alice bob The current backup contains leaked SSH host keys. alice bob Current backup directory: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-424/data/1 alice bob We strongly recommend rolling your SSH host keys and making a new backup. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' alice bob One or more older backup snapshots contain leaked SSH host keys. alice bob No immediate action is needed but when you use one of these older snapshots for a restore, alice bob please make sure to roll the SSH host keys after restore. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' Connect localhost:22 OK '(v2.2.0)'
    + grep -q 'The snapshot that is being restored contains a leaked SSH host key.'
    test failed. last command exited with 1
test: ghe-restore fails when restore to an active HA pair ...      OK
test: ghe-restore fails when restore 2.9/2.10 snapshot without audit log migration sentinel file to 2.11 ... OK
test: ghe-restore force restore of 2.9/2.10 snapshot without audit log migration sentinel file to 2.11 ... OK
test: ghe-backup empty hookshot directory ...                      OK
test: ghe-backup empty git-hooks directory ...                     OK
test: ghe-backup fsck ...                                          OK
test: ghe-backup stores version when not run from a clone ...      OK
test: ghe-backup with leaked SSH host key detection for current backup ... OK
test: ghe-backup with no leaked keys ...                           OK

==> Running testsuite with GHE_TEST_REMOTE_VERSION=2.5.0
test: ghe-backup-config GHE_DATA_DIR defined ...                   OK
warning: unable to access '/root/config/git/attributes': Permission denied
test: ghe-backup-config GHE_CREATE_DATA_DIR disabled ...           OK
test: ghe-backup-config run on GHE appliance ...                   OK
test: ghe-backup-config ssh_host_part ...                          OK
test: ghe-backup-config ssh_port_part ...                          OK
warning: unable to access '/root/config/git/attributes': Permission denied
test: ghe-backup-config ghe_parse_remote_version v11.10.x series ... OK
test: ghe-backup-config ghe_parse_remote_version v2.x series ...   OK
test: ghe-detect-leaked-ssh-keys check -h displays help message ... OK
test: ghe-detect-leaked-ssh-keys clean snapshot test, no messages ... OK
test: ghe-detect-leaked-ssh-keys leaked keys in current backup ... OK
test: ghe-detect-leaked-ssh-keys leaked keys in old snapshot ...   OK
test: ghe-backup-repositories-rsync first snapshot ...             OK
test: ghe-backup-repositories-rsync first snapshot (nw) ...        OK
test: ghe-host-check ...                                           OK
test: ghe-host-check with host arg ...                             OK
test: ghe-prune-snapshots using default GHE_NUM_SNAPSHOTS ...      OK
test: ghe-prune-snapshots non-numeric GHE_NUM_SNAPSHOTS ...        OK
test: ghe-prune-snapshots with no expired snapshots ...            OK
test: ghe-backup-repositories-rsync subsequent snapshot ...        OK
test: ghe-prune-snapshots with expired snapshots ...               OK
test: ghe-backup-repositories-rsync subsequent snapshot (nw) ...   OK
test: ghe-prune-snapshots incomplete snapshot pruning ...          OK
test: ghe-backup-repositories-rsync __special__ dirs ...           OK
test: ghe-backup-repositories-rsync temp files (nw) ...            OK
test: ghe-ssh simple command works ...                             OK
test: ghe-ssh complex command works ...                            OK
test: ghe-ssh when complex command given to simple form ...        OK
test: ghe-backup-repositories-rsync temp files ...                 OK
test: ghe-backup first snapshot ...                                OK
test: ghe-restore into configured vm ...                           OK
test: ghe-restore logs the benchmark ...                           OK
test: ghe-restore aborts without user verification ...             OK
test: ghe-backup subsequent snapshot ...                           OK
test: ghe-restore accepts user verification ...                    OK
test: ghe-backup logs the benchmark ...                            OK
test: ghe-restore -c into unconfigured vm ...                      OK
test: ghe-restore into unconfigured vm ...                         OK
test: ghe-backup with relative data dir path ...                   OK
test: ghe-restore with host arg ...                                OK
test: ghe-restore no host arg or configured restore host ...       OK
test: ghe-backup tarball strategy ...                              OK
test: ghe-backup fails fast when old style run in progress ...     OK
test: ghe-restore with no pages backup ...                         OK
test: ghe-restore with tarball strategy ...                        OK
test: ghe-backup cleans up stale in-progress file ...              OK
test: ghe-restore with empty uuid file ...                         OK
test: ghe-restore with no uuid file ...                            OK
test: ghe-restore cluster backup to non-cluster appliance ...      OK
test: ghe-backup without manage-password file ...                  OK
test: ghe-restore no leaked ssh host keys detected ...             OK
test: ghe-restore with current backup leaked key detection ... ...              FAILED
    + set -e
    + cat
    + tar -cf /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16608/data/current/ssh-host-keys.tar --directory=/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16608/data ssh_host_dsa_key.pub
    +++ which ghe-detect-leaked-ssh-keys
    ++ dirname /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/share/github-backup-utils/ghe-detect-leaked-ssh-keys
    + SHARED_UTILS_PATH=/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/share/github-backup-utils
    + echo 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60
    ++ ghe-restore -v -f localhost
    + exec ssh -p 22 -o ControlMaster=auto -o 'ControlPath="/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/.ghe-sshmux-60ea0191"' -o ControlPersist=10m -o ServerAliveInterval=10 -l admin -o BatchMode=yes localhost -- '[ -f '\''/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16608/remote/data/enterprise/dna.json'\'' -o        -f '\''/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16608/remote/etc/github/configured'\'' ]'
    + exec ssh -p 22 -o ControlMaster=auto -o 'ControlPath="/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/.ghe-sshmux-60ea0191"' -o ControlPersist=10m -o ServerAliveInterval=10 -l admin -o BatchMode=yes localhost -- '[ -f '\''/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16608/remote/etc/github/cluster'\'' ]'
    Error: Snapshot from a GitHub Enterprise cluster cannot be restored to a standalone appliance. Aborting.
    + output='Checking for leaked keys in the backup snapshot that is being restored ...
    * Leaked key found in current backup snapshot.
    * Snapshot file: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16608/data/1/ssh-host-keys.tar
    * Key file: ssh_host_dsa_key.pub
    * Key: 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60
    
    * The current backup contains leaked SSH host keys.
    * Current backup directory: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16608/data/1
    * We strongly recommend rolling your SSH host keys and making a new backup.
    * Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance.
    * (An upgrade may be required)
    
    * One or more older backup snapshots contain leaked SSH host keys.
    * No immediate action is needed but when you use one of these older snapshots for a restore, 
    * please make sure to roll the SSH host keys after restore.
    * Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance.
    * (An upgrade may be required)
    
    Connect localhost:22 OK (v2.5.0)'
    + true
    + echo 'fake ghe-export-ssh-host-keys data'
    + grep -q 'Leaked key found in current backup snapshot'
    + echo Checking for leaked keys in the backup snapshot that is being restored ... alice bob Leaked key found in current backup snapshot. alice bob Snapshot file: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16608/data/1/ssh-host-keys.tar alice bob Key file: ssh_host_dsa_key.pub alice bob Key: 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60 alice bob The current backup contains leaked SSH host keys. alice bob Current backup directory: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16608/data/1 alice bob We strongly recommend rolling your SSH host keys and making a new backup. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' alice bob One or more older backup snapshots contain leaked SSH host keys. alice bob No immediate action is needed but when you use one of these older snapshots for a restore, alice bob please make sure to roll the SSH host keys after restore. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' Connect localhost:22 OK '(v2.5.0)'
    + echo Checking for leaked keys in the backup snapshot that is being restored ... alice bob Leaked key found in current backup snapshot. alice bob Snapshot file: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16608/data/1/ssh-host-keys.tar alice bob Key file: ssh_host_dsa_key.pub alice bob Key: 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60 alice bob The current backup contains leaked SSH host keys. alice bob Current backup directory: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-16608/data/1 alice bob We strongly recommend rolling your SSH host keys and making a new backup. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' alice bob One or more older backup snapshots contain leaked SSH host keys. alice bob No immediate action is needed but when you use one of these older snapshots for a restore, alice bob please make sure to roll the SSH host keys after restore. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' Connect localhost:22 OK '(v2.5.0)'
    + grep -q 'The snapshot that is being restored contains a leaked SSH host key.'
    test failed. last command exited with 1
test: ghe-restore fails when restore to an active HA pair ...      OK
test: ghe-restore fails when restore 2.9/2.10 snapshot without audit log migration sentinel file to 2.11 ... OK
test: ghe-restore force restore of 2.9/2.10 snapshot without audit log migration sentinel file to 2.11 ... OK
test: ghe-backup empty hookshot directory ...                      OK
test: ghe-backup empty git-hooks directory ...                     OK
test: ghe-backup fsck ...                                          OK
test: ghe-backup stores version when not run from a clone ...      OK
test: ghe-backup with leaked SSH host key detection for current backup ... OK
test: ghe-backup with no leaked keys ...                           OK

==> Running testsuite with GHE_TEST_REMOTE_VERSION=2.11.0
test: ghe-backup-config GHE_DATA_DIR defined ...                   OK
test: ghe-backup-config GHE_CREATE_DATA_DIR disabled ...           OK
warning: unable to access '/root/config/git/attributes': Permission denied
test: ghe-backup-config run on GHE appliance ...                   OK
test: ghe-backup-config ssh_host_part ...                          OK
test: ghe-backup-config ssh_port_part ...                          OK
warning: unable to access '/root/config/git/attributes': Permission denied
test: ghe-backup-config ghe_parse_remote_version v11.10.x series ... OK
test: ghe-backup-config ghe_parse_remote_version v2.x series ...   OK
test: ghe-detect-leaked-ssh-keys check -h displays help message ... OK
test: ghe-detect-leaked-ssh-keys clean snapshot test, no messages ... OK
test: ghe-detect-leaked-ssh-keys leaked keys in current backup ... OK
test: ghe-detect-leaked-ssh-keys leaked keys in old snapshot ...   OK
test: ghe-backup-repositories-rsync first snapshot ...             OK
test: ghe-backup-repositories-rsync first snapshot (nw) ...        OK
test: ghe-host-check ...                                           OK
test: ghe-host-check with host arg ...                             OK
test: ghe-prune-snapshots using default GHE_NUM_SNAPSHOTS ...      OK
test: ghe-prune-snapshots non-numeric GHE_NUM_SNAPSHOTS ...        OK
test: ghe-backup-repositories-rsync subsequent snapshot ...        OK
test: ghe-prune-snapshots with no expired snapshots ...            OK
test: ghe-backup-repositories-rsync subsequent snapshot (nw) ...   OK
test: ghe-prune-snapshots with expired snapshots ...               OK
test: ghe-prune-snapshots incomplete snapshot pruning ...          OK
test: ghe-backup-repositories-rsync __special__ dirs ...           OK
test: ghe-backup-repositories-rsync temp files (nw) ...            OK
test: ghe-ssh simple command works ...                             OK
test: ghe-ssh complex command works ...                            OK
test: ghe-ssh when complex command given to simple form ...        OK
test: ghe-backup-repositories-rsync temp files ...                 OK
test: ghe-backup first snapshot ...                                OK
test: ghe-restore into configured vm ...                           OK
test: ghe-restore logs the benchmark ...                           OK
test: ghe-restore aborts without user verification ...             OK
test: ghe-backup subsequent snapshot ...                           OK
test: ghe-restore accepts user verification ...                    OK
test: ghe-backup logs the benchmark ...                            OK
test: ghe-restore -c into unconfigured vm ...                      OK
test: ghe-restore into unconfigured vm ...                         OK
test: ghe-backup with relative data dir path ...                   OK
test: ghe-restore with host arg ...                                OK
test: ghe-restore no host arg or configured restore host ...       OK
test: ghe-backup tarball strategy ...                              OK
test: ghe-backup fails fast when old style run in progress ...     OK
test: ghe-restore with no pages backup ...                         OK
test: ghe-restore with tarball strategy ...                        OK
test: ghe-backup cleans up stale in-progress file ...              OK
test: ghe-restore with empty uuid file ...                         OK
test: ghe-restore with no uuid file ...                            OK
test: ghe-restore cluster backup to non-cluster appliance ...      OK
test: ghe-backup without manage-password file ...                  OK
test: ghe-restore no leaked ssh host keys detected ...             OK
test: ghe-restore with current backup leaked key detection ... ...              FAILED
    + set -e
    + cat
    + tar -cf /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-5610/data/current/ssh-host-keys.tar --directory=/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-5610/data ssh_host_dsa_key.pub
    +++ which ghe-detect-leaked-ssh-keys
    ++ dirname /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/share/github-backup-utils/ghe-detect-leaked-ssh-keys
    + SHARED_UTILS_PATH=/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/share/github-backup-utils
    + echo 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60
    ++ ghe-restore -v -f localhost
    + exec ssh -p 22 -o ControlMaster=auto -o 'ControlPath="/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/.ghe-sshmux-60ea0191"' -o ControlPersist=10m -o ServerAliveInterval=10 -l admin -o BatchMode=yes localhost -- '[ -f '\''/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-5610/remote/data/enterprise/dna.json'\'' -o        -f '\''/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-5610/remote/etc/github/configured'\'' ]'
    + exec ssh -p 22 -o ControlMaster=auto -o 'ControlPath="/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/.ghe-sshmux-60ea0191"' -o ControlPersist=10m -o ServerAliveInterval=10 -l admin -o BatchMode=yes localhost -- '[ -f '\''/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-5610/remote/etc/github/cluster'\'' ]'
    Error: Snapshot from a GitHub Enterprise cluster cannot be restored to a standalone appliance. Aborting.
    + output='Checking for leaked keys in the backup snapshot that is being restored ...
    * Leaked key found in current backup snapshot.
    * Snapshot file: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-5610/data/1/ssh-host-keys.tar
    * Key file: ssh_host_dsa_key.pub
    * Key: 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60
    
    * The current backup contains leaked SSH host keys.
    * Current backup directory: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-5610/data/1
    * We strongly recommend rolling your SSH host keys and making a new backup.
    * Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance.
    * (An upgrade may be required)
    
    * One or more older backup snapshots contain leaked SSH host keys.
    * No immediate action is needed but when you use one of these older snapshots for a restore, 
    * please make sure to roll the SSH host keys after restore.
    * Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance.
    * (An upgrade may be required)
    
    Connect localhost:22 OK (v2.11.0)'
    + true
    + echo 'fake ghe-export-ssh-host-keys data'
    + echo Checking for leaked keys in the backup snapshot that is being restored ... alice bob Leaked key found in current backup snapshot. alice bob Snapshot file: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-5610/data/1/ssh-host-keys.tar alice bob Key file: ssh_host_dsa_key.pub alice bob Key: 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60 alice bob The current backup contains leaked SSH host keys. alice bob Current backup directory: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-5610/data/1 alice bob We strongly recommend rolling your SSH host keys and making a new backup. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' alice bob One or more older backup snapshots contain leaked SSH host keys. alice bob No immediate action is needed but when you use one of these older snapshots for a restore, alice bob please make sure to roll the SSH host keys after restore. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' Connect localhost:22 OK '(v2.11.0)'
    + grep -q 'Leaked key found in current backup snapshot'
    + grep -q 'The snapshot that is being restored contains a leaked SSH host key.'
    + echo Checking for leaked keys in the backup snapshot that is being restored ... alice bob Leaked key found in current backup snapshot. alice bob Snapshot file: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-5610/data/1/ssh-host-keys.tar alice bob Key file: ssh_host_dsa_key.pub alice bob Key: 98:d8:99:d3:be:c0:55:05:db:b0:53:2f:1f:ad:b3:60 alice bob The current backup contains leaked SSH host keys. alice bob Current backup directory: /var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2/test/tmp/test-ghe-restore.sh-5610/data/1 alice bob We strongly recommend rolling your SSH host keys and making a new backup. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' alice bob One or more older backup snapshots contain leaked SSH host keys. alice bob No immediate action is needed but when you use one of these older snapshots for a restore, alice bob please make sure to roll the SSH host keys after restore. alice bob Roll the keys either manually or with ghe-ssh-roll-host-keys on the appliance. alice bob '(An' upgrade may be 'required)' Connect localhost:22 OK '(v2.11.0)'
    test failed. last command exited with 1
test: ghe-restore fails when restore to an active HA pair ...      OK
test: ghe-restore fails when restore 2.9/2.10 snapshot without audit log migration sentinel file to 2.11 ... OK
test: ghe-backup empty hookshot directory ...                      OK
test: ghe-restore force restore of 2.9/2.10 snapshot without audit log migration sentinel file to 2.11 ... OK
test: ghe-backup empty git-hooks directory ...                     OK
test: ghe-backup fsck ...                                          OK
test: ghe-backup stores version when not run from a clone ...      OK
test: ghe-backup with leaked SSH host key detection for current backup ... OK
test: ghe-backup with no leaked keys ...                           OK

make: *** [Makefile:4: test] Error 1
 * ERROR: app-admin/github-backup-utils-2.11.2-r1::gentoo failed (test phase):
 *   emake failed
 * 
 * If you need support, post the output of `emerge --info '=app-admin/github-backup-utils-2.11.2-r1::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=app-admin/github-backup-utils-2.11.2-r1::gentoo'`.
 * The complete build log is located at '/var/log/portage/app-admin:github-backup-utils-2.11.2-r1:20180402-182744.log'.
 * For convenience, a symlink to the build log is located at '/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/temp/environment'.
 * Working directory: '/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2'
 * S: '/var/tmp/portage/app-admin/github-backup-utils-2.11.2-r1/work/backup-utils-2.11.2'