search

vmware-archive / pcf-pipelines

PCF Pipelines
Apache License 2.0
158 stars 282 forks source link

Could not execute "configure-product" during deploy-ert in vsphere install-pcf #139

Closed beibeiyang closed 7 years ago

beibeiyang commented 7 years ago

Environment:

We have consistently experienced the following error in our lab during the deploy-ert step of vsphere install-pcf:

>_ configure
configuring product...
setting properties
finished setting properties
setting up network
finished setting up network
applying resource configuration for the following jobs:
    backup-prepare
    ccdb
    clock_global
    cloud_controller
    cloud_controller_worker
    consul_server
    diego_brain
    diego_cell
    diego_database
    doppler
    etcd_tls_server
    ha_proxy
    loggregator_trafficcontroller
    mysql
    mysql_monitor
    mysql_proxy
    nats
    nfs_server
    router
could not execute "configure-product": could not fetch existing job configuration: request failed: unexpected response:
HTTP/1.1 404 Not Found
Connection: keep-alive
Content-Type: text/html; charset=utf-8
Date: Mon, 03 Jul 2017 07:03:55 GMT
Server: nginx/1.4.6 (Ubuntu)
Strict-Transport-Security: max-age=31536000
X-Request-Id: 634abe65-a8c0-4e38-a893-898df97a6c0d
X-Runtime: 0.001243
Content-Length: 0

@krishicks I believe it's caused by Commit 9843501 as PCF 1.10 does not have syslog_adapter and syslog_scheduler in the resource list. Here's the full list of resources available in Elastic Runtime 1.10.16:

