IBM Cloud Private - 加载图表时出错

Question

我安装了 IBM Cloud Private CE 2.1.0.1 以在虚拟 Ubuntu Server 环境中进行一些测试。在仪表板中，我无法打开目录 / Helm 图表。加载屏幕几秒钟后，会出现一条错误消息“加载图表时出错”。

有什么解决办法吗？

编辑

我的 helm-api pod 的日志：

2018-02-22T11:14:59.194Z 'FINE' 'repos/ GET entry'
2018-02-22T11:14:59.193Z 'FINE' 'inspect-client -> redirecting to `next`'
2018-02-22T11:14:59.195Z 'FINE' 'charts GET /'
2018-02-22T11:14:59.195Z 'FINE' 'getAllRepoUrlsFromDb'
2018-02-22T11:14:59.195Z 'FINE' 'inspect-client -> redirecting to `next`'
 [0mGET /helm-api/api/v1/repos  [32m200  [0m34.874 ms - 301 [0m
2018-02-22T11:15:03.716Z 'FINE' 'loadMessages en'
2018-02-22T11:15:03.716Z 'FINE' 'getMessage ["statusCode",200] en '
2018-02-22T11:15:03.716Z 'FINE' 'GET /healthcheck'
 [0mGET /healthcheck  [32m200  [0m0.415 ms - 16 [0m
2018-02-22T11:15:13.716Z 'FINE' 'getMessage ["statusCode",200] en '
2018-02-22T11:15:13.716Z 'FINE' 'loadMessages en'
2018-02-22T11:15:13.716Z 'FINE' 'GET /healthcheck'
 [0mGET /healthcheck  [32m200  [0m0.449 ms - 16 [0m
2018-02-22T11:15:17.258Z 'FINE' 'dbHealthcheck \nrepoName: ibm-charts\n'
2018-02-22T11:15:17.258Z 'FINE' 'GET /healthcheck'
2018-02-22T11:15:17.265Z 'FINE' 'loadMessages en'
2018-02-22T11:15:17.265Z 'FINE' 'getMessage ["statusCode",200] en '
 [0mGET /healthcheck  [32m200  [0m7.318 ms - 16 [0m
 [0mGET /healthcheck  [32m200  [0m0.439 ms - 16 [0m
   [0mGET /healthcheck  [32m200  [0m0.424 ms - 16 [0m
2018-02-22T11:16:17.258Z 'FINE' 'GET /healthcheck'
2018-02-22T11:16:17.258Z 'FINE' 'dbHealthcheck \nrepoName: ibm-charts\n'
 [0mGET /healthcheck  [32m200  [0m6.147 ms - 16 [0m
2018-02-22T11:16:17.264Z 'FINE' 'getMessage ["statusCode",200] en '
2018-02-22T11:16:17.264Z 'FINE' 'loadMessages en'
2018-02-22T11:16:23.716Z 'FINE' 'getMessage ["statusCode",200] en '
2018-02-22T11:16:23.716Z 'FINE' 'loadMessages en'
2018-02-22T11:16:23.716Z 'FINE' 'GET /healthcheck'
 [0mGET /healthcheck  [32m200  [0m0.419 ms - 16 [0m
2018-02-22T11:16:33.716Z 'FINE' 'loadMessages en'
2018-02-22T11:16:33.716Z 'FINE' 'getMessage ["statusCode",200] en '
2018-02-22T11:16:33.716Z 'FINE' 'GET /healthcheck'
 [0mGET /healthcheck  [32m200  [0m0.455 ms - 16 [0m
2018-02-22T11:16:43.716Z 'FINE' 'loadMessages en'
2018-02-22T11:16:43.716Z 'FINE' 'getMessage ["statusCode",200] en '
2018-02-22T11:16:43.716Z 'FINE' 'GET /healthcheck'
 [0mGET /healthcheck  [32m200  [0m0.373 ms - 16 [0m
2018-02-22T11:16:47.258Z 'FINE' 'dbHealthcheck \nrepoName: ibm-charts\n'
2018-02-22T11:16:47.258Z 'FINE' 'GET /healthcheck'
2018-02-22T11:16:47.265Z 'FINE' 'getMessage ["statusCode",200] en '
 [0mGET /healthcheck  [32m200  [0m8.673 ms - 16 [0m
2018-02-22T11:16:47.265Z 'FINE' 'loadMessages en'
2018-02-22T11:16:53.716Z 'FINE' 'getMessage ["statusCode",200] en '
2018-02-22T11:16:53.716Z 'FINE' 'GET /healthcheck'
2018-02-22T11:16:53.716Z 'FINE' 'loadMessages en'
 [0mGET /healthcheck  [32m200  [0m0.421 ms - 16 [0m
2018-02-22T11:17:03.720Z 'FINE' 'getMessage ["statusCode",200] en '
2018-02-22T11:17:03.720Z 'FINE' 'GET /healthcheck'
2018-02-22T11:17:03.720Z 'FINE' 'loadMessages en'
 [0mGET /healthcheck  [32m200  [0m0.435 ms - 16 [0m
2018-02-22T11:17:06.471Z 'ERROR' 'getChartsFromRepo(recursive) error:  connect ETIMEDOUT 151.101.112.133:443'
2018-02-22T11:17:13.716Z 'FINE' 'GET /healthcheck'
2018-02-22T11:17:13.716Z 'FINE' 'loadMessages en'
2018-02-22T11:17:13.716Z 'FINE' 'getMessage ["statusCode",200] en '

Answer 1

您可以从 ICP 控制台中删除默认的“ibm-charts”helm 存储库，然后单击“Sync repositories”以同步图表。网址是： ICP 主菜单 -> 管理 -> Helm 存储库

完成上述步骤后，“加载图表时出错”错误将消失。然后你可以参考 ICP 文档来管理 helm 图表： https://www.ibm.com/support/knowledgecenter/en/SSBS6K_2.1.0/app_center/app_center.html

Answer 2

一些类似的讨论：

ibm-cloud-private CE - 2.1.0 Catalog - Error Loading Charts

有时将其放置一段时间，它应该会解决。或者

[root@kvm-014170 ~]# kubectl -s 127.0.0.1:8888 -n kube-system get pods|grep helm                                                              *
helm-api-86494f54f4-4m2ss                                 1/1       Running    1                                                              31        57d
helmrepo-6ff49569b8-wfcbw                                 1/1       Running    1    

尝试杀死 helm-api 或 helmrepo pod 并等待它重新启动。

请使用搜索功能避免发布类似问题。