System triggered playbooks fail to pull images from AWS ECR if docker proxy is not configured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Tee Ngo |
Bug Description
Brief Description
-----------------
System triggered playbooks such as upgrade-
Severity
--------
Major
Steps to Reproduce
------------------
1. Bring up either an AIODX or a distributed cloud system using AWS registry and without docker http and/or https proxy.
2. Upgrade to N+1 load in which some of the system images are up-versioned.
The issue can also be observed simply by performing a controller swact and check sysinv.log
Expected Behavior
------------------
Upgrade completes successfully
Actual Behavior
----------------
Upgrade failed with the following error in sysinv log
TASK [common/
fatal: [localhost]: FAILED! => {"msg": "The field 'environment' has an invalid value, which includes an undefined variable. The error was: 'docker_http_proxy' is undefined\n\nThe error appears to have been in '/usr/share/
The same error log can also be seen with controller swact as the upgrade-
Reproducibility
---------------
Readily reproducible
System Configuration
-------
Any system type
Branch/Pull Time/Commit
-------
Jan 7th, 2021 master load
Last Pass
---------
Never. This is a test escape
Timestamp/Logs
--------------
See above
Test Activity
-------------
Developer Testing
Workaround
----------
Abort the upgrade, manually pull the new images, push them to the registry and resume the upgrade
Changed in starlingx: | |
assignee: | nobody → Tee Ngo (teewrs) |
Changed in starlingx: | |
importance: | Undecided → Medium |
status: | New → Triaged |
tags: | added: stx.5.0 stx.update |
https:/ /review. opendev. org/c/starlingx /ansible- playbooks/ +/770061