合并受阻
Hi openeuler-sync-bot, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: Networking, and any of the maintainers: @seuzw , @MrRlu , @kircher , @gebidelidaye , @zengwefeng , @sunsuwan , @robertxw
/check-cla
门禁正在运行， 您可以通过以下链接查看实时门禁检查结果.
门禁入口及编码规范检查: multiarch/src-openeuler/trigger/iproute, 当前构建号为 368
构建及构建后检查: multiarch/src-openeuler/x86-64/iproute, multiarch/src-openeuler/aarch64/iproute
门禁结果回显: multiarch/src-openeuler/comment/iproute
若您对门禁结果含义不清晰或者遇到问题不知如何解决，可参考门禁指导手册
| Check Name | Build Result | Build Details | |
|---|---|---|---|
| check_binary_file | :white_check_mark:SUCCESS | #368 | |
| check_package_license | :white_check_mark:SUCCESS | ||
| check_package_yaml_file | :white_check_mark:SUCCESS | ||
| check_consistency | :bug:WARNING | ||
| check_spec_file | :white_check_mark:SUCCESS | ||
| aarch64 | check_build | :x:FAILED | #367 |
| x86_64 | check_build | :x:FAILED | #370 |
@openeuler-sync-bot
门禁常见失败问题及解决方案, 可参考门禁问题排查手册
若门禁存在误报，您可以评论/ci_mistake 368进行误报标记，368表示本次构建号
也可带上误报的门禁检查项以及误报类型（ci、obs、infra），比如/ci_mistake 368 obs check_build check_install表示的是check_build和check_install存在误报，误报类型为obs
若想取消误报标记，可以评论/ci_unmistake 368取消
也可在评论后加上一段文字描述，但请另起一行
/retest
门禁正在运行， 您可以通过以下链接查看实时门禁检查结果.
若您对门禁结果含义不清晰或者遇到问题不知如何解决，可参考门禁指导手册
门禁入口及编码规范检查: multiarch/src-openeuler/trigger/iproute/7/console
aarch64架构构建及构建后检查：multiarch/src-openeuler/aarch64/iproute/7/console
x86_64架构构建及构建后检查：multiarch/src-openeuler/x86-64/iproute/7/console
/check-cla
1. Origin pull request:
https://gitee.com/src-openeuler/iproute/pulls/158
2. Original pull request related issue(s):
https://gitee.com/src-openeuler/iproute/issues/I8EZGI
3. Original pull request related commit(s):
tool inclusion
category: feature
bugzilla: https://gitee.com/src-openeuler/iproute/issues/I8EZGI
CVE: NA
-----------------------------------------------------
This patch adds ARPHRD_UB for iproute2 and support name parse for it.
The pf in the ub does not manage the addresses of VFs and the address
information of the VF cannot be obtained.
This patch deletes the display of vf address information in the pf.
Signed-off-by: Junxin Chen chenjunxin1@huawei.com
Signed-off-by: Fengyan Mu mufengyan@hisilicon.com