openstack port状态down,binding_vif_type显示binding_failed

问题现象:

openstack port状态down,binding_vif_type显示binding_failed

[root@controller ~]# openstack port list --router router
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------+--------+
| ID                                   | Name | MAC Address       | Fixed IP Addresses                                                           | Status |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------+--------+
| 3a144298-c39f-4722-8c95-e66ddac308a6 |      | fa:16:3e:9d:29:b7 | ip_address='172.16.1.1', subnet_id='e98365bf-b2bb-496d-a7dc-52124fe7f9a6'    | DOWN   |
| 6021e634-c8f7-4e65-8016-5d72ae66cb85 |      | fa:16:3e:6e:6e:fa | ip_address='203.0.113.207', subnet_id='416aa83f-c155-4467-b489-21e6cd9741e2' | DOWN   |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------+--------+



[root@controller ~]# openstack port show 3a144298-c39f-4722-8c95-e66ddac308a6
+-------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+
| Field                   | Value                                                                                                                                                   |
+-------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+
| admin_state_up          | UP                                                                                                                                                      |
| allowed_address_pairs   |                                                                                                                                                         |
| binding_host_id         | controller                                                                                                                                              |
| binding_profile         |                                                                                                                                                         |
| binding_vif_details     |                                                                                                                                                         |
| binding_vif_type        | binding_failed                                                                                                                                          |
| binding_vnic_type       | normal      

原因:

配置linuxbridge agent的时候没有替换网卡信息

分析过程

打开DEBUG级别日志发现缺少linux bridge agent

打开 openstackDEBUG级别日志_yue_luu的博客-优快云博客

2022-08-14 10:50:39.975 50636 DEBUG neutron.plugins.ml2.drivers.mech_agent [req-9c3ec1e1-53a5-495f-8b79-448d50c3275e - - - - -] Port 3a144298-c39f-4722-8c95-e66ddac308a6 on network 45c89664-9173-4117-b095-e9e8468c36b8 not bound, no agent of type Linux bridge agent registered on host controller bind_port /usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/mech_agent.py:104

openstack network agent list查不到linux bridge agent

[root@controller ~]# openstack network  agent list
+--------------------------------------+----------------+------------+-------------------+-------+-------+------------------------+
| ID                                   | Agent Type     | Host       | Availability Zone | Alive | State | Binary                 |
+--------------------------------------+----------------+------------+-------------------+-------+-------+------------------------+
| b307c36c-5a7e-4701-ba9b-0e0c3a4f299a | Metadata agent | controller | None              | :-)   | UP    | neutron-metadata-agent |
| b83e6cc6-07c3-40a1-bb24-9713288a62b3 | L3 agent       | controller | nova              | :-)   | UP    | neutron-l3-agent       |
| d86d84e6-eb03-4fe1-b29e-68ca61070515 | DHCP agent     | controller | nova              | :-)   | UP    | neutron-dhcp-agent     |
+--------------------------------------+----------------+------------+-------------------+-------+-------+------------------------+

systemctl status却显示正常

[root@controller ~]# systemctl status neutron-linuxbridge-agent.service
● neutron-linuxbridge-agent.service - OpenStack Neutron Linux Bridge Agent
   Loaded: loaded (/usr/lib/systemd/system/neutron-linuxbridge-agent.service; enabled; vendor preset: disabled)
   Active: active (running) since Sun 2022-08-14 11:18:11 EDT; 2s ago
  Process: 77266 ExecStartPre=/usr/bin/neutron-enable-bridge-firewall.sh (code=exited, status=0/SUCCESS)
 Main PID: 77271 (neutron-linuxbr)
    Tasks: 1
   Memory: 61.9M
   CGroup: /system.slice/neutron-linuxbridge-agent.service
           └─77271 /usr/bin/python2 /usr/bin/neutron-linuxbridge-agent --config-file /usr/share/neutron/neutron-dist.conf --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/linuxbridge_agent.ini --config-dir /e...

linuxbridge agent日志显示启动失败

2022-08-14 11:19:02.361 77840 ERROR neutron.plugins.ml2.drivers.linuxbridge.agent.linuxbridge_neutron_agent [-] Interface PROVIDER_INTERFACE_NAME for physical network provider does not exist. Agent terminated!

原来是/etc/neutron/plugins/ml2/linuxbridge_agent.ini 配置的时候没有替换物理网卡信息

还有其他配置文件没有修改的也一起改一下

修改完就正常啦

