Skip to content
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

ERROR: Unable to find interface object for configured trunk member 3.0 #361

Open
MicSkr opened this issue Aug 2, 2023 · 1 comment
Open
Labels
bug Something isn't working untriaged Issue needs to be reviewed for validity

Comments

@MicSkr
Copy link

MicSkr commented Aug 2, 2023

Environment

  • Declarative Onboarding Version: 1.39
  • BIG-IP Version: BIG-IP 15.1.8.1 as rSeries Tenant

Summary

Submitting Trunk Class fails
Existing Trunk is configured on the rSeries Tenant and references interfaces 3.0 and 7.0.

When submitting DO Declaration with Trunk and without Trunk, the Error occurs.
Unable to submit a DO Declaration successfully.

Steps To Reproduce

Steps to reproduce the behavior:

Create and Assign a Trunk on rSeries platform for Classic F5 Tenant using interfaces 3.0 and 7.0
Validate Exists on Classis Tenant: Network >> Trunks >> Bonded.Pair

  1. Submit the following declaration:
{
  "$schema": "https://raw.githubusercontent.com/F5Networks/f5-declarative-onboarding/main/src/schema/latest/do.schema.json",
  "schemaVersion": "1.0.0",
  "class": "Device",
  "async": true,
  "Common": {
   ...
   "Bonded.Pair": {
      "class": "Trunk",
      "distributionHash": "src-dst-mac",
      "interfaces": [
        "3.0",
        "7.0"
      ],
      "lacpEnabled": false,
      "spanningTreeEnabled": false,
      "lacpMode": "active",
      "lacpTimeout": "long",
      "linkSelectPolicy": "auto",
      "qinqEthertype": "0x8100"
    }
   ...
   "VLAN614": {
      "class": "VLAN",
      "tag": 614,
      "interfaces": [
        {
          "name": "Bonded.Pair",
          "tagged": true
        }
      ]
    },
    }
}

Submitting the declaration without the Trunk Class produces the same error message.

  1. Observe the following error response:
{
    "result": {
        "class": "Result",
        "code": 202,
        "status": "ROLLING_BACK",
        "message": "invalid config - rolling back",
        "errors": [
            "01070538:7: ERROR: Unable to find interface object for configured trunk member 3.0"
        ]
    }
    ...
}

Expected Behavior

Trunk is built or confirmed with DO

Actual Behavior

DO Task Indicates it is rolling back.

@MicSkr MicSkr added bug Something isn't working untriaged Issue needs to be reviewed for validity labels Aug 2, 2023
@MicSkr
Copy link
Author

MicSkr commented Aug 3, 2023

Additional Write Up:

  • Deleted the rSeries Tenant
  • Created New rSeries Tenant - Classic BIG-IP 15.1.8.1
  • On Tenant Config Applied MGMT IP Address, Prefix, Gateway, attached VLANS from Host, Deployed
  • After Bootup: Change root and admin password, accessed UI, Next >> Network: Finish
  • Trunk and Vlans already exist, passed from HOST
  • Installled DO 1.39
  • Submit DO that does not include the Trunk; Does include VLANS, Self IPs, and more.
  • Error: Unable to find interface obect for configured trunk member 3.0
  • Request to /config shows Trunk with interface 3.0, Vlans, but none of our new config

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working untriaged Issue needs to be reviewed for validity
Projects
None yet
Development

No branches or pull requests

1 participant