Uploaded image for project: 'OpenShift Specialist Platform Team'
  1. OpenShift Specialist Platform Team
  2. SPLAT-482

Validate vSphere permissions for installation

Details

    • Validate vSphere permissions for installation
    • False
    • None
    • False
    • Green
    • In Progress
    • Impediment
    • 100
    • 100% 100%

    Description

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • As a Cluster Administrator, I want to ensure the permissions for my vSphere service account are configured correctly before installing OpenShift on vSphere. If the vSphere service account does not have the sufficient privileges, I want to be informed what the missing privilege(s) is and how to remediate the issue(s).

      Why is this important?

      • Currently, when an Administrator attempts to install OCP on vSphere without sufficient vSphere service account privileges, the installation fails but and the administrator has to guess what the error is and how to resolve this today because of missing permissions (in this case, storage permission), e.g.:
        "Error: failed to lease wait: Invalid configuration for device '0'.
      • See RFE-1965 for more information.

      Scenarios

      1. ...

      Acceptance Criteria

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. SPLAT-243 - [vsphere] Create a CLI tool that checks privileges of openshift user
      2. openshift/installer#5647: ipi/vsphere: improve permission error messages

      Open questions::

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

      Attachments

        Issue Links

          Activity

            People

              rhn-support-rvanderp Richard Vanderpool
              julim Ju Lim
              Jinyun Ma Jinyun Ma
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: