The service EC2 (nova_ec2) does not exist in the catalog list

[Alexander Petrov]

Detailed bug description:
The service s3 does not exist in the catalog (endpoint) list and as result there are not any EC2 credencials in Horizon.

Steps to reproduce:
 1) deploy ENV MOS9 in minimal configuration
 2) run on any controller the next commands:
    . openrc
    openstack endpoint list

Expected results:
| a475b3480066409ba766fbe7b1e3d32b | RegionOne | nova_ec2 | ec2 |

      here is the the command output in MOS8
      http://paste.openstack.org/show/492629/

Actual result:
 The record EC2 does not exist
  here is the the command output in MOS9
  http://paste.openstack.org/show/492630/

Description of the environment:
  MOS9.0 build 106
  Liberty on Ubuntu 14.04
  QEMU
 Neutron with VLAN segmentation
 Ceph RBD for volumes (Cinder)
 Ceph RadosGW for objects (Swift API)
 Ceph RBD for ephemeral volumes (Nova)
 Ceph RBD for images (Glance)
 Controller 3
 Compute 3
 Storage - Ceph OSD 3

[Roman Podoliaka (rpodolyaka)]

Puppet team, could you please take care of this?

Since Mitaka EC2 has been moved into a separate repo - https://github.com/openstack/ec2-api . Still, we should deploy it in 9.0 and (maybe) deprecate properly before removing it from MOS (if we are sure we don't need it).

[Ivan Berezovskiy (iberezovskiy)]

EC2 api support in nova was deprecated since Kilo release and was finally dropped in this commit https://github.com/openstack/nova/commit/eec7a55319b3f22949735227199ce49b851519b8. Fuel did support its deployment till
it was in nova code. Once it was removed - the same was done in Fuel: https://review.openstack.org/#/c/268147/.
This patch depends also on puppet-nova commit: https://github.com/openstack/puppet-nova/commit/d7389d44beb9c14a236a480e8c9f423574f6466b which actually did the same.

