Brief Description
-----------------
After initial install and config, platform-integ-apps occasionally in apply-failed status due to tiller unable to get release info.
The workaround is to re-apply the platform-integ-apps. The re-apply usually passes.
Severity
--------
Minor
Steps to Reproduce
------------------
Install and configure a stx system
Expected Behavior
------------------
- platform-integ-apps automatically applied successfully
Actual Behavior
----------------
- platform-integ-apps occasionally in apply-failed status due to tiller unable to get release info
Reproducibility
---------------
Rare - less than 10%
System Configuration
--------------------
One node system
Lab-name: SM-4
Branch/Pull Time/Commit
-----------------------
2019-10-27_20-00-00
Last Pass
---------
This is very intermittent. Don't know last pass. It is the first time seen in WR sanity in the past 1.5 weeks that I looked.
Timestamp/Logs
--------------
# platform-integ-apps failed before following timestamp
[2019-10-28 07:02:53,338] 311 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://192.168.204.1:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-endpoint-type internalURL --os-region-name RegionOne application-list'
+---------------------+---------+-------------------------------+---------------+--------------+------------------------------------------+
| application | version | manifest name | manifest file | status | progress |
+---------------------+---------+-------------------------------+---------------+--------------+------------------------------------------+
| platform-integ-apps | 1.0-9 | platform-integration-manifest | manifest.yaml | apply-failed | operation aborted, check logs for detail |
+---------------------+---------+-------------------------------+---------------+--------------+------------------------------------------+
# Comment from Robert Church:
Looks like tiller couldn’t get release information which is why the apply failed.
{"log":"[main] 2019/10/28 06:56:29 Starting Tiller v2.13.1 (tls=false)\n","stream":"stderr","time":"2019-10-28T06:56:29.952167656Z"}
{"log":"[main] 2019/10/28 06:56:29 GRPC listening on :44134\n","stream":"stderr","time":"2019-10-28T06:56:29.952227906Z"}
{"log":"[main] 2019/10/28 06:56:29 Probes listening on :44135\n","stream":"stderr","time":"2019-10-28T06:56:29.95223832Z"}
{"log":"[main] 2019/10/28 06:56:29 Storage driver is ConfigMap\n","stream":"stderr","time":"2019-10-28T06:56:29.952245037Z"}
{"log":"[main] 2019/10/28 06:56:29 Max history per release is 0\n","stream":"stderr","time":"2019-10-28T06:56:29.952251347Z"}
{"log":"[storage] 2019/10/28 06:59:50 listing all releases with filter\n","stream":"stderr","time":"2019-10-28T06:59:50.862282171Z"}
{"log":"[storage/driver] 2019/10/28 06:59:52 list: failed to list: the server could not find the requested resource (get configmaps)\n","stream":"stderr","time":"2019-10-28T06:59:52.094561718Z"}
Test Activity
-------------
Sanity
stx.3.0 / medium priority - should be investigated further