Bug 2089563

Summary: Update Power VS MAPI to use api's from openshift/api repo
Product: OpenShift Container Platform Reporter: Karthik K N <kabhat>
Component: InstallerAssignee: Nobody <nobody>
Installer sub component: openshift-installer QA Contact: Julie <mjulie>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: dmistry, mjulie, mkumatag
Version: 4.11Flags: dmistry: needinfo-
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-10 11:13:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Karthik K N 2022-05-24 03:27:50 UTC
Thanks for opening a bug report!
Before hitting the button, please fill in as much of the template below as you can.
If you leave out information, it's harder to help you.
Be ready for follow-up questions, and please respond in a timely manner.
If we can't reproduce a bug we might close your issue.
If we're wrong, PLEASE feel free to reopen it and explain why.

Version: 4.11

$ openshift-install version
<your output here>

Platform: IPI Power VS

#Please specify the platform type: aws, libvirt, openstack or baremetal etc.

Please specify:
* IPI (automated install with `openshift-install`. If you don't know, then it's IPI)
* UPI (semi-manual installation on customized infrastructure)

What happened?

Update Power VS MAPI to use api's from openshift/api repository.

#Enter text here.

#See the troubleshooting documentation (https://github.com/openshift/installer/blob/master/docs/user/troubleshooting.md) for ideas about what information to collect.

#For example, 

# If the installer fails to create resources (https://github.com/openshift/installer/blob/master/docs/user/troubleshooting.md#installer-fails-to-create-resources), attach the relevant portions of your `.openshift_install.log.`
# If the installer fails to bootstrap the cluster (https://github.com/openshift/installer/blob/master/docs/user/troubleshootingbootstrap.md), attach the bootstrap log bundle.
# If the installer fails to complete installation after bootstrapping completes (https://github.com/openshift/installer/blob/master/docs/user/troubleshooting.md#installer-fails-to-initialize-the-cluster), attach the must-gather log bundle using `oc adm must-gather`

# Always at least include the `.openshift_install.log`

What did you expect to happen?

#Enter text here.

How to reproduce it (as minimally and precisely as possible)?

$ your-commands-here

Anything else we need to know?

#Enter text here.

Comment 3 Gaoyun Pei 2022-06-14 12:28:04 UTC
Hi Deep, I noticed you once verified one Power VS related bug before in https://bugzilla.redhat.com/show_bug.cgi?id=2086718, could you also please help to check if this one is working for you? Thanks.

Comment 4 mkumatag 2022-06-14 13:25:08 UTC
@mjulie.com adding test contact for the power platform

Comment 6 Julie 2022-06-20 14:03:46 UTC
Deployed a cluster and checked the specifications set in the machine object.
Compared and verified that it matches with the apis in the openshift/api repo.

Build used: https://mirror.openshift.com/pub/openshift-v4/ppc64le/clients/ocp-dev-preview/4.11.0-0.nightly-ppc64le-2022-06-16-003709/

# oc get clusterversion
NAME      VERSION                                      AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.11.0-0.nightly-ppc64le-2022-06-16-003709   True        False         2d22h   Cluster version is 4.11.0-0.nightly-ppc64le-2022-06-16-003709

# oc get machine -A
NAMESPACE               NAME                                     PHASE     TYPE   REGION   ZONE    AGE
openshift-machine-api   rdr-mju-jun17-fvjbg-master-0             Running   s922   lon      lon06   2d23h
openshift-machine-api   rdr-mju-jun17-fvjbg-master-1             Running   s922   lon      lon06   2d23h
openshift-machine-api   rdr-mju-jun17-fvjbg-master-2             Running   s922   lon      lon06   2d23h
openshift-machine-api   rdr-mju-jun17-fvjbg-worker-6l9vm         Running   s922   lon      lon06   2d23h
openshift-machine-api   rdr-mju-jun17-fvjbg-worker-c564x         Running   s922   lon      lon06   2d23h
openshift-machine-api   rdr-mju-jun17-fvjbg-worker-zq9nn         Running   s922   lon      lon06   2d23h

# oc describe machine rdr-mju-jun17-fvjbg-worker-6l9vm -n openshift-machine-api

  Lifecycle Hooks:
  Provider ID:  ibmpowervs://lon/lon06/dbc67d5e-9579-49da-b1d9-fc2ec7ddc680/9e18963a-2b9e-42e2-b09e-1bc7d9c8575d
  Provider Spec:
      API Version:  machine.openshift.io/v1
      Credentials Secret:
        Name:  powervs-credentials
        Name:         rhcos-rdr-mju-jun17-fvjbg
        Type:         Name
      Key Pair Name:  rdr-mju-jun17-fvjbg-key
      Kind:           PowerVSMachineProviderConfig
      Memory Gi B:    32
        Creation Timestamp:  <nil>
        Regex:         ^DHCPSERVER[0-9a-z]{32}_Private$
        Type:          RegEx
      Processor Type:  Shared
      Processors:      0.5
      Service Instance:
        Id:         dbc67d5e-9579-49da-b1d9-fc2ec7ddc680
        Type:       ID
      System Type:  s922
      User Data Secret:
        Name:  worker-user-data
    Address:  rdr-mju-jun17-fvjbg-worker-6l9vm
    Type:     InternalDNS
    Last Transition Time:  2022-06-17T14:37:38Z
    Status:                True
    Type:                  Drainable
    Last Transition Time:  2022-06-17T14:44:03Z
    Status:                True
    Type:                  InstanceExists
    Last Transition Time:  2022-06-17T14:37:38Z
    Status:                True
    Type:                  Terminable
  Last Updated:            2022-06-17T14:56:33Z
  Node Ref:
    Kind:  Node
    Name:  rdr-mju-jun17-fvjbg-worker-6l9vm
    UID:   ac7ed316-5e69-49b1-8443-d8cebbaf20ba
  Phase:   Running
  Provider Status:
      Last Transition Time:  2022-06-17T14:43:13Z
      Message:               Machine successfully created
      Reason:                MachineCreationSucceeded
      Status:                True
      Type:                  MachineCreation
    Instance Id:             9e18963a-2b9e-42e2-b09e-1bc7d9c8575d
    Instance State:          ACTIVE
    Service Instance ID:     dbc67d5e-9579-49da-b1d9-fc2ec7ddc680
Events:                      <none>

Comment 8 errata-xmlrpc 2022-08-10 11:13:36 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.