Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-24351

Fix call trace when running sos collect in an ocp cluster

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • sos
    • None
    • Major
    • sst_cee_supportability
    • False
    • Hide

      None

      Show
      None

      When running sos collect in an ocp cluster, we got the following call trace:

      [root@304807065a37 ~]# sos collect --cluster-type=ocp -c ocp.kubeconfig=/root/kubeconfig --alloptions --all-logs --verify --no-local --batch --plugin-option=crio.all=on --plugin-option=crio.logs=on --plugin-option=podman.all=on --plugin-option=podman.logs=on --timeout=1800 -vvvv --debug [sos_collector:__init__] Executing /usr/sbin/sos collect --cluster-type=ocp -c ocp.kubeconfig=/root/kubeconfig --alloptions --all-logs --verify --no-local --batch --plugin-option=crio.all=on --plugin-option=^Cio.logs=on --plugin-option=podman.all=on --plugin-option=podman.logs=on --timeout=1800 -vvvv --debug [sos_collector:__init__] Found cluster profiles: dict_keys(['ceph', 'jbon', 'juju', 'kubernetes', 'ocp', 'rhosp', 'ovirt', 'rhhi_virt', 'rhv', 'pacemaker', 'satellite']) sos-collector (version 4.6.0) This utility is used to collect sos reports from multiple nodes simultaneously. Remote connections are made and/or maintained to those nodes via well-known transport protocols such as SSH. An archive of sos report tarballs collected from the nodes will be generated in /var/tmp/sos.yi_fa49i and may be provided to an appropriate support representative. The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No configuration changes will be made to the system running this utility or remote systems that it connects to. [sos_collector:configure_sos_cmd] Initial sos cmd set to sosreport --batch --alloptions --all-logs --verify --chroot auto [sos_collector:prep] password not specified, assuming SSH keys sos-collector ASSUMES that SSH keys are installed on all nodes unless the --password option is provided. [localhost:run_command] Running command hostname [localhost:_run_command_with_pexpect] The command was not found or was not executable: hostname. [localhost:_get_hostname] Hostname set to localhost [localhost:determine_host_policy] using local policy Red Hat Enterprise Linux Traceback (most recent call last): File "/usr/sbin/sos", line 22, in <module> sos.execute() File "/usr/lib/python3.6/site-packages/sos/__init__.py", line 193, in execute self._component.execute() File "/usr/lib/python3.6/site-packages/sos/collector/__init__.py", line 1175, in execute self.prep() File "/usr/lib/python3.6/site-packages/sos/collector/__init__.py", line 896, in prep self.cluster.setup() File "/usr/lib/python3.6/site-packages/sos/collector/clusters/ocp.py", line 132, in setup out = self.exec_primary_cmd(self.fmt_oc_cmd("auth can-i '*' '*'")) File "/usr/lib/python3.6/site-packages/sos/collector/clusters/ocp.py", line 104, in fmt_oc_cmd return "%s %s" % (self.oc_cmd, cmd) File "/usr/lib/python3.6/site-packages/sos/collector/clusters/ocp.py", line 81, in oc_cmd 'which oc', chroot=self.primary.host.sysroot TypeError: run_command() got an unexpected keyword argument 'chroot'

            rhn-support-jcastillo Jose Castillo
            rhn-support-jcastillo Jose Castillo
            Jose Castillo Jose Castillo
            no-user-match-found no-user-match-found
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: