【问题标题】:WSO2 P.PaaS installation failure : Invalid Partition DetectedWSO2 P.PaaS 安装失败:检测到无效分区
【发布时间】:2015-07-18 21:24:56
【问题描述】:

当我运行boot.sh 命令时,我有这个错误消息列表。最后,我看到了这条消息。

**************************************************************
Management Console : https://something.private.paas:9443/console
**************************************************************

boot.sh: WSO2 Private PaaS installation completed successfully!

但是,我什至无法登录控制台。如何绕过错误消息并成功安装?

注意,在运行 boot.sh 时,我会收到 Enter EC2 credentials : 的提示,我认为这是 AWS 密钥(因为要输入的字段是密码字段)。但是,文档here 提到同时 输入访问密钥和秘密密钥。这可能是一个原因吗?

Deploying partition at /home/ubuntu/private-paas/resources/json/ec2/partition.json
{"Error":{ "errorCode": " 400", "errorMessage": " Invalid Partition Detected : P1. Cause: POST https://ec2.us-east-1.amazonaws.com/ HTTP/1.1 -> HTTP/1.1 401 Unauthorized"}}Deploying autoscale policy at /home/ubuntu/private-paas/resources/json/ec2/autoscale-policy.json
{"stratosAdminResponse":{"message":"Successfully deployed autoscaling policy definition with id economy"}}Deploying deployment policy at /home/ubuntu/private-paas/resources/json/ec2/deployment-policy.json
{"Error":{ "errorCode": " 400", "errorMessage": " Deployment policy is invalid: [id] deployp"}}Deploying deployment policy at /home/ubuntu/private-paas/resources/json/ec2/deployment-flat.json
{"Error":{ "errorCode": " 400", "errorMessage": " Deployment policy is invalid: [id] deployf"}}Deploying LB cartridge at /home/ubuntu/private-paas/resources/json/ec2/lb-cart.json
{"Error":{ "errorCode": " 400", "errorMessage": " Unable to build the jclouds object for iaas of type: ec2"}}Deploying Aplication Server (AS) Manager cartridge at /home/ubuntu/private-paas/resources/json/ec2/appserver-cart-mgt.json
{"Error":{ "errorCode": " 400", "errorMessage": " Unable to build the jclouds object for iaas of type: ec2"}}Deploying Application Service Manager service
{"Error":{ "errorCode": " 400", "errorMessage": " Failed to deploy the Service [Cartridge type] appservermgt [alias] f579b9c2-7315-4c2b-ab04-9f6cc4c101a3 . Cause: appservermgt is not a valid cartridgeSubscription type. Please try again with a valid cartridgeSubscription type."}}Deploying Aplication Server (AS) Worker cartridge at /home/ubuntu/private-paas/resources/json/ec2/appserver-cart-worker.json
{"Error":{ "errorCode": " 400", "errorMessage": " Unable to build the jclouds object for iaas of type: ec2"}}Deploying Application Service Worker service
{"Error":{ "errorCode": " 400", "errorMessage": " Failed to deploy the Service [Cartridge type] appserverworker [alias] 42174455-c01f-4b2a-a9ae-d40694768697 . Cause: appserverworker is not a valid cartridgeSubscription type. Please try again with a valid cartridgeSubscription type."}}Deploying API Manager (AM) - Gateway cartridge at /home/ubuntu/private-paas/resources/json/ec2/gateway.json
{"Error":{ "errorCode": " 400", "errorMessage": " Unable to build the jclouds object for iaas of type: ec2"}}Deploying API Manager - Gateway service
{"Error":{ "errorCode": " 400", "errorMessage": " Failed to deploy the Service [Cartridge type] gateway [alias] f55ef728-405e-44de-8dac-6990fe65983c . Cause: gateway is not a valid cartridgeSubscription type. Please try again with a valid cartridgeSubscription type."}}Deploying API Manager (AM) - Gateway manager cartridge at /home/ubuntu/private-paas/resources/json/ec2/gatewaymgt.json
{"Error":{ "errorCode": " 400", "errorMessage": " Unable to build the jclouds object for iaas of type: ec2"}}Deploying API Manager - Gateway manager service
{"Error":{ "errorCode": " 400", "errorMessage": " Failed to deploy the Service [Cartridge type] gatewaymgt [alias] 08381456-b720-4280-8904-1a8fa294901b . Cause: gatewaymgt is not a valid cartridgeSubscription type. Please try again with a valid cartridgeSubscription type."}}Deploying API Manager (AM) - Keymanager cartridge at /home/ubuntu/private-paas/resources/json/ec2/keymanager.json
{"Error":{ "errorCode": " 400", "errorMessage": " Unable to build the jclouds object for iaas of type: ec2"}}Deploying API Manager (AM) - Keymanager service
{"Error":{ "errorCode": " 400", "errorMessage": " Failed to deploy the Service [Cartridge type] keymanager [alias] 93e67ddb-86f2-416b-8feb-b1a4e4bc6d82 . Cause: keymanager is not a valid cartridgeSubscription type. Please try again with a valid cartridgeSubscription type."}}Deploying API Manager (AM) - Publisher cartridge at /home/ubuntu/private-paas/resources/json/ec2/publisher.json
{"Error":{ "errorCode": " 400", "errorMessage": " Unable to build the jclouds object for iaas of type: ec2"}}Deploying API Manager (AM) - Publisher service
{"Error":{ "errorCode": " 400", "errorMessage": " Failed to deploy the Service [Cartridge type] publisher [alias] 95de5e64-7169-49d1-a4d8-c582980c0d38 . Cause: publisher is not a valid cartridgeSubscription type. Please try again with a valid cartridgeSubscription type."}}Deploying API Manager (AM) - Store cartridge at /home/ubuntu/private-paas/resources/json/ec2/store.json
{"Error":{ "errorCode": " 400", "errorMessage": " Unable to build the jclouds object for iaas of type: ec2"}}Deploying API Manager (AM) - Store service
{"Error":{ "errorCode": " 400", "errorMessage": " Failed to deploy the Service [Cartridge type] apistore [alias] 2a46279f-8ffa-4ab0-88df-28591053e9f6 . Cause: apistore is not a valid cartridgeSubscription type. Please try again with a valid cartridgeSubscription type."}}Deploying Enterprise Service Bus (ESB) Manager cartridge at /home/ubuntu/private-paas/resources/json/ec2/esb-cart-mgt.json
{"Error":{ "errorCode": " 400", "errorMessage": " Unable to build the jclouds object for iaas of type: ec2"}}Deploying Enterprise Service Bus (ESB) Manager service
{"Error":{ "errorCode": " 400", "errorMessage": " Failed to deploy the Service [Cartridge type] esbmgt [alias] 63e7e8c0-04f5-4486-af48-b171f1e52688 . Cause: esbmgt is not a valid cartridgeSubscription type. Please try again with a valid cartridgeSubscription type."}}Deploying Enterprise Service Bus (ESB) Worker cartridge at /home/ubuntu/private-paas/resources/json/ec2/esb-cart-worker.json
{"Error":{ "errorCode": " 400", "errorMessage": " Unable to build the jclouds object for iaas of type: ec2"}}Deploying Enterprise Service Bus (ESB) Worker service
{"Error":{ "errorCode": " 400", "errorMessage": " Failed to deploy the Service [Cartridge type] esbworker [alias] d940f54c-98fc-4c21-aafa-b31488b9616d . Cause: esbworker is not a valid cartridgeSubscription type. Please try again with a valid cartridgeSubscription type."}}Deploying Business Process Server (BPS) Manager cartridge at /home/ubuntu/private-paas/resources/json/ec2/bps-cart-mgt.json
{"Error":{ "errorCode": " 400", "errorMessage": " Unable to build the jclouds object for iaas of type: ec2"}}Deploying Business Process Server (BPS) Manager service
{"Error":{ "errorCode": " 400", "errorMessage": " Failed to deploy the Service [Cartridge type] bpsmgt [alias] 779291a8-a4f2-4ef7-9815-43675749a881 . Cause: bpsmgt is not a valid cartridgeSubscription type. Please try again with a valid cartridgeSubscription type."}}Deploying Business Process Server (BPS) Worker cartridge at /home/ubuntu/private-paas/resources/json/ec2/bps-cart-worker.json
{"Error":{ "errorCode": " 400", "errorMessage": " Unable to build the jclouds object for iaas of type: ec2"}}Deploying Business Process Server (BPS) Worker service
{"Error":{ "errorCode": " 400", "errorMessage": " Failed to deploy the Service [Cartridge type] bpsworker [alias] 4aa5efa2-5b63-49aa-ada5-765bbf409a9d . Cause: bpsworker is not a valid cartridgeSubscription type. Please try again with a valid cartridgeSubscription type."}}


Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "agent.py", line 33, in getLBIp
    lb_ip=cluster['cluster'][0]['member'][0]['memberPublicIp']
