canonical / canonical/cloud-init
Invalid cloud-config provided warning but still works -- how to remove?
- 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: #1977818](https://bugs.launchpad.net/cloud-init/+bug/1977818)
Launchpad details
affected_projects = []
assignee = None
assignee_name = None
date_closed = None
date_created = 2022-06-07T09:09:43.404736+00:00
date_fix_committed = None
date_fix_released = None
id = 1977818
importance = medium
is_complete = False
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1977818
milestone = None
owner = kimsia
owner_name = kimsia sim
private = False
status = triaged
submitter = kimsia
submitter_name = kimsia sim
tags = []
duplicates = []
_Launchpad user **kimsia sim(kimsia)** wrote on 2022-06-07T09:09:43.404736+00:00_
I get an invalid cloud-config warning despite everything working as expected.
This is the question i asked in superuser https://superuser.com/questions/1725127/invalid-config-for-cloud-init-but-apparently-still-works-how-do-i-remove-the
the cloud provider is DigitalOcean
this is not the full config
#cloud-config
package_update: true
package_upgrade: true
users:
- name: sammy
ssh-authorized-keys:
- ssh-rsa abcd...
- ssh-rsa efgh...
sudo: ['ALL=(ALL) NOPASSWD:ALL']
groups: sudo
shell: /bin/bash
See attached for the logs
Contributor guide
Research direction
Start with the provided cloud-config and the attached logs, then compare the warning with the DigitalOcean behavior described in the issue and the linked Launchpad report. Done means determining why this configuration is reported as invalid and ensuring the warning is removed or corrected without changing the working behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100