[root@controller ~]# openstack network  agent list
+--------------------------------------+--------------------+------------+-------------------+-------+-------+---------------------------+
| ID                                   | Agent Type         | Host       | Availability Zone | Alive | State | Binary                    |
+--------------------------------------+--------------------+------------+-------------------+-------+-------+---------------------------+
| 206b0223-b2d4-4ae6-82d6-a87c32b589f1 | Linux bridge agent | controller | None              | :-)   | UP    | neutron-linuxbridge-agent |
| b307c36c-5a7e-4701-ba9b-0e0c3a4f299a | Metadata agent     | controller | None              | :-)   | UP    | neutron-metadata-agent    |
| b83e6cc6-07c3-40a1-bb24-9713288a62b3 | L3 agent           | controller | nova              | :-)   | UP    | neutron-l3-agent          |
| d86d84e6-eb03-4fe1-b29e-68ca61070515 | DHCP agent         | controller | nova              | :-)   | UP    | neutron-dhcp-agent        |
+--------------------------------------+--------------------+------------+-------------------+-------+-------+---------------------------+
[root@controller ~]# openstack port list --router router
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------+--------+
| ID                                   | Name | MAC Address       | Fixed IP Addresses                                                           | Status |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------+--------+
| 3a144298-c39f-4722-8c95-e66ddac308a6 |      | fa:16:3e:9d:29:b7 | ip_address='172.16.1.1', subnet_id='e98365bf-b2bb-496d-a7dc-52124fe7f9a6'    | ACTIVE |
| 6021e634-c8f7-4e65-8016-5d72ae66cb85 |      | fa:16:3e:6e:6e:fa | ip_address='203.0.113.207', subnet_id='416aa83f-c155-4467-b489-21e6cd9741e2' | ACTIVE |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------+--------+

<think>好的,用户遇到了Git合并时本地更改会被覆盖的问题,需要解决方案。根据之前的引用资料,解决方法主要有commit、stash和revert三种。首先,我得确认用户的具体情况,比如他们的本地更改是否已经完成,是否需要保留,或者是否可以丢弃。用户可能不太清楚这三种方法的适用场景,需要详细解释每个选项的步骤和优缺点。比如,commit适用于需要保留更改的情况,stash适合临时保存以便后续恢复,而revert则是直接撤销更改,适用于不需要保留的情况。需要结构清晰,分点说明,每个方法都给出操作步骤和适用场景,帮助用户理解哪种情况最适合他们。还要注意使用中文,避免技术术语过于复杂,让用户容易理解。同时,生成相关问题,可能涉及如何恢复stash的内容,或者如何避免频繁冲突等,扩展用户的知识点。另外,要确保LaTeX格式正确,但在这个问题中可能用不上数学公式,所以主要关注代码块和引用标识。检查引用是否正确,比如引用[^1]和[^2]的来源是否相关,用户提供的引用内容是否准确对应解决方案。 最后,确保回答真实可靠,操作步骤准确无误,避免误导用户。可能还需要提醒用户根据具体情况选择方法,比如如果有未完成的实验性代码,stash可能是更好的选择,而如果是确定要保留的修改,则应该commit。</think>要解决Git合并时本地更改被覆盖的问题,可根据不同场景选择以下三种方法: ### 一、提交本地更改(commit) **适用场景**:当本地更改已测试通过且需要保留到版本历史中。 **操作步骤**: 1. 将改动添加到暂存区: ```bash git add . # 添加所有文件 # 或指定文件 git add file1.txt file2.py ``` 2. 提交更改并添加描述: ```bash git commit -m "完成用户登录模块优化" ``` 3. 执行合并操作: ```bash git merge origin/main ``` **优点**:保留完整的开发记录,便于后续追溯[^1]。 ### 二、暂存更改(stash) **适用场景**:需要临时保存未完成的修改(如调试代码),优先处理合并操作。 **操作步骤**: 1. 保存当前工作状态: ```bash git stash # 可选添加备注 git stash save "用户登录模块调试代码" ``` 2. 查看暂存记录列表: ```bash git stash list ``` 3. 合并远程分支: ```bash git merge origin/main ``` 4. 恢复暂存内容: ```bash git stash pop # 恢复并删除最近一次暂存 # 或指定特定暂存 git stash apply stash@{1} ``` **优点**:保持工作目录整洁,特别适合处理紧急合并任务[^2]。 ### 三、撤销本地更改(revert) **适用场景**:本地修改可丢弃(如实验性代码或错误修改)。 **操作步骤**: 1. 撤销所有未提交的修改: ```bash git checkout -- . # 全部文件 # 或指定文件 git checkout -- file1.txt ``` 2. 执行合并操作: ```bash git merge origin/main ``` **风险提示**:此操作不可逆,需确认文件无需保留。 --- ### 对比决策表 | 方法 | 保留记录 | 可恢复性 | 适用阶段 | |---------|----------|----------|------------------| | commit | ✅ | ✅ | 功能开发完成时 | | stash | ❌ | ✅ | 开发中途临时切换 | | revert | ❌ | ❌ | 放弃无效修改 | ### 扩展应用场景 - 当存在多个暂存时,可用`git stash list`查看记录,通过`git stash apply stash@{n}`精准恢复 - 合并后出现冲突时,可使用`git mergetool`可视化工具解决冲突 - 长期分支开发推荐使用`git rebase`保持提交历史线性
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值