#10526 proxy34 is dead
Closed: Fixed 3 years ago by kevin. Opened 3 years ago by mobrien.

Describe what you would like us to do:


Proxy34 is dead and needs to be replaced

When do you need this to be done by? (YYYY/MM/DD)



Metadata Update from @kevin:
- Issue assigned to mobrien
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: medium-gain, medium-trouble, ops

3 years ago

I think this is fine now and we can re-add it and close, but @mobrien can you confirm?

I think we do need to drop:

  • { role: ec2_proxy,
    when: "inventory_hostname in groups['cloud_aws']" }

from the proxies playbook now tho, as this sized ec2 instance doesn't have 2 nvme devices, so we don't need to bother with that anymore.

I think this is fine now and we can re-add it and close, but @mobrien can you confirm?

Yes we can close it

I think we do need to drop:

  • { role: ec2_proxy,
    when: "inventory_hostname in groups['cloud_aws']" }
    from the proxies playbook now tho, as this sized ec2 instance doesn't have 2 nvme devices, so we don't need to bother with that anymore.

I ran the playbook with skip-tags for that but some of the older proxies still have the 2 drives so I will change the when statement and put a var in for the ones that need it.

Yeah, but thats if we reprovision them... if we do that, wouldn't we just use this new flavor? :)

Anyhow, thanks for poking at this!

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Log in to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog