AtomiX84's questions

We have a NFS client which print in to messages this error:

kernel: nfs: server nfsserver not responding, timed out

it is printed about every minute. Normally I will think there had a communication issue or firewalled ports.

But here what is fun, the mounted NFS share works has expected, we cane R/W from it with the expected bandwidth!

Both server and client are RHEL7 the client mount it with the following mount options:

rw,vers=4.1,user,auto

the timeo and retrans are set to default (600 and 2). We have many clients point to this NFS Server and only one of them get this issue, all client mount the share with the same parameters and comes from different networks.

I need to create a in-memory inventory to run playbook over overcloud instance, all instance are not directly exposed, only one server is exposed and can be used as "gateway" aka "JumpHost" aka "ProxyHost".

I have been accomplish this task whit the following tasks:

Get infos on the server I'm interested

...
  - name: detect gateway for the {{ project }} tenant
    openstack.cloud.server_info:
      cloud: "{{ project }}"
      server: "*gw*"
    register: gw_info
...

Then I extract the information of the FloatingIP associated to this instance:

...
- name: Register info of gateway for {{ project }} tenant
  set_fact:
    gw_ip: "{{ item.interface_ip }}"
  loop: "{{ gw_info.openstack_servers }}"
...

Once I get the infos I need I collect infos to all instances in the tenant

...
- name: fetch instances on {{ project }} tenant
  openstack.cloud.server_info:
    cloud: "{{ project }}"
  register: servers_info
...

And finally create the in memory inventory with the necessary group from the instances metadata to run others play

...
- name: create in memory inventory
  add_host:
    hostname: "{{ item.name }}"
    ansible_ssh_host: "{{ item.private_v4 }}"
    ansible_user: "{{ ansible_user }}"
    ansible_ssh_common_args: '-o ProxyCommand="ssh -i {{ ssh_priv_ key }} -W %h:%p -q ansible@{{ gw_ip }}"'
    group:
      - "{{ item.metadata.tool }}"
      - "{{ item.metadata.environment }}"
  loop: "{{ servers_info.openstack_servers }}"
...

It's working play but are there a way to do this in a better way, maybe more "elegant"?

I have also a doubt on ansible module openstack.cloud.server_info, in the documentation have the parameter filter, I try to filter on metadata of the instance but it does not work.

I would prefer to use metadata instead server name for filter my gateway because like this if another instance get a name with the "gw" letter will be selected and my playbook may fails because the gw_ip facts may contain the wrong information.

I encountered an issue on the way the sshd daemon is configured, here we have a couple of path exposed in RO by a server, the end user have to use the service in RO on their machine use sshfs to mount it.

The configuration are:

Match Group ADGroup1
  # Force the connection to use SFTP and chroot to the required directory.
  ForceCommand internal-sftp
  ChrootDirectory /ADGroup1Dir
  # Disable tunneling, authentication agent, TCP and X11 forwarding.
  PermitTunnel no
  AllowAgentForwarding no
  AllowTcpForwarding no
  X11Forwarding no

Match Group ADGroup2
  # Force the connection to use SFTP and chroot to the required directory.
  ForceCommand internal-sftp
  ChrootDirectory /ADGroup2Dir
  # Disable tunneling, authentication agent, TCP and X11 forwarding.
  PermitTunnel no
  AllowAgentForwarding no
  AllowTcpForwarding no
  X11Forwarding no

Usually every think works, except when some user are present in both group. Ssh chrootdirectory the user on the first match and the mount works only with the following command:

sshfs aduser@server:/ /localpath

whit the following command we receive a no such file or directory error:

sshfs aduser@server:/ADGroup2Dir

but by watching the debug log of ssh server, the only No such file or directory error are saying that the /usr/libexec/openssh/sftp-server are not found.

Some body can help to figured out this issue?