Neutron prevents us to change public_network.cidr on unlock settings

Bug #1587897 reported by Alexander Kurenyshev on 2016-06-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
High
Fuel Documentation Team
Mitaka
High
Evgeny Konstantinov

Bug Description

Steps to reproduce:
1) Create a cluster
2) Deploy the cluster
3) Change a public network cidr
4) Redeploy the cluster

Expected result:
Redeploy passed

Actual result:
Redeploy failed with error: Deployment has failed. All nodes are finished. Failed tasks: Task[openstack-network-networks/1] Stopping the deployment process!

Snapshot is here https://drive.google.com/file/d/0BzdDsIW-ymG2RU5ERWtZSmFqQk0/view?usp=sharing

[root@nailgun ~]# shotgun2 short-report
cat /etc/fuel_build_id:
 416
cat /etc/fuel_build_number:
 416
cat /etc/fuel_release:
 9.0
cat /etc/fuel_openstack_version:
 mitaka-9.0
rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun':
 fuel-release-9.0.0-1.mos6347.noarch
 fuel-bootstrap-cli-9.0.0-1.mos284.noarch
 fuel-migrate-9.0.0-1.mos8398.noarch
 rubygem-astute-9.0.0-1.mos746.noarch
 fuel-provisioning-scripts-9.0.0-1.mos8709.noarch
 network-checker-9.0.0-1.mos72.x86_64
 fuel-mirror-9.0.0-1.mos137.noarch
 fuel-openstack-metadata-9.0.0-1.mos8709.noarch
 fuel-notify-9.0.0-1.mos8398.noarch
 nailgun-mcagents-9.0.0-1.mos746.noarch
 python-fuelclient-9.0.0-1.mos316.noarch
 fuelmenu-9.0.0-1.mos270.noarch
 fuel-9.0.0-1.mos6347.noarch
 fuel-utils-9.0.0-1.mos8398.noarch
 fuel-setup-9.0.0-1.mos6347.noarch
 fuel-library9.0-9.0.0-1.mos8398.noarch
 shotgun-9.0.0-1.mos90.noarch
 fuel-agent-9.0.0-1.mos284.noarch
 fuel-ui-9.0.0-1.mos2706.noarch
 fuel-ostf-9.0.0-1.mos934.noarch
 fuel-misc-9.0.0-1.mos8398.noarch
 python-packetary-9.0.0-1.mos137.noarch
 fuel-nailgun-9.0.0-1.mos8709.noarch

Maksim Malchuk (mmalchuk) wrote :

Lowering to High because this doesn't affect the standard deploy.

no longer affects: fuel/newton
Changed in fuel:
importance: Critical → High
status: New → Confirmed
tags: added: area-library team-network
Changed in fuel:
assignee: Fuel Sustaining (fuel-sustaining-team) → Kyrylo Galanov (kgalanov)
Kyrylo Galanov (kgalanov) wrote :

2016-05-31 15:20:40 +0000 Puppet (err): Property cidr does not support being updated

It is a restriction of puppet-neutron module:
https://github.com/openstack/puppet-neutron/blob/master/lib/puppet/provider/neutron_subnet/neutron.rb#L259-L269

Kyrylo Galanov (kgalanov) wrote :

2016-05-31 15:20:40 +0000 /Stage[main]/Openstack_tasks::Openstack_network::Networks/Neutron_subnet[admin_floating_net__subnet]
/cidr (err): change from 10.109.30.0/24 to 10.109.30.0/25 failed: Property cidr does not support being updated

Changed in fuel:
assignee: Kyrylo Galanov (kgalanov) → MOS Puppet Team (mos-puppet)
Kyrylo Galanov (kgalanov) wrote :

Hi mos-puppet team,

Could you please provide assistance is resolving an issue? Is it possible to change mentioned network parameters after the first cluster deployment? Perhaps, replacing subnet instead of modifying could help?

Otherwise, forward issue to UI/Doc teams to tackle the problem.

Best regards,
Kyrylo

Sergey Kolekonov (skolekonov) wrote :

CIDR is a read-only value by design:

root@node-4:/etc/puppet/modules/neutron# neutron subnet-update admin_floating_net__subnet --cidr 172.18.161.0/25
Cannot update read-only attribute cidr

Complete subnet removing/replacing looks like a hack - it will require removal of all related artifacts (floating IPs, router gateways, ports and so on). I think it should be addressed in docs/UI

Changed in fuel:
assignee: MOS Puppet Team (mos-puppet) → Fuel Documentation Team (fuel-docs)
tags: added: area-docs
removed: area-library

Fix proposed to branch: master
Change author: Evgeny Konstantinov <email address hidden>
Review: https://review.fuel-infra.org/22064

Reviewed: https://review.fuel-infra.org/22064
Submitter: Evgeny Konstantinov <email address hidden>
Branch: master

Commit: 3dcb38b27add47dd83c5d53a89c304cba6378532
Author: Evgeny Konstantinov <email address hidden>
Date: Wed Jun 15 12:40:34 2016

Add CIDR is read-only known issue

Change-Id: I619c2edcf8b5d94622b33a7636732afffc70234e
Closes-Bug:#1587897

Related fix proposed to branch: master
Change author: Evgeny Konstantinov <email address hidden>
Review: https://review.fuel-infra.org/22317

Aleksey Kasatkin (alekseyk-ru) wrote :

I suppose it will be the same issue with Floating range and Public GW. Please comment whether it can be an issue.

Reviewed: https://review.fuel-infra.org/22317
Submitter: Evgeny Konstantinov <email address hidden>
Branch: master

Commit: 3efec3275f772c0c41c01d2a5013c596463a24fa
Author: Evgeny Konstantinov <email address hidden>
Date: Wed Jun 22 12:58:01 2016

Add Fuel known issues to relnotes 9.0

Change-Id: I9130ecc87d013db29e8a170911e59de0631a0222
Related-Bug: #1587897
Related-Bug: #1450100
Related-Bug: #1490597
Related-Bug: #1466431
Related-Bug: #1419201

Vladimir Eremin (yottatsa) wrote :

CIDR could be updated using PD mechanism, and actually, there is a code to make it updatable.

https://bugs.launchpad.net/neutron/+bug/1605343

Vladimir Eremin (yottatsa) wrote :

https://review.openstack.org/345594 [WIP] Update CIDR for subnet

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers