XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • DO316 - OCP4.14-en-4-20240806
    • DO316
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • 9
    • ROLE
    • en-US (English)

      Please fill in the following information:


      URL: https://rol.redhat.com/rol/app/courses/cl210-16.1/pages/ch04s09
      Reporter RHNID: jonathan.fulde.svi
      Section Title:              Lab: Configuring Kubernetes High Availability for Virtual Machines                                                          

      Issue description

      Task 7.3 to 7.5
      Task 8 ( 8.3) would also work without the change of the eviction strategy. (After it is stopped, you can still start it without the change of the eviction strategy, there is no learning here.)

      In my oppinion there should either be a Task 9 that repeats Task 7.5 (cordon again - but watch out, there is only one worker left - or 2 masters) so you can see the node is getting migrated automatically, or just switch task 8 with 7, so first 8 then 7

      Problem: If the vmi is running on the master, the end of lab grade script does give an error, because it only checks if worker01 or worker02 is cordoned off, not a master node (with the worker role).
      In my lab the www2 vmi was running on a master node.

      Steps to reproduce:

       

      Workaround:

       

      Expected result:

              lauber Susan Lauber
              wraja@redhat.com Wasim Raja
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: