Backup & Restore doesn't work with private registry if it's configured at Ansible bootstrap
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Ovidiu Poncea |
Bug Description
Brief Description
-----------------
Backup& restore won't work with private registry if it's configured during Ansible bootstrap.
The related code in backup playbooks doesn't handle it correctly.
e.g.
roles/backup/
- block:
- name: Search for docker registries
shell: >-
grep -w registry {{ tempdir.path }}/docker.txt |
awk '{if ($6=="registry") print $8 ".io: " $10}'
register: docker_registries
- block:
- name: Write docker_registries
dest: "{{ override_
line: "docker_
- name: Write docker_registry to override backup file
dest: "{{ override_
line: " {{ item }}"
...
1. The check '$6 == registry' is out of date as the section moved from 'registry' to 'quay-registry', 'k8s-registry', 'docker-registry', 'gcr-registry', 'elastic-registry' in service-parameter
e.g.
[sysadmin@
| a0d31309-
| 531f6845-
| 638b4ae9-
| e454e062-
| a0d32434-
2. The format of registry info written into backup file is not right since the format was changed in bootstrap overrides.
e.g.
The new format:
docker_registries:
docker.io:
url:
gcr.io:
url:
...
3. More parameters added in each registry entry under docker_registries as well, need to be handled as well.
e.g.
docker_registries:
docker.io:
url:
type:
username:
password:
additional_
tags: | added: stx.update |
summary: |
- Backup&restore doesn't work with private registry if it's configured at - Ansible bootstrap + Backup & Restore doesn't work with private registry if it's configured + at Ansible bootstrap |
Marking as stx.3.0 / high priority - B&R is an stx.3.0 feature deliverable