baremetal role fails to fetch docker gpg key behind proxy
Bug #1633131 reported by
Paul Bourke
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla |
Expired
|
Undecided
|
Unassigned |
Bug Description
Workaround:
diff --git a/ansible/
index 4399322..5314214 100644
--- a/ansible/
+++ b/ansible/
@@ -116,6 +116,10 @@
rpm_key:
state: present
key: "{{ docker_yum_url }}/gpg"
+ validate_certs: False
+ environment:
+ http_proxy: x.x.x.x
+ https_proxy: x.x.x.x
become: True
when: ansible_os_family == 'RedHat'
Need a robust way of allowing for this in the task
Changed in kolla: | |
importance: | Undecided → High |
status: | New → Confirmed |
milestone: | none → ocata-1 |
Changed in kolla: | |
milestone: | ocata-1 → ocata-2 |
Changed in kolla: | |
milestone: | ocata-2 → ocata-3 |
Changed in kolla: | |
milestone: | ocata-3 → ocata-rc1 |
Changed in kolla: | |
milestone: | ocata-rc1 → pike-1 |
Changed in kolla: | |
milestone: | pike-2 → pike-3 |
Changed in kolla: | |
milestone: | pike-3 → pike-rc1 |
Changed in kolla: | |
milestone: | pike-rc1 → queens-1 |
Changed in kolla: | |
milestone: | queens-2 → queens-3 |
Changed in kolla: | |
milestone: | queens-3 → queens-rc1 |
Changed in kolla: | |
milestone: | queens-rc1 → queens-rc2 |
Changed in kolla: | |
milestone: | queens-rc2 → rocky-1 |
To post a comment you must log in.
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
Valid example: CONFIRMED FOR: OCATA