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

SSHkeys fails to write on upgrade to 4.13.rc3


    • Moderate
    • No
    • 2
    • MCO Sprint 238, MCO Sprint 239, MCO Sprint 240, MCO Sprint 241
    • 4
    • Rejected
    • False
    • Hide



      Description of problem:

      While trying to update build01 from 4.13.rc2->4.13.rc3, the MCO degraded upon trying to upgrade the first master node. The error being:
      E0414 15:42:29.597388 2323546 writer.go:200] Marking Degraded due to: exit status 1
      Which I mapped to this line:
      I think this error can be improved since it is a bit confusing, but that's not the main problem.
      We noticed that the actual issue was that there is an existing "/home/core/.ssh" directory, that seemed to have been created by 4.13.rc2 (but could have been earlier), that belonged to the root user, as such when we attempted to create the folder via runuser core by hand, it failed with permission denied (and since we return the exec status, I think it just returned status 1 and not this error message).
      I am currently not sure if we introduced something that caused this issue. There was an ssh (only on master pool) in that build01 cluster for 600 days already, so it must have worked in the past?
      Workaround is to delete the .ssh folder and let the MCD recreate it

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


      How reproducible:

      uncertain, but shouldn't be very high otherwise we would have ran into this in CI much more I think?

      Steps to Reproduce:

      1. create some 4.12 cluster with sshkey
      2. upgrade to 4.13.rc2
      3. upgrade to 4.13.rc3

      Actual results:


      Expected results:


      Additional info:


            rh-ee-iqian Ines Qian
            jerzhang@redhat.com Yu Qi Zhang
            Sergio Regidor de la Rosa Sergio Regidor de la Rosa
            0 Vote for this issue
            6 Start watching this issue