Bug 1399801 - Restoring of director fails [NEEDINFO]
Summary: Restoring of director fails
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: instack-undercloud
Version: 9.0 (Mitaka)
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: ---
: 9.0 (Mitaka)
Assignee: James Slagle
QA Contact: Arik Chernetsky
URL:
Whiteboard:
Depends On:
Blocks: 1321607 1373538
TreeView+ depends on / blocked
 
Reported: 2016-11-29 18:46 UTC by Satish
Modified: 2017-09-08 21:34 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-08 21:34:00 UTC
Target Upstream Version:
aschultz: needinfo? (satishv)


Attachments (Terms of Use)

Description Satish 2016-11-29 18:46:43 UTC
Description of problem:
the install aborted at post-configuration.
Undercloud installer at post config finds that cidr for pxe subnet is incorrect. This seem to be a bug in RH. And installer tried to delete all subnets, but fails as there are ports on these subnets. This resulting in abort.

Please also share you thoughts on service tuskar error.

Thanks
Satish



++ neutron subnet-show 3d066d86-97dd-4558-bccc-26d8e9d5ab18 -f value -c cidr^M
+ cidr=192.0.0.0/8^M
+ '[' 192.0.0.0/8 = 192.100.0.0/8 ']'^M
+ echo 'New cidr 192.100.0.0/8 does not equal old cidr 192.0.0.0/8'^M
New cidr 192.100.0.0/8 does not equal old cidr 192.0.0.0/8^M
+ echo 'Will attempt to delete and recreate subnet 3d066d86-97dd-4558-bccc-26d8e9d5ab18'^M
Will attempt to delete and recreate subnet 3d066d86-97dd-4558-bccc-26d8e9d5ab18^M
+ '[' 1 -eq 1 ']'^M
+ neutron subnet-list^M
+ grep start^M
| d72f9088-28be-4b58-a878-dffc9e4140aa | external_subnet     | 10.23.249.0/24 | {"start": "10.23.249.49", "end": "10.23.249.60"}   |^M
| 963b20f6-6419-48cf-879b-bfc2a2f577ea | storage_mgmt_subnet | 11.150.0.0/24  | {"start": "11.150.0.10", "end": "11.150.0.200"}    |^M
| a3772c62-bf9e-4494-ba8f-740b2fd6b95d | storage_subnet      | 11.120.0.0/24  | {"start": "11.120.0.10", "end": "11.120.0.200"}    |^M
| be30c3e6-eed3-4f30-bffd-aacb44bbb453 | tenant_subnet       | 11.130.0.0/24  | {"start": "11.130.0.10", "end": "11.130.0.200"}    |^M
| 484c9739-c813-4e43-958e-62c71224db09 | internal_api_subnet | 11.100.0.0/24  | {"start": "11.100.0.10", "end": "11.100.0.200"}    |^M
| 3d066d86-97dd-4558-bccc-26d8e9d5ab18 |                     | 192.0.0.0/8    | {"start": "192.100.0.110", "end": "192.100.0.170"} |^M
++ neutron subnet-list^M
++ grep start^M
++ awk '{print $2}'^M
+ neutron subnet-delete be30c3e6-eed3-4f30-bffd-aacb44bbb453 484c9739-c813-4e43-958e-62c71224db09 d72f9088-28be-4b58-a878-dffc9e4140aa 963b20f6-6419-48cf-879b-bfc2a2f577ea a3772c62-bf9e-4494-ba8f-740b2fd6b95d 3d066d86-97dd-4558-bccc-26d8e9d5ab18^M
Unable to complete operation on subnet be30c3e6-eed3-4f30-bffd-aacb44bbb453: One or more ports have an IP allocation from this subnet.^M
Neutron server returns request_ids: ['req-9476a889-1ba7-41d3-b5c5-ce0647a1ec7e']^M
[2016-11-28 22:25:32,267] (os-refresh-config) [ERROR] during post-configure phase. [Command '['dib-run-parts', '/usr/libexec/os-refresh-config/post-configure.d']' returned non-zero exit status 1]^M
^M
[2016-11-28 22:25:32,268] (os-refresh-config) [ERROR] Aborting...^M
Traceback (most recent call last):^M
  File "<string>", line 1, in <module>^M
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 845, in install^M
    _run_orc(instack_env)^M
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 735, in _run_orc^M
    _run_live_command(args, instack_env, 'os-refresh-config')^M
  File "/usr/lib/python2.7/site-packages/instack_undercloud/undercloud.py", line 406, in _run_live_command^M
    raise RuntimeError('%s failed. See log for details.' % name)^M
RuntimeError: os-refresh-config failed. See log for details.^M
Command 'instack-install-undercloud' returned non-zero exit status 1^M
^[]0;stack@ucsb-monster:~^G[stack@ucsb-monster ~]$  exit^M
exit^M

Script done on Mon 28 Nov 2016 10:49:52 PM PST



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Alex Schultz 2017-03-01 20:45:15 UTC
Can you provide details around the state of the undercloud prior to running the install command? It seems like it was partially configured and then because the network cidr was changed on the subsequent run that it failed when it goes to try and delete & recreate the subnet.  Can you verify if this was the case?


Note You need to log in before you can comment on or make changes to this bug.