Right now it's looking like we should add documentation for configuring an
override within the role
On Fri, Jul 13, 2018 at 4:08 PM, DimGR <email address hidden> wrote:
> hi ,
>
> for some reason your heat containers can not resolve the internal
> network . I think this is not a magnum bug but i will be keeping a close
> eye on this on my clusters and update if i see anything that relates to
> this
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1780385
>
> Title:
> [os_heat][pike] heat-container-agent fails to communicate with
> Keystone
>
> Status in openstack-ansible:
> Triaged
>
> Bug description:
> I'm not quite sure whether this is a bug or just configuration.
>
> I setup magnum with openstack-ansible. The cluster creation in magnum
> never finished because the heat-container-agent tried to connect to
> the internal keystone endpoint, which is not reachable from our VMs.
>
> This is the post which helped me to solve the problem:
> https://ask.openstack.org/en/question/102214/software-
> deployment-in-heat-problem-with-os-collect-config/
> Kolla already addressed the same problem: https://bugs.launchpad.net/
> kolla-ansible/+bug/1762754
>
> In my osa deployment, I could fix it with these overrides:
> heat_heat_conf_overrides:
> clients_keystone:
> endpoint_type: publicURL
> auth_uri: "{{ keystone_service_publicurl }}"
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openstack-ansible/+bug/1780385/+subscriptions
>
Right now it's looking like we should add documentation for configuring an
override within the role
On Fri, Jul 13, 2018 at 4:08 PM, DimGR <email address hidden> wrote:
> hi , /bugs.launchpad .net/bugs/ 1780385 agent fails to communicate with agent tried to connect to /ask.openstack. org/en/ question/ 102214/ software- in-heat- problem- with-os- collect- config/ /bugs.launchpad .net/ +bug/1762754 conf_overrides: service_ publicurl }}" /bugs.launchpad .net/openstack- ansible/ +bug/1780385/ +subscriptions
>
> for some reason your heat containers can not resolve the internal
> network . I think this is not a magnum bug but i will be keeping a close
> eye on this on my clusters and update if i see anything that relates to
> this
>
> --
> You received this bug notification because you are a bug assignee.
> https:/
>
> Title:
> [os_heat][pike] heat-container-
> Keystone
>
> Status in openstack-ansible:
> Triaged
>
> Bug description:
> I'm not quite sure whether this is a bug or just configuration.
>
> I setup magnum with openstack-ansible. The cluster creation in magnum
> never finished because the heat-container-
> the internal keystone endpoint, which is not reachable from our VMs.
>
> This is the post which helped me to solve the problem:
> https:/
> deployment-
> Kolla already addressed the same problem: https:/
> kolla-ansible/
>
> In my osa deployment, I could fix it with these overrides:
> heat_heat_
> clients_keystone:
> endpoint_type: publicURL
> auth_uri: "{{ keystone_
>
> To manage notifications about this bug go to:
> https:/
>