Comment 7 for bug 1564536

Horizon won't generate EC2 credentials, if there's no ec2 service registered in the Keystone catalog:

https://github.com/openstack/horizon/blob/2ac6a69148e8357353c08d7ca9e8abf7e769f6c5/openstack_dashboard/dashboards/project/access_and_security/api_access/tables.py#L36-L45

At the same time, it's possible to generate and download credentials via openstackclient (MOS 9.0, ISO 154, built on April the 4th):

root@node-1:~# openstack ec2 credentials create
+------------+----------------------------------+
| Field | Value |
+------------+----------------------------------+
| access | 986d209f3e204673aa1ea50064caa63d |
| project_id | 61d52321fefb4c3fb42d3ede7faae70a |
| secret | 99c918ad3d094e38b541c62a33a0121f |
| trust_id | None |
| user_id | aa65bd0fac1947a2b0723efd8128736e |
+------------+----------------------------------+

So technically, we have a workaround to make S3 work, if EC2 is missing. But the former is still missing:

root@node-1:~# openstack service list
+----------------------------------+----------+----------------+
| ID | Name | Type |
+----------------------------------+----------+----------------+
| 096803ff753540b5aa62d9a302a09fb9 | heat | orchestration |
| 14d6947258d347459f2d02ec0d5e3e5e | glance | image |
| 24c24f2328e044cfaf9195e9b048d651 | keystone | identity |
| 2837a7f1d63145efa573a8fe81521708 | cinderv2 | volumev2 |
| 2eedffb7085d47ca97f82255e1beaef8 | nova | compute |
| 5ae568ae5b194e3090f7b30012f9afaf | cinder | volume |
| 5b7ee9938fa84a7494da041d043cc16a | cinderv3 | volumev3 |
| 6e511b79f3454c07bf1a7b2eb0569407 | swift | object-store |
| 74aa52f3aeab4cb0949905fb37a68027 | heat-cfn | cloudformation |
| 78124b4afaf84c6083e7308a9bf7eddf | novav3 | computev3 |
| ef83a5dee20f476b952cbb6c2b1ab525 | neutron | network |
+----------------------------------+----------+----------------+

So we should at least fix the S3 part, if not both. I wonder how our tests have missed this...