[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand

This bug was fixed in the package cloud-init - 24.1.3-0ubuntu1~20.04.4 --- cloud-init (24.1.3-0ubuntu1~20.04.4) focal; urgency=medium * cherry-pick 51c6569f: fix(snapd): ubuntu do not snap refresh when snap absent (LP: #2064132) - fix in 24.1.3-0ubuntu1~20.04.2 did not

[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand

This bug was fixed in the package cloud-init - 24.1.3-0ubuntu1~22.04.4 --- cloud-init (24.1.3-0ubuntu1~22.04.4) jammy; urgency=medium * cherry-pick 51c6569f: fix(snapd): ubuntu do not snap refresh when snap absent (LP: #2064132) - fix in 24.1.3-0ubuntu1~20.04.2 did not

[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand

This bug was fixed in the package cloud-init - 24.1.3-0ubuntu1~23.10.5 --- cloud-init (24.1.3-0ubuntu1~23.10.5) mantic; urgency=medium * cherry-pick 51c6569f: fix(snapd): ubuntu do not snap refresh when snap absent (LP: #2064132) - fix in 24.1.3-0ubuntu1~23.10.3 did not

[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand

# verification complete mantic # csmith@midtown:~$ lxc launch ubuntu-daily:mantic test-m Creating test-m Starting test-m file push myfile.yaml csmith@midtown:~$ lxc file push myfile.yaml test-m/ csmith@midtown:~$ lxc file push setup_proposed.sh test-m/

[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand

test verification complete jammy csmith@midtown:~$ lxc launch ubuntu-daily:jammy test-jammy Creating test-jammy Starting test-jammy csmith@midtown:~$ lxc file push myfile.yaml test-jammy/ csmith@midtown:~$ lxc file push setup_proposed.sh test-jammy/

[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand

Thanks Timo! focal verification complete = csmith@midtown:~$ lxc launch ubuntu-daily:focal test-focal Creating test-focal Starting test-focal csmith@midtown:~$ lxc exec test-focal bash root@test-focal:~# hostname # confirm test-focal from standard meta-data test-focal root@test-focal:~#

[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand

Hello Brett, or anyone else affected, Accepted cloud-init into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/24.1.3-0ubuntu1~22.04.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package.

[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand

Hello Brett, or anyone else affected, Accepted cloud-init into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/24.1.3-0ubuntu1~23.10.5 in a few hours, and then in the -proposed repository. Please help us by testing this new

[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand

mantic verification complete csmith@midtown:~$ lxc launch ubuntu-daily:mantic test-mantic Creating test-mantic Starting test-mantic csmith@midtown:~$ lxc file push myfile.yaml test-mantic/ csmith@midtown:~$ lxc file push setup_proposed.sh test-mantic/ csmith@midtown:~$ lxc exec

[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand

= jammy verification complete csmith@midtown:~$ lxc launch ubuntu-daily:jammy test-jammy Creating test-jammy Starting test-jammy csmith@midtown:~$ lxc file push myfile.yaml test-jammy/ csmith@midtown:~$ lxc file push setup_proposed.sh test-jammy/ csmith@midtown:~$ lxc exec test-jammy bash

[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand

focal verification complete csmith@midtown:~$ lxc file push myfile.yaml test-focal/ csmith@midtown:~$ lxc exec test-focal bash root@test-focal:~# # confirm usage failure root@test-focal:~# cloud-init -f /myfile.yaml init usage: /usr/bin/cloud-init [-h] [--version] [--debug] [--force]

[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand

** Description changed: [ Impact ] - * Environments or scripts which directly call cloud-init subcommands and -provide an optional -f or --file argument to inject supplemental -configuration after first boot will receive usage errors on the command -line which will break any

[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand

I'm told that for noble and later, the change in behavior that this SRU is reverting will not be applied, as there it's intended. I'll thus make this clear by adding noble and Oracular tasks and marking them as invalid. ** Also affects: cloud-init (Ubuntu Noble) Importance: Undecided

[Bug 2064300] Re: cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand

** Summary changed: - cli behavior changed + cli behavior changed for commands passing optional --file argument to cloud-init init, modules or single subcommand -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.