We skipped deprecation period in Fuel (e.g. we didn't provide any warnings), but in 9.0 it didn't make sense to do (because as I said before it was removed from Nova code). If we speack about previous versions of Fuel the deprecation should come from Nova.

For 9.0 it's too late to deploy ec2-api as separate service because it looks like a huge feature:
puppet-module isn't ready at all - https://github.com/openstack/puppet-ec2api

If we really need this in 10.0 - please file a blueprint with specification, our team will take care about puppet module and deployment tasks in Fuel. But for 9.0 this issue is invalid.

[Timur Nurlygayanov (tnurlygayanov)]

I'm going to describe separate bug because it is an important feature and we can't just move but to Invalid and forget that we lost the large part of OpenStack features.

[Maksym Shalamov (mshalamov)]

Hello all,
This bug has been reopened because functionality described in this bug affects S3 API usage, we are unable to generate credentials.(download an archive via horizon which contains credential).

[Maksym Shalamov (mshalamov)]

Critical - due to this bug is a blocker for S3 API

[Dina Belova (dbelova)]

Sorry, somehow turned back to High. Setting Critical importance.

[Roman Podoliaka (rpodolyaka)]

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...

[Timur Sufiev (tsufiev-x)]

A link to the Horizon ad-hoc fix: https://review.fuel-infra.org/#/c/19184/

[Roman Podoliaka (rpodolyaka)]

Per the discussion in the ML thread, downgrading this to High, as there is a workaround for S3

[Ivan Berezovskiy (iberezovskiy)]

Workaround for horizon was implemented, we also have a workaround for CLI. So we should document that ec2-api was removed from Fuel 9.0 (https://review.openstack.org/#/c/268147/) and need to describe the workaround in release notes. I change assignee to doc team.

[Fuel Devops McRobotson (fuel-devops-robot)]

Fix proposed to branch: master
Change author: Alexander Adamov <email address hidden>
Review: https://review.fuel-infra.org/21128

[Fuel Devops McRobotson (fuel-devops-robot)]

Reviewed: https://review.fuel-infra.org/21128
Submitter: Olga Gusarenko <email address hidden>
Branch: master

Commit: d5199565c1a069c0d586e78b0e7d75a05c83fc31
Author: Alexander Adamov <email address hidden>
Date: Tue May 24 10:56:25 2016

[RN MOS9.0] Fuel known and resolved issues

Adds Fuel known and resolved issues to the
MOS9.0 Release Notes:

- #1564536 The service EC2 (nova_ec2) does not exist
           in the catalog list
- #1545988 Fix idempotency of compute tasks
- #1547003 Cluster capacity calculation fix
- #1556854 [NFV] Deployment with enabled SR-IOV fails

Change-Id: I9e683cf18797a19d4d67043d7652f94a39960e42
Closes-Bug: #1564536
Closes-Bug: #1545988
Closes-Bug: #1547003
Closes-Bug: #1556854

[Kyrylo Romanenko (kromanenko)]

I can not see ec2 in service and endpoint list.
# openstack service list
+----------------------------------+----------------+----------------+
| ID | Name | Type |
+----------------------------------+----------------+----------------+
| 11eed64e2447451aa351282213e85be5 | cinder | volume |
| 17fc13ae1798431298dbffbbab10bd41 | heat-cfn | cloudformation |
| 2d53e096d8d447f286a4be35f039c866 | glance | image |
| 3c475d832b2c42ed8c83083a9907beaf | glare | artifact |
| 42d63289927a4588bbfb0806eb08d381 | heat | orchestration |
| 5431eef678cf408895f7c0ea7a9e3ad9 | swift_s3 | s3 |
| 5f4a2d30b64047249cd80cc96c1e32ad | cinderv2 | volumev2 |
| 7aa08297e37c473d89ad9a47e0f392ef | swift | object-store |
| 9ad7a9bd4a254aabb82b79f9966a3b9a | nova | compute |
| ab0c561838124dd7bca23e0f73c89699 | keystone | identity |
| c65324b66f924d16a4895170b13ac8ef | compute_legacy | compute_legacy |
| df2cf820f18e47ce92f5903d17a83894 | novav3 | computev3 |
| f4044acd1fa94207bd14a71179f2bc64 | cinderv3 | volumev3 |
| f58867857b254c5ebd58ac065f371d8a | neutron | network |
+----------------------------------+----------------+----------------+
root@node-1:~# openstack endpoint list
+----------------------------------+-----------+----------------+----------------+
| ID | Region | Service Name | Service Type |
+----------------------------------+-----------+----------------+----------------+
| 7a0a510d2fb547538ab71306f04e5f23 | RegionOne | neutron | network |
| 151d1629c5f84585807ef56d4601407a | RegionOne | novav3 | computev3 |
| 669a2a2865914d86af7f5adeb7ae908f | RegionOne | glare | artifact |
| 958f30dd17464de6af66c96ff4e41db6 | RegionOne | heat | orchestration |
| 942172bc9ed14c9db9b66ea821ed31b6 | RegionOne | heat-cfn | cloudformation |
| a0ca2cc5319d418ea098885e61a95518 | RegionOne | swift | object-store |
| 38f723912b8d4f04ac0a2b23e65163f3 | RegionOne | cinder | volume |
| f343063dbe384c68b73898bf167f02bd | RegionOne | nova | compute |
| b7f4fb82f9604da68daf64f07922cc95 | RegionOne | cinderv2 | volumev2 |
| 40a1f770d386429abc6102b838d9421f | RegionOne | cinderv3 | volumev3 |
| 800208f64175441f889e1bfddf6d412c | RegionOne | compute_legacy | compute_legacy |
| 0a6012067a0f481f9d94d41a860dd9ba | RegionOne | swift_s3 | s3 |
| 82fa5b7ce75d4fef8f0513e12e888ad7 | RegionOne | glance | image |
| 6038917e6dcc4e9f99d416ab502f6b32 | RegionOne | keystone | identity |
+----------------------------------+-----------+----------------+----------------+

But i can download EC2 creds via Horizon. Is it expected behavior after fix?

[Kyrylo Romanenko (kromanenko)]

Well, it`s expected after fix.
 shotgun2 short-report
cat /etc/fuel_build_id:
 416
cat /etc/fuel_build_number:
 416
cat /etc/fuel_release:
 9.0
cat /etc/fuel_openstack_version:
 mitaka-9.0
rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun':
 fuel-release-9.0.0-1.mos6347.noarch
 fuel-bootstrap-cli-9.0.0-1.mos284.noarch
 fuel-migrate-9.0.0-1.mos8398.noarch
 rubygem-astute-9.0.0-1.mos746.noarch
 fuel-provisioning-scripts-9.0.0-1.mos8709.noarch
 network-checker-9.0.0-1.mos72.x86_64
 fuel-mirror-9.0.0-1.mos137.noarch
 fuel-openstack-metadata-9.0.0-1.mos8709.noarch
 fuel-notify-9.0.0-1.mos8398.noarch
 nailgun-mcagents-9.0.0-1.mos746.noarch
 python-fuelclient-9.0.0-1.mos316.noarch
 fuelmenu-9.0.0-1.mos270.noarch
 fuel-9.0.0-1.mos6347.noarch
 fuel-utils-9.0.0-1.mos8398.noarch
 fuel-setup-9.0.0-1.mos6347.noarch
 fuel-library9.0-9.0.0-1.mos8398.noarch
 shotgun-9.0.0-1.mos90.noarch
 fuel-agent-9.0.0-1.mos284.noarch
 fuel-ui-9.0.0-1.mos2706.noarch
 fuel-ostf-9.0.0-1.mos934.noarch
 fuel-misc-9.0.0-1.mos8398.noarch
 python-packetary-9.0.0-1.mos137.noarch
 fuel-nailgun-9.0.0-1.mos8709.noarch

[Fuel Devops McRobotson (fuel-devops-robot)]

Change abandoned by Paul Karikh <email address hidden> on branch: master
Review: https://review.fuel-infra.org/19184
Reason: Is not necessary anymore.

[Anna Babich (ababich)]

Verified on devstack with Newton. Since the fix https://review.fuel-infra.org/#/c/19184/ has been abandoned, it's no need to check that workaround works via Horizon, only via CLI:

stack@ubuntu:~/mos-rally-verify$ openstack ec2 credentials create
+------------+----------------------------------+
| Field | Value |
+------------+----------------------------------+
| access | 80a355b14f8f43c79597edff26b2b44f |
| project_id | aee2e8a014f3406a95464670d7a380c3 |
| secret | 688d8d8d9d48445cbaed2207200ab90e |
| trust_id | None |
| user_id | bb86d321b42c4901a17eef05c69e55c3 |
+------------+----------------------------------+

stack@ubuntu:~/mos-rally-verify$ openstack ec2 credentials list
+----------------------------------+----------------------------------+----------------------------------+----------------------------------+
| Access | Secret | Project ID | User ID |
+----------------------------------+----------------------------------+----------------------------------+----------------------------------+
| 80a355b14f8f43c79597edff26b2b44f | 688d8d8d9d48445cbaed2207200ab90e | aee2e8a014f3406a95464670d7a380c3 | bb86d321b42c4901a17eef05c69e55c3 |
+----------------------------------+----------------------------------+----------------------------------+----------------------------------+

stack@ubuntu:~/mos-rally-verify$ openstack ec2 credentials show --user admin 80a355b14f8f43c79597edff26b2b44f
+------------+----------------------------------+
| Field | Value |
+------------+----------------------------------+
| access | 80a355b14f8f43c79597edff26b2b44f |
| project_id | aee2e8a014f3406a95464670d7a380c3 |
| secret | 688d8d8d9d48445cbaed2207200ab90e |
| trust_id | None |
| user_id | bb86d321b42c4901a17eef05c69e55c3 |
+------------+----------------------------------+