Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-16392

Sos reports contains greenboot logs only in bulk journal file

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Normal Normal
    • 4.14.z
    • 4.14
    • MicroShift
    • None
    • No
    • uShift Sprint 242, uShift Sprint 243
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required

      Description of problem:

      sos report contains logs of microshift in separate location: sos_commands/microshift/journalctl_--no-pager_–unit_microshift
      But to get greenboot logs a sos_commands/logs/journalctl* file need to be filtered which impacts supportability.
      

      Version-Release number of selected component (if applicable):

       

      How reproducible:

       

      Steps to Reproduce:

      1. generate sos report using the command `sos report`
      2. extract the generated report: `tar xvf sosreport-*.tar.xz`
      3. there is no dedicated greenboot logs under `sosreport-*/sos_commands/greenboot` 
      
      greenboot logs need to be filtered from sos_commands/logs/journalctl*
      

      Expected results:

      greenboot logs reside in separate dir and they are easy to access: sos_commands/greenboot/
      
      # ls sos_commands/greenboot/journalctl*
      
      sos_commands/greenboot/journalctl_--no-pager_--unit_greenboot-healthcheck  
      sos_commands/greenboot/journalctl_--no-pager_--unit_redboot-task-runner
      sos_commands/greenboot/journalctl_--no-pager_--unit_greenboot-task-runner 

       

      Additional info:

       

            eslutsky Evgeny Slutsky
            pmatusza@redhat.com Patryk Matuszak
            Rama Kasturi Narra Rama Kasturi Narra
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: