Closed
Bug 1192386
Opened 10 years ago
Closed 10 years ago
jenkins prod wants to remove SSL listener
Categories
(Socorro :: Infra, task)
Socorro
Infra
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rhelmer, Assigned: jschneider)
Details
We just had a problem on prod where peterbe applied a tag, and the terraform removed the SSL listener.
Here's the plan from the jenkins box:
Refreshing Terraform state prior to plan...
aws_elasticache_subnet_group.ec-socorroweb-sub: Refreshing state... (ID: ec-prod-socorroweb-sub)
aws_security_group.ec2-socorroweb-sg: Refreshing state... (ID: sg-94b4a4f1)
aws_elb.elb-socorroweb: Refreshing state... (ID: elb-prod-socorroweb)
aws_security_group.ec-socorroweb-sg: Refreshing state... (ID: sg-9b0814fe)
aws_launch_configuration.lc-socorroweb: Refreshing state... (ID: terraform-ngm7fnxn7reo5acj4gsjzdzlvm)
aws_elasticache_cluster.ec-socorroweb: Refreshing state... (ID: ec-prod-socorroweb)
aws_autoscaling_group.as-socorroweb: Refreshing state... (ID: as-prod-socorroweb)
The Terraform execution plan has been generated and is shown below.
Resources are shown in alphabetical order for quick scanning. Green resources
will be created (or destroyed and then created if an existing resource
exists), yellow resources are being changed in-place, and red resources
will be destroyed.
Note: You didn't specify an "-out" parameter to save this plan, so when
"apply" is called, Terraform can't guarantee this is what will execute.
~ aws_autoscaling_group.as-socorroweb
desired_capacity: "8" => "3"
launch_configuration: "terraform-ngm7fnxn7reo5acj4gsjzdzlvm" => "${aws_launch_configuration.lc-socorroweb.id}"
min_size: "8" => "3"
~ aws_elb.elb-socorroweb
listener.1357722086.instance_port: "" => "80"
listener.1357722086.instance_protocol: "" => "http"
listener.1357722086.lb_port: "" => "443"
listener.1357722086.lb_protocol: "" => "https"
listener.1357722086.ssl_certificate_id: "" => ""
listener.283847201.instance_port: "80" => "0"
listener.283847201.instance_protocol: "http" => ""
listener.283847201.lb_port: "443" => "0"
listener.283847201.lb_protocol: "https" => ""
listener.283847201.ssl_certificate_id: "arn:aws:iam::293989542403:server-certificate/crash-stats-mozilla-com-2015-06-18" => ""
listener.3057123346.instance_port: "80" => "80"
listener.3057123346.instance_protocol: "http" => "http"
listener.3057123346.lb_port: "80" => "80"
listener.3057123346.lb_protocol: "http" => "http"
listener.3057123346.ssl_certificate_id: "" => ""
-/+ aws_launch_configuration.lc-socorroweb
associate_public_ip_address: "true" => "1"
ebs_block_device.#: "0" => "<computed>"
ebs_optimized: "false" => "<computed>"
enable_monitoring: "true" => "1"
iam_instance_profile: "generic" => "generic"
image_id: "ami-71686341" => "ami-e9734cd9" (forces new resource)
instance_type: "m3.medium" => "m3.medium"
key_name: "socorro__us-west-2" => "socorro__us-west-2"
name: "terraform-ngm7fnxn7reo5acj4gsjzdzlvm" => "<computed>"
root_block_device.#: "0" => "<computed>"
security_groups.#: "1" => "1"
security_groups.1500551122: "sg-94b4a4f1" => "sg-94b4a4f1"
user_data: "a2424a3d49cc5077acbdbd4323dbfb3ab8344e71" => "a2424a3d49cc5077acbdbd4323dbfb3ab8344e71"
Plan: 0 to add, 3 to change, 0 to destroy.
| Reporter | ||
Comment 1•10 years ago
|
||
It looks like "webapp_cert.prod" is missing from the tfvars file.
| Assignee | ||
Comment 2•10 years ago
|
||
Resolved
| Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•