Skip to content

OCPBUGS-42220: Infoblox - use 2.12.2 WAPI version #229

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 20, 2025

Conversation

alebedev87
Copy link
Contributor

@alebedev87 alebedev87 commented Sep 3, 2024

This PR aims at updating the nominal version of Infoblox's WAPI we test our operator against. The test Infoblox instance we use is recommended to be used with 2.12.2 WAPI version (Infoblox ref).

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 3, 2024
@openshift-ci openshift-ci bot requested review from candita and gcs278 September 3, 2024 22:03
@alebedev87 alebedev87 changed the title [WIP] e2e: Infoblox - use 2.9.1 WAPI version e2e: Infoblox - use 2.9.1 WAPI version Sep 5, 2024
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Sep 5, 2024
@alebedev87 alebedev87 changed the title e2e: Infoblox - use 2.9.1 WAPI version e2e: Infoblox - use 2.12.2 WAPI version Sep 5, 2024
@alebedev87
Copy link
Contributor Author

/retest

Job execution failed: Pod scheduling timeout.

The test NIOS instance has been upgraded to 8.6.4
which recommends 2.12.2 as the WAPI version.
This commit updates the e2e test and docs with the
recommended WAPI version.

Ref:
https://community.infoblox.com/cixhp49439/attachments/cixhp49439/IPAM/6153/2/NIOS_8.6.2_ReleaseNotesREVC.pdf
@alebedev87 alebedev87 changed the title e2e: Infoblox - use 2.12.2 WAPI version OCPBUGS-42220: Infoblox - use 2.12.2 WAPI version Oct 7, 2024
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 7, 2024
@openshift-ci-robot
Copy link

@alebedev87: This pull request references Jira Issue OCPBUGS-42220, which is invalid:

  • expected the bug to target the "4.18.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@alebedev87
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 7, 2024
@openshift-ci-robot
Copy link

@alebedev87: This pull request references Jira Issue OCPBUGS-42220, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @melvinjoseph86

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from melvinjoseph86 October 7, 2024 11:20
// https://community.infoblox.com/cixhp49439/attachments/cixhp49439/IPAM/6153/2/NIOS_8.6.2_ReleaseNotesREVC.pdf
// Chapter: "Changes to Infoblox API and Restful API (WAPI)"
// "2.12.2" version is recommended for NIOS 8.6.2 (our Infoblox test instance is currently 8.6.4).
defaultWAPIVersion = "2.12.2"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this break compatibility with NIOS 7? We might need to add an API field to specify the WAPI version.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I see that it is configurable:

// WAPIVersion is the version of the Infoblox WAPI.
//
// +kubebuilder:validation:Required
// +required
WAPIVersion string `json:"wapiVersion"`

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could this break compatibility with NIOS 7?

Not really, this is just the nominal version of the API we test our operator against. As you mentioned the user has to provide its version as a dedicated API field.

@openshift-ci-robot
Copy link

@alebedev87: This pull request references Jira Issue OCPBUGS-42220, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @melvinjoseph86

In response to this:

This PR aims at updating the nominal version of Infoblox's WAPI we test our operator against. The test Infoblox instance we use is recommended to be used with 2.12.2 WAPI version (Infoblox ref).

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@alebedev87
Copy link
Contributor Author

After a bug scrub discussion:

  • We think that https://issues.redhat.com//browse/OCPBUGS-42220 can be fixed by a simple doc update. A placeholder can be used for the wapi version in the docs.
  • The API doc needs to be updated to specify valid versions. And may be a validation webhook needs to updated to make sure the provided version is valid.
  • This PR pursues yet an other goal - update the nominal wapi version we test against.

@melvinjoseph86
Copy link

this PR cannot be test using pre-merge verification method as external-dns-operator repo is still not supported in clusterbot

@melvinjoseph86
Copy link

/retest

@alebedev87
Copy link
Contributor Author

xref: openshift/openshift-docs#83270

@melvinjoseph86
Copy link

Pre merged verified using cluster bot

