[podman] Insecure registries not configured

Bug #1812966 reported by Martin Mágr on 2019-01-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
High
Unassigned

Bug Description

When using config [1] during deployment the insecure registries are not configured on overcloud nodes and so deployment fails. You have to modify /etc/containers/registries.conf manually to workaround this problem.

[1] (undercloud) [stack@undercloud ~]$ cat config.yaml
parameter_defaults:
  ContainerCli: podman
  DockerInsecureRegistryAddress:
    - 192.168.24.1:8787
(undercloud) [stack@undercloud ~]$

Martin Mágr (mmagr) on 2019-01-23
Changed in tripleo:
milestone: none → train-1
milestone: train-1 → stein-3
importance: Undecided → Critical
Changed in tripleo:
importance: Critical → High
status: New → Triaged
Emilien Macchi (emilienm) wrote :
Changed in tripleo:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers