canonical / canonical/cloud-init
Building cloud-init on SLES 15 complains about missing cloud-id binary
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 1.1k
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 22
Description
This bug was originally filed in Launchpad as [LP: #1799337](https://bugs.launchpad.net/cloud-init/+bug/1799337)
Launchpad details
affected_projects = []
assignee = None
assignee_name = None
date_closed = None
date_created = 2018-10-23T02:52:43.009015+00:00
date_fix_committed = None
date_fix_released = None
id = 1799337
importance = medium
is_complete = False
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1799337
milestone = None
owner = jasonzio
owner_name = Jason Zions
private = False
status = confirmed
submitter = jasonzio
submitter_name = Jason Zions
tags = []
duplicates = []
_Launchpad user **Jason Zions(jasonzio)** wrote on 2018-10-23T02:52:43.009015+00:00_
Change 6ee8a2c55 (Chad Smith 2018-10-09 22:19:20 +0000 286) added 'cloud-id' to the list of console scripts in setup.py. The packaging spec for suse wasn't changed to package that script.
Contributor guide
Research direction
Start in setup.py to confirm cloud-id is declared as a console script, then locate the SUSE packaging spec mentioned in the issue. Update that spec so the cloud-id binary is included, build cloud-init on SLES 15, and verify the missing-binary warning is gone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100