mjoseph@mjoseph-mac Downloads % oc get clusterversion                                                              
NAME      VERSION                                                   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.17.0-0.ci.test-2024-11-05-145258-ci-ln-nv2gvht-latest   True        False         69m     Cluster version is 4.17.0-0.ci.test-2024-11-05-145258-ci-ln-nv2gvht-latest

mjoseph@mjoseph-mac Downloads % oc get po -n external-dns-operator                                                 
NAME                                                              READY   STATUS      RESTARTS   AGE
external-dns-operator-76bfd77657-zvqdq                            2/2     Running     0          65m
external-dns-sample-aws-545c65987d-p62hp                          1/1     Running     0          32s
mjoseph@mjoseph-mac Downloads % oc get po -n  external-dns-operator external-dns-operator-76bfd77657-zvqdq   -oyaml
apiVersion: v1
kind: Pod
metadata:
  annotations:
    alm-examples: |-
<-----snip---->
        {
          "apiVersion": "externaldns.olm.openshift.io/v1alpha1",
          "kind": "ExternalDNS",
          "metadata": {
            "name": "sample-infoblox"
          },
          "spec": {
            "domains": [
              {
                "filterType": "Include",
                "matchType": "Exact",
                "name": "myzonedomain.com"
              }
            ],
            "provider": {
              "infoblox": {
                "credentials": {
                  "name": "infoblox-credentials"
                },
                "gridHost": "100.100.100.100",
                "wapiPort": 443,
                "wapiVersion": "2.12.2". <-----------
              },
              "type": "Infoblox"
            },
            "source": {
              "openshiftRouteOptions": {
                "routerName": "default"
              },
              "type": "OpenShiftRoute"
            }
          }
        },
<-----snip---->
          "apiVersion": "externaldns.olm.openshift.io/v1beta1",
          "kind": "ExternalDNS",
          "metadata": {
            "name": "sample-infoblox"
          },
          "spec": {
            "domains": [
              {
                "filterType": "Include",
                "matchType": "Exact",
                "name": "myzonedomain.com"
              }
            ],
            "provider": {
              "infoblox": {
                "credentials": {
                  "name": "infoblox-credentials"
                },
                "gridHost": "100.100.100.100",
                "wapiPort": 443,
                "wapiVersion": "2.12.2".    <----------------------
              },
              "type": "Infoblox"
            },
            "source": {
              "openshiftRouteOptions": {
                "routerName": "default"
              },
              "type": "OpenShiftRoute"
            }
          }
        }
      ]
<-----snip---->

@melvinjoseph86
Copy link

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Nov 6, 2024
@Miciah Miciah added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Nov 13, 2024
@Miciah
Copy link
Contributor

Miciah commented Nov 27, 2024

/assign

@candita
Copy link

candita commented Nov 27, 2024

/assign @Miciah
/assign

@candita
Copy link

candita commented Jan 13, 2025

@alebedev87 is this supposed to be on hold? I was going to LGTM, but once it comes off hold that will be removed.

@alebedev87
Copy link
Contributor Author

@candita : No. The only related thing is the doc PR but one does not block another.

@candita
Copy link

candita commented Jan 16, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 16, 2025
@alebedev87
Copy link
Contributor Author

/approve

Copy link
Contributor

openshift-ci bot commented Jan 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alebedev87

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 20, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 1f90625 and 2 for PR HEAD 57a58f8 in total

Copy link
Contributor

openshift-ci bot commented Jan 20, 2025

@alebedev87: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 39c5d56 into openshift:main Jan 20, 2025
10 checks passed
@openshift-ci-robot
Copy link

@alebedev87: Jira Issue OCPBUGS-42220: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-42220 has been moved to the MODIFIED state.

In response to this:

This PR aims at updating the nominal version of Infoblox's WAPI we test our operator against. The test Infoblox instance we use is recommended to be used with 2.12.2 WAPI version (Infoblox ref).

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. priority/backlog Higher priority than priority/awaiting-more-evidence. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants