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

RHOCP 4 .13 reboot time has increased

XMLWordPrintable

    • Important
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      In BMC infra, reboot of node is taking longer time since 4.12.

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

      OCP 4.12, 4.13

      How reproducible:

      Always

      Steps to Reproduce:

      1. Install cluster on bare metal servers.
2. Restart node
3.

      Actual results:

      Restart of node is takin around 15 mins.

      Expected results:

      Restart of node should not take longer time.

      Additional info:

      What are you experiencing? What are you expecting to happen?
Our test automation we  executing the Master node restart via BMC for all releases. Now we have observe that Master node Restart recovery time has increased from earlier 4.12 releases i.e. 4.12.5 average restart time was 12minute 32 second. Now in 4.12.19  restart recovery time is more than 15min and out test automation hitting to the time out. 
The Master node restart recovery time should not be increased.   

Define the value or impact to you or the business
Master node restart recovery time is not possible it increase since it's have direct impact for the application vCU&vDU recovery time. 
That can effect to the end user for longer downtime in case of restart 

Where are you experiencing this behavior? What environment?
Environment be used for testing is Airframe RM20 (3+5) MNO 
The Master node restart recovery time should be more or less similar from release to release. 

When does this behavior occur? Frequency? Repeatedly? At certain times?
For the later 4.12 releases master node restart recovery time looks to be extending. 
The recovery time behavior are same in every master node start exact time could be variate about 2 minutes but overall time has increased

            [OCPBUGS-18926] RHOCP 4 .13 reboot time has increased

            OpenShift Jira Bot added a comment -

            Thanks for reporting your issue!

            In order for the CoreOS team to be able to triage your issue, please copy the applicable parts of the following template into a comment and fill them out as completely as possible.

            • OCP Version at Install Time:
            • RHCOS Version at Install Time:
            • OCP Version after Upgrade (if applicable):
            • RHCOS Version after Upgrade (if applicable):
            • Platform (AWS, Azure, bare metal, GCP, vSphere, etc.):
            • Architecture (x86_64, ppc64le, s390x, etc.):

            If you're having problems booting/installing RHCOS, please provide:

            • The full contents of the serial console showing disk initialization, network configuration, and Ignition stages.
              • See this article for information about configuring your serial console.
              • Screenshots or a video recording of the console is usually not sufficient.
            • The full Ignition config (JSON format)

            If you're having problems post-installation or post-upgrade, please provide:

            • An sos report for affected nodes. See this documentation page for instructions on how to gather one.
            • A complete must-gather (oc adm must-gather)

            If you're having SELinux related issues, please provide:

            • The full /var/log/audit/audit.log file
            • Were any SELinux modules or booleans changed from the default configuration?
            • The output of ostree admin config-diff | grep selinux/targeted on impacted nodes

            OpenShift Jira Bot added a comment - Thanks for reporting your issue! In order for the CoreOS team to be able to triage your issue, please copy the applicable parts of the following template into a comment and fill them out as completely as possible. OCP Version at Install Time: RHCOS Version at Install Time: OCP Version after Upgrade (if applicable): RHCOS Version after Upgrade (if applicable): Platform (AWS, Azure, bare metal, GCP, vSphere, etc.): Architecture (x86_64, ppc64le, s390x, etc.): If you're having problems booting/installing RHCOS, please provide: The full contents of the serial console showing disk initialization, network configuration, and Ignition stages. See this article for information about configuring your serial console. Screenshots or a video recording of the console is usually not sufficient. The full Ignition config (JSON format) If you're having problems post-installation or post-upgrade, please provide: An sos report for affected nodes. See this documentation page for instructions on how to gather one. A complete must-gather ( oc adm must-gather ) If you're having SELinux related issues, please provide: The full /var/log/audit/audit.log file Were any SELinux modules or booleans changed from the default configuration? The output of ostree admin config-diff | grep selinux/targeted on impacted nodes

              rhn-engineering-jsafrane Jan Safranek
              rhn-support-akanekar Ankita Kanekar
              Michael Nguyen Michael Nguyen
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: