cannot apply a chart with local registry
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Al Bailey |
Bug Description
Brief Description
-----------------
Cannot deploy an application by helm chart upload which is pointing to an image on local registry
Severity
--------
Provide the severity of the defect.
Major: System/Feature is usable but degraded
Steps to Reproduce
------------------
1. Have a SXT deploymen up an running, with stx-openstack application correctly applied
2. Copy `hello-kitty.tgz` file (attached) to the active controller
3. Modify the `values.yaml` file adding the <REGISTRY IP> on:
- charts/
- charts/
as follows:
images:
pullPolicy: IfNotPresent
tags:
hellokitty: <REGISTRY_
3. on active controller do
$ . /etc/platform/
$ system application-upload -n hello-kitty -v 1.0 /home/sysadmin/
# wait until is uploaded correctly
$ system application-apply hello-kitty
Expected Behavior
------------------
Application should be applied correctly.
Actual Behavior
----------------
Application cannot be applied due cannot download images
NOTE: Note: If we do a `sudo docker pull : <REGISTRY_
======== Logs =======
2019-09-12 13:26:40.036 328907 INFO sysinv.
2019-09-12 13:26:41.306 330854 INFO sysinv.
2019-09-12 13:26:41.381 330854 INFO sysinv.
2019-09-12 13:26:43.448 330855 INFO sysinv.
2019-09-12 13:26:43.457 328907 INFO sysinv.
2019-09-12 13:26:43.586 328907 INFO sysinv.
2019-09-12 13:26:43.618 328907 INFO sysinv.
2019-09-12 13:26:43.682 328907 INFO sysinv.
2019-09-12 13:26:43.683 328907 INFO sysinv.
2019-09-12 13:26:43.784 328907 INFO sysinv.
2019-09-12 13:26:43.785 328907 ERROR sysinv.
2019-09-12 13:26:43.786 328907 ERROR sysinv.
2019-09-12 13:26:43.786 328907 TRACE sysinv.
2019-09-12 13:26:43.786 328907 TRACE sysinv.
2019-09-12 13:26:43.786 328907 TRACE sysinv.
2019-09-12 13:26:43.786 328907 TRACE sysinv.
2019-09-12 13:26:43.786 328907 TRACE sysinv.
2019-09-12 13:26:43.786 328907 TRACE sysinv.
2019-09-12 13:26:43.786 328907 TRACE sysinv.
2019-09-12 13:26:44.020 328907 ERROR sysinv.
2019-09-12 13:26:44.020 328907 INFO sysinv.
2019-09-12 13:26:44.021 328907 ERROR sysinv.
2019-09-12 13:26:44.021 328907 TRACE sysinv.
2019-09-12 13:26:44.021 328907 TRACE sysinv.
2019-09-12 13:26:44.021 328907 TRACE sysinv.
2019-09-12 13:26:44.021 328907 TRACE sysinv.
2019-09-12 13:26:44.021 328907 TRACE sysinv.
2019-09-12 13:26:44.021 328907 TRACE sysinv.
2019-09-12 13:26:44.021 328907 TRACE sysinv.
2019-09-12 13:26:44.021 328907 TRACE sysinv.
2019-09-12 13:26:44.021 328907 TRACE sysinv.
2019-09-12 13:26:44.021 328907 TRACE sysinv.
2019-09-12 13:26:44.021 328907 TRACE sysinv.
2019-09-12 13:26:44.021 328907 TRACE sysinv.
2019-09-12 13:26:44.021 328907 TRACE sysinv.
=======
Reproducibility
---------------
<Reproducible/
100%
System Configuration
-------
Multi-node system - Local Storage
Branch/Pull Time/Commit
-------
Last Pass
---------
First Time tested
Timestamp/Logs
--------------
File hello-kitty.tgz attached
Test Activity
-------------
Pytest automated suite enablement
Changed in starlingx: | |
importance: | Undecided → High |
status: | Incomplete → In Progress |
assignee: | nobody → Al Bailey (albailey1974) |
tags: | added: stx.2.0 stx.config stx.containers |
@Jose, You need to have an image secret in the application spec to be able to access the private registry. You haven't attached the yaml file, so we're suspecting you don't have an image secret defined.