push_destination: true doesn't work when deploying a standalone node.
Bug #1859757 reported by
Cédric Jeanneret
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Triaged
|
Medium
|
Yadnesh Kulkarni | ||
Bug Description
Hello there,
When deploying a standalone node and using the default containers-prepare parameters, it fails during the deploy due to the difference between the called things:
- httpd VirtualHost for image-serve is 192.168.24.2:8787
- if we run the container prepare command it generates with undercloud.
- finally, the deploy itself is using "localhost"
In order to solve this situation, we must set the "push_destination" to 192.168.24.2:8787 so that it matches the httpd vhost.
This isn't necessary when deploying an undercloud, and creates an annoying inconsistency in the standard deploy workflow.
Care to have a look?
Cheers,
C.
| Changed in tripleo: | |
| milestone: | ussuri-3 → ussuri-rc3 |
| Changed in tripleo: | |
| milestone: | ussuri-rc3 → victoria-1 |
| Changed in tripleo: | |
| milestone: | victoria-1 → victoria-3 |
Revision history for this message
| Yadnesh Kulkarni (ykulkarn) wrote | #1 |
| Changed in tripleo: | |
| assignee: | nobody → Yadnesh Kulkarni (ykulkarn) |
To post a comment you must log in.
Is substituting the httpd VirtualHost instead of True in tripleoclient the correct approach here ?
941 if parsed_
942 for entry in cip:
943 entry['
944 params = {
945 'ContainerImage
946 }