Overview

Request 902795 revoked

- Update to 21.2
* Add \r\n check for SSH keys in Azure
* Azure: adding support for consuming userdata from IMDS
* Add Vultr support
* Fix unpickle for source paths missing run_dir
* sysconfig: use BONDING_MODULE_OPTS on SUSE
* make suse and sles support 127.0.1.1
* Azure: Support for VMs without ephemeral resource disks.
* azure: case-insensitive UUID to avoid new IID during kernel upgrade
* many more improvements and fixes, see upstream changelog
- Drop patches:
* cloud-init-tests-set-exec.patch
* cloud-init-no-tempnet-oci.patch
* cloud-init-after-kvp.diff
* cloud-init-recognize-hpc.patch
* cloud-init-azure-def-usr-pass.patch
* use_arroba_to_include_sudoers_directory-bsc_1181283.patch
* cloud-init-bonding-opts.patch
* cloud-init-log-file-mode.patch
* cloud-init-no-pwd-in-log.patch

Markéta Machová's avatar
Markéta Machová (mcalabkova) -
author source maintainer

was broken by new setuptools in Staging:F

Benjamin Greiner's avatar
Benjamin Greiner (bnavigator) -

It's still failing in Staging:F even without the updated setuptools :(((

Benjamin Greiner's avatar
Benjamin Greiner (bnavigator) -

Its' actually python-Jinja2. Proof:

osc co openSUSE:Factory:Staging:F/cloud-init
cd openSUSE:Factory:Staging:F/cloud-init
osc build # fails
osc getbinaries openSUSE:Factory/python-Jinja2 standard x86_64
osc build -p binaries # passes
osc getbinaries devel:languages:python/python-setuptools openSUSE_Tumbleweed x86_64
osc build -p binaries # still passes
Antonio Larrosa's avatar
Antonio Larrosa (alarrosa) -

Thanks for finding out where the problem exactly was! With that, I managed to find the patch from upstream that fixes cloud-init to build with the recent Jinja2 version. I submitted it in https://build.opensuse.org/request/show/905232 in the hope that it can help to get reviewed faster.

Benjamin Greiner's avatar
Benjamin Greiner (bnavigator) -

excellent!

Robert Schweikert's avatar
Robert Schweikert (rjschwei) -
reviewer target maintainer

Would be a lot easier if this were running through the Cloud:Tools:Next project. I am out tomorrow and Friday, will try to get to this early next week. Also need to give some more thought about the cache clearing patch based on upstream discussion. Might want hose in the package before a version upgrade so they can easily be pushed to SLE 12 before the cloud-init version in SLE 12 gets frozen.

So PLEASE do not accept this just yet.

Antonio Larrosa's avatar
Antonio Larrosa (alarrosa) -

Hi, there are currently ~42 python packages blocked by this in Staging:F, so it would be great if you could look into it and forward it to Factory. I don't know anything about cloud-init, but I checked that this update fixes the build failure in Staging:F.

Thanks!

Benjamin Greiner's avatar
Benjamin Greiner (bnavigator) -

I think it would also be okay to unstage the python-Jinja2 update until cloud-init is fixed so that the other python packages can be merged.

In the long run, in my humble opinion, there should not be anything blocking a tumbleweed update because of some SLE12 compatibility.

Robert Schweikert's avatar
Robert Schweikert (rjschwei) -
reviewer target maintainer

If we have packages that depend on cloud-init that sounds fundamentally incorrect

Markéta Machová's avatar
Markéta Machová (mcalabkova) -
author source maintainer

what is wrong with my request? How can I fix it?

Antonio Larrosa's avatar
Antonio Larrosa (alarrosa_factory) -

It's not that those packages depend on cloud-init. The problem is that the current cloud-init version in Factory fails to build with updated python packages. So we can't accept the SRs in Staging:F (which currently contains ~46 python packages) until cloud-init is fixed. This SR allows cloud-init to build with the updated packages and so when it's submitted to Factory, it would unblock all packages in Staging:F.

Staging Bot's avatar
Staging Bot (staging-bot) -

@jdsn, @rjschwei: review reminder

Robert Schweikert's avatar
Robert Schweikert (rjschwei) -
reviewer target maintainer

I have to test whether the new code for detecting iscsi boot configuration works with SLES.

Request History
Markéta Machová's avatar

mcalabkova created request

- Update to 21.2
* Add \r\n check for SSH keys in Azure
* Azure: adding support for consuming userdata from IMDS
* Add Vultr support
* Fix unpickle for source paths missing run_dir
* sysconfig: use BONDING_MODULE_OPTS on SUSE
* make suse and sles support 127.0.1.1
* Azure: Support for VMs without ephemeral resource disks.
* azure: case-insensitive UUID to avoid new IID during kernel upgrade
* many more improvements and fixes, see upstream changelog
- Drop patches:
* cloud-init-tests-set-exec.patch
* cloud-init-no-tempnet-oci.patch
* cloud-init-after-kvp.diff
* cloud-init-recognize-hpc.patch
* cloud-init-azure-def-usr-pass.patch
* use_arroba_to_include_sudoers_directory-bsc_1181283.patch
* cloud-init-bonding-opts.patch
* cloud-init-log-file-mode.patch
* cloud-init-no-pwd-in-log.patch

Robert Schweikert's avatar

rjschwei declined request

Breaks iscsi setup connection from the kernel commandline. The cloud-init-no-tempnet-oci.patch patch probably needs forward porting instead of being dropped.

Markéta Machová's avatar

mcalabkova revoked request

ok, I have no experience with this stuff, so let somebody more experienced do the porting

openSUSE Build Service is sponsored by
Places