[beibei@concourse-server concourse]$ om-linux   --target https://om.pcf.concourse.local   --username $USERNAME   --password $PASSWORD   --skip-ssl-validation   curl --path /api/v0/staged/products/cf-e514f6bfbb3ef75eaf30/resources
Status: 200 OK
Cache-Control: max-age=0, private, must-revalidate
Connection: keep-alive
Content-Type: application/json; charset=utf-8
Date: Mon, 03 Jul 2017 15:58:58 GMT
Etag: W/"b9e13ff8e9e811f61b31af1c184a9823"
Server: nginx/1.4.6 (Ubuntu)
Strict-Transport-Security: max-age=31536000
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-Request-Id: 1c38be6c-e96e-428a-95d0-0a5db73f9280
X-Runtime: 0.527115
X-Xss-Protection: 1; mode=block
{
  "resources": [
    {
      "identifier": "consul_server",
      "description": "",
      "instances": 1,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro",
      "persistent_disk_mb": 1024,
      "persistent_disk_best_fit": 1024
    },
    {
      "identifier": "nats",
      "description": "Acts as the Pivotal CF Elastic Runtime message bus",
      "instances": 1,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro"
    },
    {
      "identifier": "etcd_tls_server",
      "description": "An etcd TLS cluster node, which maintains the state of applications, and its metrics server",
      "instances": 1,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro",
      "persistent_disk_mb": 1024,
      "persistent_disk_best_fit": 1024
    },
    {
      "identifier": "nfs_server",
      "description": "Stores droplets and app packages on behalf of Cloud Controller",
      "instances": 1,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "medium.mem",
      "persistent_disk_mb": 102400,
      "persistent_disk_best_fit": 102400
    },
    {
      "identifier": "mysql_proxy",
      "description": "MySQL Proxy",
      "instances": 1,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro"
    },
    {
      "identifier": "mysql",
      "description": "Multi-tenant MySQL server.",
      "instances": 1,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "large.disk",
      "persistent_disk_mb": 102400,
      "persistent_disk_best_fit": 100000
    },
    {
      "identifier": "backup-prepare",
      "description": "Streams backups from MySQL Cluster",
      "instances": 0,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro",
      "persistent_disk_mb": 204800,
      "persistent_disk_best_fit": 200000
    },
    {
      "identifier": "ccdb",
      "description": "Stores Cloud Controller information",
      "instances": 0,
      "instances_best_fit": 0,
      "instance_type_id": "",
      "instance_type_best_fit": "micro",
      "persistent_disk_mb": 2048,
      "persistent_disk_best_fit": 2048
    },
    {
      "identifier": "diego_database",
      "description": "An datastore node for Diego",
      "instances": 1,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro"
    },
    {
      "identifier": "uaadb",
      "description": "Stores user information for the UAA",
      "instances": "",
      "instances_best_fit": 0,
      "instance_type_id": "",
      "instance_type_best_fit": "micro",
      "persistent_disk_mb": 10240,
      "persistent_disk_best_fit": 8192
    },
    {
      "identifier": "uaa",
      "description": "Pivotal CF Elastic Runtime's Authentication and Authorization server",
      "instances": "",
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "medium.disk"
    },
    {
      "identifier": "cloud_controller",
      "description": "Coordinates Pivotal CF Elastic Runtime application lifecycles",
      "instances": 1,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "medium.disk"
    },
    {
      "identifier": "ha_proxy",
      "description": "HAProxy is the default load balancer for SSL termination. Alternatively, you can use your own load balancer and forward traffic to the Pivotal CF Elastic Runtime router IP. Self signed certificates will function properly.",
      "instances": 0,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro"
    },
    {
      "identifier": "router",
      "description": "Routers route Internet traffic to applications and between Pivotal CF Elastic Runtime components.",
      "instances": 1,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro"
    },
    {
      "identifier": "mysql_monitor",
      "description": "Monitors the MySQL Cluster",
      "instances": 1,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro"
    },
    {
      "identifier": "clock_global",
      "description": "Schedules asynchronous tasks for cloud controller",
      "instances": 1,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro"
    },
    {
      "identifier": "cloud_controller_worker",
      "description": "Worker for cloud controller asynchronous tasks",
      "instances": 1,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro"
    },
    {
      "identifier": "diego_brain",
      "description": "Diego Brain",
      "instances": 1,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "small",
      "persistent_disk_mb": 1024,
      "persistent_disk_best_fit": 1024
    },
    {
      "identifier": "diego_cell",
      "description": "Diego Cell",
      "instances": 3,
      "instances_best_fit": 3,
      "instance_type_id": "",
      "instance_type_best_fit": "xlarge.disk"
    },
    {
      "identifier": "doppler",
      "description": "Doppler server collects application logs",
      "instances": 1,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro"
    },
    {
      "identifier": "loggregator_trafficcontroller",
      "description": "Loggregator trafficcontroller distributes requests to Loggregator servers",
      "instances": 1,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro"
    },
    {
      "identifier": "tcp_router",
      "description": "TCP Routers route TCP traffic.",
      "instances": 0,
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro",
      "persistent_disk_mb": 1024,
      "persistent_disk_best_fit": 1024
    },
    {
      "identifier": "smoke-tests",
      "description": "Runs Smoke Tests against your Elastic Runtime installation",
      "instances": "",
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro"
    },
    {
      "identifier": "push-apps-manager",
      "description": "Pushes the Pivotal Apps Manager application to your Elastic Runtime installation",
      "instances": "",
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro"
    },
    {
      "identifier": "notifications",
      "description": "Pushes the Pivotal Notifications application to your Elastic Runtime installation",
      "instances": "",
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro"
    },
    {
      "identifier": "notifications-ui",
      "description": "Pushes the Notifications UI component to your Elastic Runtime installation",
      "instances": "",
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro"
    },
    {
      "identifier": "push-pivotal-account",
      "description": "Pushes the Pivotal Account application to your Elastic Runtime installation",
      "instances": "",
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "small"
    },
    {
      "identifier": "autoscaling",
      "description": "Pushes the Pivotal App Autoscaling application to your Elastic Runtime installation",
      "instances": "",
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "small"
    },
    {
      "identifier": "autoscaling-register-broker",
      "description": "Registers the Autoscaling Service Broker",
      "instances": "",
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "nano"
    },
    {
      "identifier": "nfsbrokerpush",
      "description": "Pushes the NFS Broker application to your Elastic Runtime installation",
      "instances": "",
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro"
    },
    {
      "identifier": "bootstrap",
      "description": "Errand for bootstrapping the MySQL cluster",
      "instances": "",
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "small"
    },
    {
      "identifier": "mysql-rejoin-unsafe",
      "description": "MySQL Rejoin Unsafe Errand",
      "instances": "",
      "instances_best_fit": 1,
      "instance_type_id": "",
      "instance_type_best_fit": "micro"
    }
  ]
}
cf-gitbot commented 7 years ago

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

krishicks commented 7 years ago

pcf-pipelines tracks the current version of OpsMgr and Elastic Runtime; as of v0.15.1 (and 9843501), 1.10 is no longer supported.

You should be able to use v0.15.0 to install 1.10.