Bug 974222
Summary: | Cloud-init various fails obtain instance-id | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Jaroslav Henner <jhenner> |
Component: | distribution | Assignee: | RHOS Maint <rhos-maint> |
Status: | CLOSED WORKSFORME | QA Contact: | Ami Jeain <ajeain> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.0 | CC: | markmc, yeylon |
Target Milestone: | --- | ||
Target Release: | 4.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-13 19:11:14 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jaroslav Henner
2013-06-13 17:35:08 UTC
Also note that during the time the cloud-init has problems, claiming "no route to host", the instance is pingable. The problem is that cloud-init adds temporary routing rule, saying that the 169.254.0.0/16 is local, therefore the packets are not routed to gateway from the sending machine, but ARP requests are being sent: 13:53:02.634932 ARP, Request who-has 169.254.169.254 tell 10.34.64.7, length 28 Nothing replies since there is no such listener (there is only NAT rule on the controller). The sender than realizes there is no route to host. I believe this problem is not present when using nova-network, but I would need confirmation. I think I had some problem in my deployment. |