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

log additional host info at warning level

XMLWordPrintable

    • No
    • Sprint 235, Sprint 236, Sprint 238
    • 3
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required

      Description of problem:

      For https://issues.redhat.com//browse/OCPBUGS-4998, additional logging was added to the wait-for command when the state is in pending-user-action in order to show the particular host errors preventing installation. This additional host info should be added at the WARNING level.

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

       

      How reproducible:

       

      Steps to Reproduce:

      1. Test this in the same as bug https://issues.redhat.com//browse/OCPBUGS-4998, i.e. by swapping the boot order of the disks
      2. When the log message with additional info is logged it is logged at DEBUG level, for example
      DEBUG Host master-2 Expected the host to boot from disk, but it booted the installation image - please reboot and fix boot order to boot from disk Virtual_disk 6000c295b246decdbb4f4e691c185fcf (sda, /dev/disk/by-id/wwn-0x6000c295b246decdbb4f4e691c185fcf)INFO cluster has stopped installing... working to recover installation
      3. This has now been changed to log at WARNING level
      4. In addition multiple messages are logged:
      "level=info msg=cluster has stopped installing... working to recover installation". This will change to only log it one time.

      Actual results:

       

      Expected results:

      1. The message is now logged at WARNING level
      2. Only one message for "cluster has stopped installing... working to recover installation" will appear

      Additional info:

       

            bfournie@redhat.com Robert Fournier
            bfournie@redhat.com Robert Fournier
            Biagio Manzari Biagio Manzari
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: