rally deployment check is giving _unknown_ under services

Bug #1618121 reported by Ram Kumar
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Rally
Invalid
Undecided
Unassigned

Bug Description

+-------------+---------------------+-----------+
| services | type | status |
+-------------+---------------------+-----------+
| __unknown__ | application_catalog | Available |
| __unknown__ | computev3 | Available |
| __unknown__ | volumev2 | Available |

getting unknown services for three types.

Thanks,
Ram

Revision history for this message
Alexander Maretskiy (maretskiy) wrote :

This is not a bug, and there should be a message printed at the end of services list [1].

 There are __unknown__ services because their types are not recognized automatically [2]:
application_catalog, computev3 and volumev2. This is normal since cloud can be configured to return custom service type name, however these services can be used without any restrictions by api_versions context [3]

[1] https://github.com/openstack/rally/blob/0.5.0/rally/cli/commands/deployment.py#L245-L252
[2] https://github.com/openstack/rally/blob/0.5.0/rally/consts.py#L119-L173
[3] https://github.com/openstack/rally/blob/0.5.0/rally/plugins/openstack/context/api_versions.py

Changed in rally:
status: New → Invalid
Revision history for this message
Ram Kumar (ram-kumar2) wrote :

I noticed there is a name listed for costs.py for application_catalog
APPLICATION_CATALOG = "application-catalog"
self.APPLICATION_CATALOG: _Service.MURANO,

Is it supposed to give murano for application_catalog?

Thanks

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.