9:07 a.m.
I am looking for help in properly configuring a TripleO environment on a
machine with two network cards talking to two baremetal nodes in the
overcloud also with two network cards. One network will be for
provisioning and one will be for internet connection. I have documented
my current configuration at:
https://fedoraproject.org/wiki/User:Hamzy/TripleO_mixed_undercloud_overcl...
2017-09-23 23:54:49Z [overcloud.ControllerAllNodesValidationDeployment.0]:
CREATE_COMPLETE state changed
2017-09-23 23:54:49Z [overcloud.ControllerAllNodesValidationDeployment]:
CREATE_COMPLETE Stack CREATE completed successfully
2017-09-23 23:54:49Z [overcloud.ControllerAllNodesValidationDeployment]:
CREATE_COMPLETE state changed
2017-09-24 00:05:06Z [overcloud.ComputeAllNodesValidationDeployment.0]:
SIGNAL_IN_PROGRESS Signal: deployment d54b96a6-1860-4802-a$
45-db4ece0317e4 failed (1)
2017-09-24 00:05:06Z [overcloud.ComputeAllNodesValidationDeployment.0]:
CREATE_FAILED Error: resources[0]: Deployment to server fa$led:
deploy_status_code : Deployment exited with non-zero status code: 1
2017-09-24 00:05:06Z [overcloud.ComputeAllNodesValidationDeployment]:
CREATE_FAILED Resource CREATE failed: Error: resources[0]: D$ployment to
server failed: deploy_status_code : Deployment exited with non-zero status
code: 1
2017-09-24 00:05:07Z [overcloud.ComputeAllNodesValidationDeployment]:
CREATE_FAILED Error:
resources.ComputeAllNodesValidationDepl$yment.resources[0]: Deployment to
server failed: deploy_status_code: Deployment exited with non-zero status
code: 1
2017-09-24 00:05:07Z [overcloud]: CREATE_FAILED Resource CREATE failed:
Error: resources.ComputeAllNodesValidationDeployment.resou$ces[0]:
Deployment to server failed: deploy_status_code: Deployment exited with
non-zero status code: 1
Stack overcloud CREATE_FAILED
overcloud.ComputeAllNodesValidationDeployment.0:
resource_type: OS::Heat::StructuredDeployment
physical_resource_id: d54b96a6-1860-4802-ad45-db4ece0317e4
status: CREATE_FAILED
status_reason: |
Error: resources[0]: Deployment to server failed: deploy_status_code :
Deployment exited with non-zero status code: 1
deploy_stdout: |
...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
FAILURE
(truncated, view all with --long)
deploy_stderr: |
172.16.0.14 is not pingable. Local Network: 172.16.0.0/24
--
Mark
You must be the change you wish to see in the world. -- Mahatma Gandhi
Never let the future disturb you. You will meet it, if you have to, with
the same weapons of reason which today arm you against the present. --
Marcus Aurelius
10:06 a.m.
Hi Mark,
Could you also post the network configuration files you are using for the
overcloud deployment, e.g.
- network-environment.yaml
- network-isolation-custom.yaml
- any nic config files used by network-environment.yaml
It looks like you are using an isolated network that is not reachable
(172.16.0.14).
Also, did you run introspection on these nodes?
Thanks,
Bob
On Mon, Oct 9, 2017 at 10:07 AM, Mark Hamzy <hamzy(a)us.ibm.com> wrote:
I am looking for help in properly configuring a TripleO environment
on a
machine with two network cards talking to two baremetal nodes in the
overcloud also with two network cards. One network will be for
provisioning and one will be for internet connection. I have documented my
current configuration at:
https://fedoraproject.org/wiki/User:Hamzy/TripleO_mixed_
undercloud_overcloud_try8
2017-09-23 23:54:49Z [overcloud.ControllerAllNodesValidationDeployment.0]:
CREATE_COMPLETE state changed
2017-09-23 23:54:49Z [overcloud.ControllerAllNodesValidationDeployment]:
CREATE_COMPLETE Stack CREATE completed successfully
2017-09-23 23:54:49Z [overcloud.ControllerAllNodesValidationDeployment]:
CREATE_COMPLETE state changed
2017-09-24 00:05:06Z [overcloud.ComputeAllNodesValidationDeployment.0]:
SIGNAL_IN_PROGRESS Signal: deployment d54b96a6-1860-4802-a$
45-db4ece0317e4 failed (1)
2017-09-24 00:05:06Z [overcloud.ComputeAllNodesValidationDeployment.0]:
CREATE_FAILED Error: resources[0]: Deployment to server fa$led:
deploy_status_code : Deployment exited with non-zero status code: 1
2017-09-24 00:05:06Z [overcloud.ComputeAllNodesValidationDeployment]:
CREATE_FAILED Resource CREATE failed: Error: resources[0]: D$ployment to
server failed: deploy_status_code : Deployment exited with non-zero status
code: 1
2017-09-24 00:05:07Z [overcloud.ComputeAllNodesValidationDeployment]:
CREATE_FAILED Error: resources.ComputeAllNodesValidationDepl$yment.resources[0]:
Deployment to server failed: deploy_status_code: Deployment exited with
non-zero status code: 1
2017-09-24 00:05:07Z [overcloud]: CREATE_FAILED Resource CREATE failed:
Error: resources.ComputeAllNodesValidationDeployment.resou$ces[0]:
Deployment to server failed: deploy_status_code: Deployment exited with
non-zero status code: 1
Stack overcloud CREATE_FAILED
overcloud.ComputeAllNodesValidationDeployment.0:
resource_type: OS::Heat::StructuredDeployment
physical_resource_id: d54b96a6-1860-4802-ad45-db4ece0317e4
status: CREATE_FAILED
status_reason: |
Error: resources[0]: Deployment to server failed: deploy_status_code :
Deployment exited with non-zero status code: 1
deploy_stdout: |
...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
Ping to 172.16.0.14 failed. Retrying...
FAILURE
(truncated, view all with --long)
deploy_stderr: |
172.16.0.14 is not pingable. Local Network: 172.16.0.0/24
--
Mark
You must be the change you wish to see in the world. -- Mahatma Gandhi
Never let the future disturb you. You will meet it, if you have to, with
the same weapons of reason which today arm you against the present. --
Marcus Aurelius
_______________________________________________
rdo-list mailing list
rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
10:49 a.m.
Bob Fournier <bfournie(a)redhat.com> wrote on 10/09/2017 10:06:20 AM:
Could you also post the network configuration files you are using
for the overcloud deployment, e.g.
- network-environment.yaml
- network-isolation-custom.yaml
- any nic config files used by network-environment.yaml
Burried somewhat in that URL was the following:
cp -r /usr/share/openstack-tripleo-heat-templates templates
(cd templates/; wget --quiet -O - h
ttps://hamzy.fedorapeople.org/openstack-tripleo-heat-templates.patch |
patch -p1)
Is the patch file enough for people to view the configuration files?
It looks like you are using an isolated network that is not
reachable (172.16.0.14).
Also, did you run introspection on these nodes?
Well, the overcloud nodes are ppc64le machines and introspection does not
work correctly yet IIRC. However, they both do deploy and I can watch
that process on the consoles. They do get IPs from DHCP.
[hamzy@overcloud-controller-0 ~]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enP1p3s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq
portid 98be9454b240 state DOWN qlen 1000
link/ether 98:be:94:54:b2:40 brd ff:ff:ff:ff:ff:ff
3: enP1p3s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq
portid 98be9454b242 state DOWN qlen 1000
link/ether 98:be:94:54:b2:42 brd ff:ff:ff:ff:ff:ff
4: enP1p5s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq
portid 98be94546360 state DOWN qlen 1000
link/ether 98:be:94:54:63:60 brd ff:ff:ff:ff:ff:ff
5: enP1p5s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq
portid 98be94546362 state DOWN qlen 1000
link/ether 98:be:94:54:63:62 brd ff:ff:ff:ff:ff:ff
6: enP3p11s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq
portid 40f2e9316940 state DOWN qlen 1000
link/ether 40:f2:e9:31:69:40 brd ff:ff:ff:ff:ff:ff
7: enP3p11s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq
portid 40f2e9316942 state DOWN qlen 1000
link/ether 40:f2:e9:31:69:42 brd ff:ff:ff:ff:ff:ff
8: enP6p1s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq
portid 98be94541f80 state DOWN qlen 1000
link/ether 98:be:94:54:1f:80 brd ff:ff:ff:ff:ff:ff
9: enP6p1s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq
portid 98be94541f82 state DOWN qlen 1000
link/ether 98:be:94:54:1f:82 brd ff:ff:ff:ff:ff:ff
10: enP3p5s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq
portid 0100000000304534323130363730453131 state DOWN qlen 1000
link/ether 00:90:fa:74:05:50 brd ff:ff:ff:ff:ff:ff
11: enP3p5s0f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq
portid 0200000000304534323130363730453131 state DOWN qlen 1000
link/ether 00:90:fa:74:05:51 brd ff:ff:ff:ff:ff:ff
12: enP3p5s0f2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master
ovs-system portid 0300000000304534323130363730453131 state UP qlen 1000
link/ether 00:90:fa:74:05:52 brd ff:ff:ff:ff:ff:ff
inet6 fe80::290:faff:fe74:552/64 scope link
valid_lft forever preferred_lft forever
13: enP3p5s0f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq portid
0400000000304534323130363730453131 state UP qlen 1000
link/ether 00:90:fa:74:05:53 brd ff:ff:ff:ff:ff:ff
inet 9.114.118.245/24 brd 9.114.118.255 scope global dynamic
enP3p5s0f3
valid_lft 64400sec preferred_lft 64400sec
inet6 fe80::290:faff:fe74:553/64 scope link
valid_lft forever preferred_lft forever
14: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen
1000
link/ether e2:41:9f:8c:f8:62 brd ff:ff:ff:ff:ff:ff
15: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN qlen 1000
link/ether 00:90:fa:74:05:52 brd ff:ff:ff:ff:ff:ff
inet 9.114.118.245/24 brd 9.114.118.255 scope global br-ex
valid_lft forever preferred_lft forever
inet6 fd55:faaf:e1ab:3d9:290:faff:fe74:552/64 scope global mngtmpaddr
dynamic
valid_lft 2591857sec preferred_lft 604657sec
inet6 fe80::290:faff:fe74:552/64 scope link
valid_lft forever preferred_lft forever
16: vlan10: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN qlen 1000
link/ether ce:fa:f3:36:e9:bb brd ff:ff:ff:ff:ff:ff
inet 10.0.0.18/24 brd 10.0.0.255 scope global vlan10
valid_lft forever preferred_lft forever
inet6 fe80::ccfa:f3ff:fe36:e9bb/64 scope link
valid_lft forever preferred_lft forever
17: vlan20: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN qlen 1000
link/ether e2:59:d0:45:4b:2e brd ff:ff:ff:ff:ff:ff
inet 172.17.0.20/24 brd 172.17.0.255 scope global vlan20
valid_lft forever preferred_lft forever
inet6 fe80::e059:d0ff:fe45:4b2e/64 scope link
valid_lft forever preferred_lft forever
18: vlan30: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN qlen 1000
link/ether 32:b7:a2:9c:f9:c7 brd ff:ff:ff:ff:ff:ff
inet 172.18.0.13/24 brd 172.18.0.255 scope global vlan30
valid_lft forever preferred_lft forever
inet6 fe80::30b7:a2ff:fe9c:f9c7/64 scope link
valid_lft forever preferred_lft forever
19: vlan40: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN qlen 1000
link/ether 8e:e0:a7:a6:ba:f5 brd ff:ff:ff:ff:ff:ff
inet 172.19.0.10/24 brd 172.19.0.255 scope global vlan40
valid_lft forever preferred_lft forever
inet6 fe80::8ce0:a7ff:fea6:baf5/64 scope link
valid_lft forever preferred_lft forever
20: vlan50: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state
UNKNOWN qlen 1000
link/ether 4e:d6:7e:d8:45:da brd ff:ff:ff:ff:ff:ff
inet 172.16.0.14/24 brd 172.16.0.255 scope global vlan50
valid_lft forever preferred_lft forever
inet6 fe80::4cd6:7eff:fed8:45da/64 scope link
valid_lft forever preferred_lft foreve
2400
days inactive
2400
days old
2 comments
2 participants
participants (2)
-
Bob Fournier -
Mark Hamzy