Network verification has failed after successful HA deployment. Second controller has changed network configuration after deploy (not idempotent)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Ihor Kalnytskyi | ||
7.0.x |
Invalid
|
High
|
Sergii Rizvan | ||
8.0.x |
Invalid
|
High
|
Ihor Kalnytskyi | ||
Mitaka |
Fix Released
|
High
|
Ihor Kalnytskyi |
Bug Description
1. Download and install detach plugins
https:/
https:/
https:/
2. Create new environment by default
3. Add 3 controllers, 3 database+
4. Start network verification. It was successful
5. Start deployment. It was successful
6. Start Network verification. It has failed with error:
Some untagged networks are assigned to the same physical interface. You should assign them to different physical interfaces. Affected: "admin (PXE)", "public" networks at node "Untitled (2d:35)"
I didn't change anything in network configuration before deployment.
But after deployment the second controller (node-7) has changed network configuration (see attached screen)
Logs are here: https:/
Controllers: node-6,7,10
Compute: node-8
Cinder: node-9
Database+
VERSION:
feature_groups:
- mirantis
production: "docker"
release: "8.0"
api: "1.0"
build_number: "417"
build_id: "417"
fuel-nailgun_sha: "9ebbaa0473effa
python-
fuel-agent_sha: "df16d41cd7a944
fuel-
astute_sha: "c7ca63a4921674
fuel-library_sha: "7ef751bdc0e460
fuel-ostf_sha: "214e794835acc7
fuel-mirror_sha: "b62f3cce5321fd
fuelmenu_sha: "2a0def56276f0f
shotgun_sha: "63645dea384a37
network-
fuel-upgrade_sha: "616a7490ec7199
fuelmain_sha: "cfeadd34d8d048
Changed in fuel: | |
assignee: | nobody → Fuel Library Team (fuel-library) |
status: | New → Confirmed |
tags: | added: area-library |
tags: | added: life-cycle-management |
summary: |
Network verification has failed after successful HA deployment. Second - controller has changed network configuration after deploy + controller has changed network configuration after deploy (not + idempotent) |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Dmitry Bilunov (dbilunov) |
tags: | added: team-bugfix |
Changed in fuel: | |
status: | Confirmed → In Progress |
Changed in fuel: | |
assignee: | Dmitry Bilunov (dbilunov) → nobody |
tags: |
added: team-network removed: team-bugfix |
tags: |
added: area-mos removed: area-library |
Changed in fuel: | |
status: | In Progress → Confirmed |
Changed in fuel: | |
assignee: | nobody → Fuel Python Team (fuel-python) |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
tags: |
added: area-python removed: area-mos |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Aleksey Kasatkin (alekseyk-ru) |
Changed in fuel: | |
status: | Confirmed → Triaged |
tags: | added: release-notes |
no longer affects: | fuel/mitaka |
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Fuel Python Team (fuel-python) |
tags: |
added: 8.0 release-notes-done removed: release-notes |
tags: | added: on-verification |
tags: | removed: on-verification |
tags: | added: on-verification |
Bogdan, network verification was successful before deployment.
I added this information to description of the bug.