Uploaded image for project: 'Machine Config Operator'
  1. Machine Config Operator
  2. MCO-474

Investigate MCO reboot behavior when machine-os content hasn't changed during upgrade

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • False
    • None
    • False
    • MCO Sprint 231, MCO Sprint 232
    • 0
    • 0

      It was brought up on slack that MCO reboots node even when OSImage remains same between two OCP releases.  Our OCP customer would be benefited if we know the cause and if there is possibility to avoid such reboots.

      For this spike, we can look into update from 4.11.11 -> 4.11.12 as both release have machine-os=411.86.202210201510-0

      Acceptance Criteria:

      • We know whether node reboots occurs or not. If it happens, what is the reason
      • Based on the finding and possibilities, create follow-up story card if necessary

       
       

            jkyros@redhat.com John Kyros
            rhn-engineering-skumari Sinny Kumari
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: