Juju未能部署服务

时间:2017-03-27 09:39:05

标签: ubuntu deployment cloud juju

我是Juju的新手,我正在尝试部署一个服务,其中SO是Ubuntu 16.10 yakkety,juju版本是2.0.2-yakkety-amd64。使用的云是手动,环境引导没有问题,并且机器被添加到云中。

因此,当我尝试将wordpress服务部署到添加的机器号0运行时,我遇到了问题:

juju deploy cs:wordpress/yakkety --to 0  --series yakkety --debug

但我支持公司代理,所以我得到了:

11:16:37 ERROR cmd supercommand.go:458 cannot resolve charm URL "cs:wordpress/yakkety": cannot get "/wordpress/yakkety/meta/any?include=id&include=supported-series&include=published": Get https://api.jujucharms.com/charmstore/v5/wordpress/yakkety/meta/any?include=id&include=supported-series&include=published: x509: certificate signed by unknown authority

然后我决定从jujucharms本地下载魅力并使用本地存储库来部署wordpress服务,运行:

juju deploy ./wordpress/ --to 0  --series yakkety --debug

但我得到了:

11:25:07 INFO  juju.cmd supercommand.go:63 running juju [2.0.2 gc go1.6.3]
11:25:07 DEBUG juju.cmd supercommand.go:64   args: []string{"juju", "deploy", "./wordpress/", "--to", "0", "--series", "yakkety", "--debug"}
11:25:07 INFO  juju.juju api.go:72 connecting to API addresses: [*.*.*.*:17070 *.99.0.1:17070]
11:25:07 INFO  juju.api apiclient.go:530 dialing "wss://*.*.*.*:17070/model/ea08fba2-0150-4bf7-84d0-95949a55b835/api"
11:25:08 INFO  juju.api apiclient.go:466 connection established to "wss://*.*.*.*:17070/model/ea08fba2-0150-4bf7-84d0-95949a55b835/api"
11:25:08 DEBUG juju.juju api.go:263 API hostnames unchanged - not resolving
11:25:08 DEBUG juju.cmd.juju.application deploy.go:762 cannot interpret as local bundle: read ./wordpress/: is a directory
11:25:08 DEBUG httpbakery client.go:244 client do POST https://*.*.*.*:17070/model/ea08fba2-0150-4bf7-84d0-95949a55b835/charms?revision=93&schema=local&series=yakkety {
11:25:09 DEBUG httpbakery client.go:246 } -> error [{/build/juju-core-sGG418/juju-core-2.0.2/_build/src/gopkg.in/macaroon-bakery.v1/httpbakery/client.go:274: } {Post https://*.*.*.*:17070/model/ea08fba2-0150-4bf7-84d0-95949a55b835/charms?revision=93&schema=local&series=yakkety: Forbidden}]
11:25:09 DEBUG juju.api monitor.go:35 RPC connection died
11:25:09 ERROR cmd supercommand.go:458 POST https://*.*.*.*:17070/model/ea08fba2-0150-4bf7-84d0-95949a55b835/charms?revision=93&schema=local&series=yakkety: Post https://*.*.*.*:17070/model/ea08fba2-0150-4bf7-84d0-95949a55b835/charms?revision=93&schema=local&series=yakkety: Forbidden
11:25:09 DEBUG cmd supercommand.go:459 (error details: [{github.com/juju/juju/cmd/juju/application/deploy.go:823: } {github.com/juju/juju/api/client.go:299: } {github.com/juju/juju/api/client.go:315: } {github.com/juju/juju/api/client.go:482: } {/build/juju-core-sGG418/juju-core-2.0.2/_build/src/github.com/juju/httprequest/client.go:193: POST https://*.*.*.*:17070/model/ea08fba2-0150-4bf7-84d0-95949a55b835/charms?revision=93&schema=local&series=yakkety} {/build/juju-core-sGG418/juju-core-2.0.2/_build/src/gopkg.in/macaroon-bakery.v1/httpbakery/client.go:274: } {Post https://*.*.*.*:17070/model/ea08fba2-0150-4bf7-84d0-95949a55b835/charms?revision=93&schema=local&series=yakkety: Forbidden}])

juju model-config:

Attribute                   From     Value
agent-metadata-url          default  ""
agent-stream                default  released
agent-version               model    2.0.2.1
apt-ftp-proxy               default  ""
apt-http-proxy              default  ""
apt-https-proxy             default  ""
apt-mirror                  default  ""
automatically-retry-hooks   default  true
default-series              default  xenial
development                 default  false
disable-network-management  default  false
enable-os-refresh-update    default  true
enable-os-upgrade           default  true
firewall-mode               default  instance
ftp-proxy                   model    http://user:password@address:port/
http-proxy                  model    http://user:password@address:port/
https-proxy                 model    http://user:password@address:port/
ignore-machine-addresses    default  false
image-metadata-url          default  ""
image-stream                default  released
logforward-enabled          default  false
logging-config              model    <root>=WARNING;unit=DEBUG
no-proxy                    default  ""
provisioner-harvest-mode    default  destroyed
proxy-ssh                   default  false
resource-tags               model    {}
ssl-hostname-verification   model    false
test-mode                   model    true
transmit-vendor-metrics     default  true

我已经下载了juju源代码,我正在尝试理解该软件,在这种情况下,特别是http请求如何工作,所以我们可以在日志中看到错误集中在那里。

如何才能继续修复错误?

1 个答案:

答案 0 :(得分:0)

这里发生了一些事情。首先,尝试从魅力商店本身进行部署,将魅力和系列融为一体。通过juju部署魅力时,正确的语法是cs:/,或者只是cs: - 例如。

juju deploy cs:wordpress --to 0 --series yakkety --debug

其次,您的环境中似乎有基于ftp-proxy,http-proxy和https-proxy值的代理。配置代理可能有点棘手,因为您(通常)希望确保也应用无代理设置,以便内部请求不会转到代理。端口17070是juju单元用来与控制器通信的端口,我强烈怀疑它们是通过代理路由并被拒绝的。

相关问题