Bug 1574473
| Summary: | Failled to scale up upgraded overcloud | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Yurii Prokulevych <yprokule> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Emilien Macchi <emacchi> |
| Status: | CLOSED EOL | QA Contact: | Gurenko Alex <agurenko> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 11.0 (Ocata) | CC: | aschultz, augol, bfournie, ccamacho, ebarrera, mburns, mcornea |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-06-22 12:38:44 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
Yurii Prokulevych
2018-05-03 11:42:09 UTC
Regarding: May 03 07:30:22 compute-2 os-collect-config[3052]: /usr/libexec/os-refresh-config/configure.d/20-os-net-config: line 81: /etc/os-net-config/dhcp_all_interfaces.yaml: No such file or directory Since 20-os-net-config is actually creating /etc/os-net-config/dhcp_all_interfaces.yaml starting at line 55, the only way that error message would occur is if /etc/os-net-config/ did not exist. Need to track down where this dir is getting created and why it would not when scaling up in this case. It appears that the logs for compute-2 are not in the Build artifacts link. I only see compute-0 and compute-1. Can you indicate where the logs were obtained in the initial bug comment? @Bob, scale up failed so inventory wasn't updated properly, hence logs collection failed:
fatal: [compute-2]: FAILED! => {
"changed": false,
"module_stderr": "Shared connection to 172.16.0.11 closed.\r\n",
"module_stdout": "Please login as the user \"heat-admin\" rather than the user \"root\".\r\n\r\n",
"rc": 0
}
>Bob, You are also talking about old/new format. Can you point me about an example of >each one ? I dont know which one I'm using In Ocata the nic config files were changed to use a script instead of the os-apply-config to drive os-net-config. The "old-style" nic config files could be identified by: Software Config to drive os-net-config to configure multiple interfaces group: os-apply-config While the "new-style" doesn't use os-apply-config, instead it includes the script: str_replace: template: get_file: ../../scripts/run-os-net-config.sh The old-style was still supported until Queens. In Queens a script is available in $THT/tools/yaml-nic-config-2-script.py to do the conversion. We've seen some issues when upgrading and using the new-style configs in that /etc/os-net-config/config.json was overwritten by os-apply-config, e.g. - https://bugzilla.redhat.com/show_bug.cgi?id=1514949. Not sure yet what is going on here or if the problem you are seeing is the same as comment 3. Would be useful to get some logs to help figure out what is going on. Yuri - the 2nd set of logs looks quite different from the first, I don't see the os-net-config issues from the initial description. I do see many connectivity issues when trying to access the metadata server from controller-2 I also see these libvirt issues in /var/log/messages on controller-2, which may be causing problems. messages:May 11 13:58:06 controller-2 libvirtd: 2018-05-11 17:58:06.846+0000: 1649: error : logStrToLong_ui:2564 : Failed to convert 'virtio0' to unsigned int messages:May 11 13:58:06 controller-2 libvirtd: 2018-05-11 17:58:06.849+0000: 1649: error : virPCIGetDeviceAddressFromSysfsLink:2643 : internal error: Failed to parse PCI config address 'virtio0' messages:May 11 13:58:06 controller-2 libvirtd: 2018-05-11 17:58:06.850+0000: 1649: error : logStrToLong_ui:2564 : Failed to convert 'virtio1' to unsigned int messages:May 11 13:58:06 controller-2 libvirtd: 2018-05-11 17:58:06.850+0000: 1649: error : virPCIGetDeviceAddressFromSysfsLink:2643 : internal error: Failed to parse PCI config address 'virtio1' messages:May 11 13:58:06 controller-2 libvirtd: 2018-05-11 17:58:06.852+0000: 1649: error : logStrToLong_ui:2564 : Failed to convert 'virtio2' to unsigned int messages:May 11 13:58:06 controller-2 libvirtd: 2018-05-11 17:58:06.852+0000: 1649: error : virPCIGetDeviceAddressFromSysfsLink:2643 : internal error: Failed to parse PCI config address 'virtio2' messages:May 11 21:11:38 controller-2 libvirtd: 2018-05-11 21:11:38.808+0000: 2289: error : logStrToLong_ui:2564 : Failed to convert 'virtio0' to unsigned int messages:May 11 21:11:38 controller-2 libvirtd: 2018-05-11 21:11:38.809+0000: 2289: error : virPCIGetDeviceAddressFromSysfsLink:2643 : internal error: Failed to parse PCI config address 'virtio0' messages:May 11 21:11:38 controller-2 libvirtd: 2018-05-11 21:11:38.812+0000: 2289: error : logStrToLong_ui:2564 : Failed to convert 'virtio1' to unsigned int messages:May 11 21:11:38 controller-2 libvirtd: 2018-05-11 21:11:38.812+0000: 2289: error : virPCIGetDeviceAddressFromSysfsLink:2643 : internal error: Failed to parse PCI config address 'virtio1' messages:May 11 21:11:38 controller-2 libvirtd: 2018-05-11 21:11:38.813+0000: 2289: error : logStrToLong_ui:2564 : Failed to convert 'virtio2' to unsigned int messages:May 11 21:11:38 controller-2 libvirtd: 2018-05-11 21:11:38.813+0000: 2289: error : virPCIGetDeviceAddressFromSysfsLink:2643 : internal error: Failed to parse PCI config address 'virtio2' OSP11 is now retired, see details at https://access.redhat.com/errata/product/191/ver=11/rhel---7/x86_64/RHBA-2018:1828 |