calico felix.cfg metadata https protocol support

Bug #1938447 reported by Satish Patel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-calico
Invalid
Undecided
Unassigned

Bug Description

I am deploying openstack using openstack-ansible and found calico is failing at Metadata and turned out nova-metadata api using SSL vip and felix has no option to tell to use protocol https

$ cat felix.cfg
[global]
MetadataAddr = 172.29.236.101
EtcdEndpoints = http://127.0.0.1:2379
DatastoreType = etcdv3

[log]
LogFilePath = none
LogSeverityScreen = Fatal

How do i tell it to use https instead of http to talk to nova-metadata-api service?

Revision history for this message
Nell Jerram (neil-jerram) wrote :

Hi Satish, would you mind re-raising this at https://github.com/projectcalico/felix/issues ? That's the right place for Felix issues, rather than here.

I also took a quick look and think there is a very simple fix - but please let's discuss that over at https://github.com/projectcalico/felix

Revision history for this message
Nell Jerram (neil-jerram) wrote :

Oh, if you can tag me as @neiljerram on the issue, that'll make sure that I see it.

Revision history for this message
Satish Patel (satish-txt) wrote :

Thank you for reply, i have posted question there https://github.com/projectcalico/felix/issues/2933

Revision history for this message
Satish Patel (satish-txt) wrote :

Neil, let me know if there is any fix, because its holding up some stuff :)

Revision history for this message
Nell Jerram (neil-jerram) wrote :

Thanks Satish, I've responded at https://github.com/projectcalico/felix/issues/2933. Will close this one now.

Changed in networking-calico:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.