Docker proxy service parameters cannot be changed without a lock unlock
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Jerry Sun |
Bug Description
Brief Description
-----------------
Changing OAM IP should be possible without a lock unlock. Changing OAM IP must be accompanied by a change to docker proxy config if the system is configured to use docker proxy. This means system configured with a Docker proxy cannot change the OAM IP without a lock unlock.
Severity
--------
Major
Steps to Reproduce
------------------
Configure system with docker proxy. Change OAM IP
Expected Behavior
------------------
Changes applied without any node lock unlocks
Actual Behavior
----------------
Docker login, push, and pull fails due to bad proxy setting. Changing proxy requires lock unlock
Reproducibility
---------------
100% reproducible
System Configuration
-------
All configurations
Branch/Pull Time/Commit
-------
2021-06-10 master branch
Workaround
----------
Lock and unlock the nodes with config out-of-date alarms to apply config changes
Note
----
The current service parameter does not allow differentiation at a "section" level. Service parameter should be enhanced to allow differentiation at a "section" level to ensure docker_proxy can be changed without a reboot while the various docker registry url settings still requires a reboot.
description: | updated |
Changed in starlingx: | |
assignee: | nobody → Jerry Sun (jerry-sun-u) |
tags: | added: stx.6.0 stx.config |
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.containers |
Fix proposed to branch: master /review. opendev. org/c/starlingx /stx-puppet/ +/795825
Review: https:/