I am running ceph-deploy from node pi00 (admin node), and node pi11,pi12,pi13 are meant to be the nodes running mon and ods.

the global name error is due to a non imported module inside remote/process.py file
adding "from pkgutil import extend_path" solve the issue but another one is trigger just after that.


I also tried to use the ceph-deploy from the official ceph repo ( https://download.ceph.com/rpm-mimic/el7/noarch ) but ceph-deploy 2.0 is not installable due to dependency issues...

I hade the same issue ad I solved upgrading remoto package (0.0.33 -> 0.0.35) using pip:
sudo pip install --upgrade remoto

I hade the same issue ad I solved upgrading ceph-deploy
   
pip install --upgrade ceph-deploy

Does it work with https://bodhi.fedoraproject.org/updates/FEDORA-2019-677e06db0b (an updated python-remoto)?

and if not with that 1.0.0, does it work with 1.1.2 - https://koji.fedoraproject.org/koji/buildinfo?buildID=1239499 ?

https://github.com/alfredodeza/remoto/commit/9f5269600e31f5597d66068e5561fc23e68d405b#diff-851a8bec360fd3d4dbd79c810bb2f64d is probably the fix for this, btw.

I was trying to run ceph-deploy new `hostname -f` on fc29. I found the results below.

python2-remoto-0.0.30-6.fc29.noarch.rpm <--- Works
python2-remoto-0.0.31-2.fc29.noarch.rpm <--- NameError: global name 'extend_path' is not defined
python2-remoto-0.0.33-1.fc29.noarch.rpm <--- NameError: global name 'extend_path' is not defined
python2-remoto-1.0.0-1.fc29.noarch      <--- AttributeError: 'module' object has no attribute 'needs_ssh'
python2-remoto-1.1.2-1.fc29.noarch.rpm  <--- AttributeError: 'module' object has no attribute 'needs_ssh'

(In reply to Nathan G. Grennan from comment #7)
> I was trying to run ceph-deploy new `hostname -f` on fc29. I found the
> results below.
> 
> python2-remoto-0.0.30-6.fc29.noarch.rpm <--- Works
> python2-remoto-0.0.31-2.fc29.noarch.rpm <--- NameError: global name
> 'extend_path' is not defined
> python2-remoto-0.0.33-1.fc29.noarch.rpm <--- NameError: global name
> 'extend_path' is not defined
> python2-remoto-1.0.0-1.fc29.noarch      <--- AttributeError: 'module' object
> has no attribute 'needs_ssh'
> python2-remoto-1.1.2-1.fc29.noarch.rpm  <--- AttributeError: 'module' object
> has no attribute 'needs_ssh'

I changed the /usr/lib/python2.7/site-packages/ceph_deploy/util/ssh.py like that:

#import logging
#from ceph_deploy.lib import remoto
#from ceph_deploy.connection import get_local_connection
#
#
#def can_connect_passwordless(hostname):
#    """
#    Ensure that current host can SSH remotely to the remote
#    host using the ``BatchMode`` option to prevent a password prompt.
#
#    That attempt will error with an exit status of 255 and a ``Permission
#    denied`` message or a``Host key verification failed`` message.
#    """
#    # Ensure we are not doing this for local hosts
#    if not remoto.connection.needs_ssh(hostname):
#        return True
#
#    logger = logging.getLogger(hostname)
#    with get_local_connection(logger) as conn:
#        # Check to see if we can login, disabling password prompts
#        command = ['ssh', '-CT', '-o', 'BatchMode=yes', hostname]
#        out, err, retval = remoto.process.check(conn, command, stop_on_error=False)
#        permission_denied_error = 'Permission denied '
#        host_key_verify_error = 'Host key verification failed.'
#        has_key_error = False
#        for line in err:
#            if permission_denied_error in line or host_key_verify_error in line:
#                has_key_error = True
#
#        if retval == 255 and has_key_error:
#            return False
#    return True
def can_connect_passwordless(hostname): return True

Make sure that You have passwordless ssh access to the nodes, because the code above will not check that at all.
I know it's a silly workaround, but I just need that for testing right now.

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.