ExtraConfigPre and NodeExtraConfig are executed before network settings are applied
Bug #1907214 reported by
Takashi Kajinami
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Takashi Kajinami |
Bug Description
Currently ExtraConfigPre and NodeExtraConfig, are executed before network settigs are applied. This is different from old versions like Queens, in which these resources are executed after network configuration.
Some users currently use these resources to apply some configurations which depend on network connectivity on networks which are different from provisioning network in old releases like Queens, and this change in resource order causes failure with such implementations in current releases.
Changed in tripleo: | |
assignee: | nobody → Takashi Kajinami (kajinamit) |
description: | updated |
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → wallaby-2 |
tags: | added: queens-backport-potential |
tags: |
added: train-backport-potential removed: queens-backport-potential |
tags: | added: ux |
Changed in tripleo: | |
milestone: | wallaby-2 → wallaby-3 |
Changed in tripleo: | |
milestone: | wallaby-3 → wallaby-rc1 |
Changed in tripleo: | |
milestone: | wallaby-rc1 → xena-1 |
Changed in tripleo: | |
milestone: | xena-1 → xena-2 |
To post a comment you must log in.
Related fix proposed to branch: stable/ussuri /review. opendev. org/c/openstack /tripleo- common/ +/786901
Review: https:/