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

OCPBUGS-19908: Downstream sync 2023-10-23 #842

Merged
merged 12 commits into from
Oct 23, 2023

Conversation

zeeke
Copy link
Contributor

@zeeke zeeke commented Oct 23, 2023

clean merge from upstream without conflicts

ran make -f Makefile.bundle generate bundle to align downstream manifests for

  • externallyManaged field in sriovnetworknodestate and sriovnetworknodepolicy (cc @SchSeba)
  • vlanProto field in sriovnetwork (cc @mlguerrero12)

cc @EmilienM

murali509 and others added 12 commits October 16, 2023 14:01
We use Kontron ME1310 Edge Servers which has built in E823C NICs. We create VFs using these NICs. We are able to create SriovNetworkNodePolicy and create the VFs after adding it under supported-nic-ids config map
Add support for Intel E823C NICs
We can't rely on the PCI address from the metadata so we will lookup the real PCI address
for the NIC that matches the MAC address.

Libvirt/QEMU cannot guarantee that the address specified in the XML will match the address seen by the guest.
This is a well known limitation: https://libvirt.org/pci-addresses.html
When using the q35 machine type, it highlights this issue due to the change from using PCI to PCI-E bus for virtual devices.

With that said, the PCI value in Nova Metadata is a best effort hint due to the limitations mentioned above. Therefore
we will lookup the real PCI address for the NIC that matches the MAC address.
Co-Authored-By: Andrea Panattoni <apanatto@redhat.com>
Co-Authored-By: Emilien Macchi <emilien@redhat.com>
virtual: get real PCI address for each device found
Updates to OCP:
* add a retry to the policy create to fix OCP CI flake
* add more ram to the OCP master single node
* add a wait for registry to be available
* update the ocp version to latest 4.14 rc release

Updates for K8s:
* switch to not use dockerhub for the registry image to overcome the pull limit
* add alias for golang to the dockerhub image

github actions:
* always remove the cluster

Signed-off-by: Sebastian Sch <sebassch@gmail.com>
via command:

```
make -f Makefile.bundle generate bundle
```

Signed-off-by: Andrea Panattoni <apanatto@redhat.com>
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Oct 23, 2023
@openshift-ci-robot
Copy link
Contributor

@zeeke: This pull request references Jira Issue OCPBUGS-19908, which is valid.

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

No GitHub users were found matching the public email listed for the QA contact in Jira (zgreenbe@redhat.com), skipping review request.

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

In response to this:

clean merge from upstream without conflicts

ran make -f Makefile.bundle generate bundle to align downstream manifests for

  • externallyManaged field in sriovnetworknodestate and sriovnetworknodepolicy (cc @SchSeba)
  • vlanProto field in sriovnetwork (cc @mlguerrero12)

cc @EmilienM

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/test-infra repository.

@mlguerrero12
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 23, 2023
@mlguerrero12
Copy link
Member

/retest-required

@bn222
Copy link
Contributor

bn222 commented Oct 23, 2023

/lgtm
/approve

@EmilienM
Copy link
Member

out of curiosity but not blocking it:
/test e2e-openstack-nfv

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 23, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bn222, mlguerrero12, zeeke

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 Oct 23, 2023
@openshift-ci openshift-ci bot merged commit 8b3e75a into openshift:master Oct 23, 2023
8 of 10 checks passed
@openshift-ci-robot
Copy link
Contributor

@zeeke: Jira Issue OCPBUGS-19908: All pull requests linked via external trackers have merged:

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

In response to this:

clean merge from upstream without conflicts

ran make -f Makefile.bundle generate bundle to align downstream manifests for

  • externallyManaged field in sriovnetworknodestate and sriovnetworknodepolicy (cc @SchSeba)
  • vlanProto field in sriovnetwork (cc @mlguerrero12)

cc @EmilienM

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/test-infra repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 23, 2023

@zeeke: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-openstack-nfv-hwoffload dfb84a1 link false /test e2e-openstack-nfv-hwoffload

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/test-infra repository. I understand the commands that are listed here.

@EmilienM
Copy link
Member

@zeeke could we have a sync on 4.14 also, thanks.

@zeeke
Copy link
Contributor Author

zeeke commented Oct 23, 2023

@zeeke could we have a sync on 4.14 also, thanks.

There is no sync for older branches. We can cherry-pick specific commits and create a pull request targeting release-4.14

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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants