canonical / canonical/cloud-init

ds-identify does not identify openstack Open Telecom Cloud BMS

Open
#3,378 6 comments 0 reactions 0 assignees View on GitHub
bug launchpad
Dominant language
Python
Stars
3.8k
Forks
1.1k
Avg merge
2d 23h
Merged PRs (30d)
18

Description

This bug was originally filed in Launchpad as [LP: #1828236](https://bugs.launchpad.net/cloud-init/+bug/1828236)

Launchpad details

affected_projects = []

assignee = None
assignee_name = None
date_closed = None
date_created = 2019-05-08T13:50:56.955867+00:00
date_fix_committed = None
date_fix_released = None
id = 1828236
importance = medium
is_complete = False
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1828236
milestone = None
owner = sabrina-mueller
owner_name = Sabrina
private = False
status = triaged
submitter = sabrina-mueller
submitter_name = Sabrina
tags = ['dsid']
duplicates = []

_Launchpad user **Sabrina(sabrina-mueller)** wrote on 2019-05-08T13:50:56.955867+00:00_

relating to cloud-init bugs #1669675 #1756471

The OpenStack detection fails on BMS (Bare Metal) hosts in Open Telekom Cloud.

cloud-init version 18.5 detection fails
cloud-init Version 18.2 still works

/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceOpenStack.py searches for
(...) 
# OpenStack DMI constants
DMI_PRODUCT_NOVA = 'OpenStack Nova'
DMI_PRODUCT_COMPUTE = 'OpenStack Compute'
VALID_DMI_PRODUCT_NAMES = [DMI_PRODUCT_NOVA, DMI_PRODUCT_COMPUTE]
DMI_ASSET_TAG_OPENTELEKOM = 'OpenTelekomCloud'
VALID_DMI_ASSET_TAGS = [DMI_ASSET_TAG_OPENTELEKOM]
(...)
 
BMS server in OTC have none of theses tags set.
Manual edit DataSourceOpenStack.py only for testing to accept our host, all is working fine.

How we can get back OTC BMS hosts detected as valid OpenStack hosts in cloud-init?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.