IndexError: list index out of range

【问题讨论】:

  • 这似乎是一个权限问题。您是否提供了正确的 EC2 身份和凭证?您可以在 EC2 部分下的 conf.sh 文件(与 boot.sh 位于同一目录中)中指定它并运行 boot.sh。
  • 你的意思是,export ec2_credentials= 被设置为密钥?
  • 是 - 将其设置为秘密访问密钥。并设置其他参数,如 ec2_identity、ec2_availability_zone 等
  • 确保在再次运行 boot.sh 之前运行 clean.sh。它将清除以前的安装。
  • 不走运。我在boot.sh 之前运行过clean.sh。我在 EC2 部分中为export ec2_credentials= 设置了密钥。我知道密钥是正确的,因为我已将其设置为 AWS_SECRET_KEY 并且 AWS EC2 CLI 正在为我工​​作。 (这意味着,分配给我的角色具有足够的访问权限 - 就 AWS EC2 而言。)

标签: amazon-web-services amazon-ec2 wso2 paas


【解决方案1】:

WSO2 P.PaaS 安装期间的几件事。

您在安装期间使用的用户 ID 应具有完全管理权限,因为它将调用某些 AWS EC2 CLI 命令。见here

private-paas 文件夹中的 conf.sh 文件对于 IaaS 部分应该看起来像这样。

export iaas="ec2"
export region="ap-southeast-1"
export cartridge_base_img_id="ami-e6bd9eb4"

而且,就像 EC2 部分一样。

export ec2_vpc="this-was-y-for-me"
export ec2_identity="AWS ACCESS KEY"  
export ec2_credentials="AWS SECRET KEY" 
export ec2_owner_id="num-owner-id" 
export ec2_keypair_name="as-applicable-to-you"
export ec2_security_groups="as-applicable-to-you"
export ec2_availability_zone="ap-southeast-1a"
export ec2_security_group_ids="as-applicable-to-you"
export ec2_subnet_id="as-applicable-to-you"
export ec2_associate_public_ip_address="as-applicable-to-you"

上面列出的“as-applicable-to-you”可以通过在命令行aws ec2 describe-instances上运行来获得。请参阅here 了解如何安装和使用 AWS EC2 CLI。

ec2_availability_zone 设置为 ap-southeast-1a,因为基本映像位于亚太地区。这与IaaS 部分中的region 设置同步。有关 P.PaaS 的 EC2 AMI,请参阅 here

【讨论】:

    猜你喜欢
    • 2015-10-22
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2015-01-17
    • 2012-07-10
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多