canonical / cloud-init

Official upstream for the cloud-init: cloud instance initialization
https://cloud-init.io/
Other
2.74k stars 831 forks source link

WARNING in logs due to missing python-jsonschema #3032

Closed ubuntu-server-builder closed 1 year ago

ubuntu-server-builder commented 1 year ago

This bug was originally filed in Launchpad as LP: #1724354

Launchpad details
affected_projects = ['cloud-init (Ubuntu)', 'cloud-init (Ubuntu Xenial)', 'cloud-init (Ubuntu Zesty)', 'cloud-init (Ubuntu Artful)']
assignee = None
assignee_name = None
date_closed = 2017-12-14T21:02:31.405441+00:00
date_created = 2017-10-17T19:40:43.786517+00:00
date_fix_committed = 2017-10-18T20:13:02.292966+00:00
date_fix_released = 2017-12-14T21:02:31.405441+00:00
id = 1724354
importance = low
is_complete = True
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1724354
milestone = None
owner = smoser
owner_name = Scott Moser
private = False
status = fix_released
submitter = smoser
submitter_name = Scott Moser
tags = ['verification-done', 'verification-done-artful', 'verification-done-xenial', 'verification-done-zesty']
duplicates = []

Launchpad user Scott Moser(smoser) wrote on 2017-10-17T19:40:43.786517+00:00

=== Begin SRU Template === [Impact] If python3-jsonschema is not installed, then WARNING will be written to console log and to /var/log/cloud-init.log with certain cloud-config data is provided.

python3-jsonschema is a soft dependency of cloud-init and specically not listed in 16.04 and 17.04 packaging as it was not a dependency in the versions of cloud-init originally released then.

The WARNING is only "scary", and has no negative affect on runtime.

[Test Case] The change for this bug modified the integration test suite so that WARN in /var/log/cloud-init would trigger a test failure. Running the integration testsuite would show this failure with that test now in place.

A manual test can be done though as follows.

$ cat > my.cfg <<EOF

cloud-config

bootcmd:   - "cat /proc/uptime > /run/bootcmd-works" runcmd:   - "cat /proc/uptime > /run/runcmd-works" EOF

$ for r in zesty xenial; do    lxc init $r-proposed $r-info &&    lxc-pstart $r-info \      sh -c 'dpkg-query --show cloud-init; cat /etc/cloud/build.info' &&      lxc delete --force $r-info; done

show container info just to show versions.

$ for r in zesty xenial; do    lxc init $r-proposed $r-info >/dev/null 2>&1 && echo == $r-info == &&    lxc-pstart $r-info -- \       sh -xc 'dpkg-query --show cloud-init; cat /etc/cloud/build.info' &&    lxc delete --force $r-info; done

launch an instance of each release and grab logs.

$ for rel in xenial zesty; do    n=$rel-1724354    lxc launch $rel-proposed $n "--config=user.user-data=$(cat my.cfg)"    lxc exec $n -- sh -c \       'while ! [ -e /run/cloud-init/result.json ]; do echo -n .; sleep 1; done; echo'    lxc file pull $n/var/log/cloud-init.log $n-cloud-init.log done

check that 1724354 is installed.

$ grep "WARN" *-1724354-cloud-init.log

[Regression Potential] Highest chance for regression would be in the integration test suite. The only change in code path is in cloudinit/config/schema.py:  - logging.warning(  + logging.debug(

[Other Info] Upstream commit at   https://git.launchpad.net/cloud-init/commit/?id=41152f10ddb

Note, this is not specifically in artful at this point, but also note that this bug does not affect artful. Artful's package has a depends on python3-jsonschema, so it will not demonstrate the issue.

=== End SRU Template ===

$ dpkg-query --show cloud-init cloud-init 17.1-18-gd4f70470-0ubuntu1~16.04.1

$ sudo cat /var/lib/cloud/instance/user-data.txt

cloud-config

bootcmd:   - "cat /proc/uptime > /run/bootcmd-works" runcmd:   - "cat /proc/uptime > /run/runcmd-works"

$ grep WARN /var/log/cloud-init.log 2017-10-17 19:08:10,509 - schema.py[WARNING]: Ignoring schema validation. python-jsonschema is not present 2017-10-17 19:08:10,586 - schema.py[WARNING]: Ignoring schema validation. python-jsonschema is not present 2017-10-17 19:08:14,651 - schema.py[WARNING]: Ignoring schema validation. python-jsonschema is not present

ubuntu-server-builder commented 1 year ago

Launchpad user Brian Murray(brian-murray) wrote on 2017-10-19T18:11:47.337934+00:00

Hello Scott, or anyone else affected,

Accepted cloud-init into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/17.1-18-gd4f70470-0ubuntu1~17.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

ubuntu-server-builder commented 1 year ago

Launchpad user Brian Murray(brian-murray) wrote on 2017-10-19T18:15:19.831472+00:00

Hello Scott, or anyone else affected,

Accepted cloud-init into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/17.1-18-gd4f70470-0ubuntu1~16.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

ubuntu-server-builder commented 1 year ago

Launchpad user Chris Halse Rogers(raof) wrote on 2017-10-25T00:33:44.444285+00:00

Hello Scott, or anyone else affected,

Accepted cloud-init into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/17.1-25-g17a15f9e-0ubuntu1~17.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

ubuntu-server-builder commented 1 year ago

Launchpad user Chris Halse Rogers(raof) wrote on 2017-10-25T03:20:56.993235+00:00

Hello Scott, or anyone else affected,

Accepted cloud-init into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/17.1-25-g17a15f9e-0ubuntu1~17.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

ubuntu-server-builder commented 1 year ago

Launchpad user Chris Halse Rogers(raof) wrote on 2017-10-25T03:29:43.167199+00:00

Hello Scott, or anyone else affected,

Accepted cloud-init into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/17.1-25-g17a15f9e-0ubuntu1~16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

ubuntu-server-builder commented 1 year ago

Launchpad user Chad Smith(chad.smith) wrote on 2017-10-25T22:00:07.224389+00:00

Ran the following script for SRU verification, we expect Artful to carry a strict dependency on python3-jsonschema so no messages about "Ignoring schema validation" will exist. Xenial and Zesty don't have a package dependency for jsonschema defined, so debug message (not warning) should exist.

!/bin/bash

cat > my.cfg <<EOF

cloud-config

bootcmd:

for release in artful; do ref="$release-proposed"; echo "$release START --------------"; lxc-proposed-snapshot -p -P $release $ref; lxc init $ref test-$release; lxc config set test-$release user.user-data - < my.cfg; lxc start test-$release; lxc exec test-$release -- sh -c 'while ! [ -e /run/cloud-init/result.json ]; do echo -n .; sleep 1; done; echo'; lxc exec test-$release -- cat /run/cloud/build.info; lxc exec test-$release -- grep 'Ignoring schema validation' /var/log/cloud-init.log; done

=== Abridged SRU output === xenial START -------------- Creating xenial-proposed-204712498 ... Preparing to unpack .../cloud-init_17.1-25-g17a15f9e-0ubuntu1~16.04.1_all.deb ...

Creating test-xenial ........ build_name: server serial: 20171024 2017-10-25 21:55:45,845 - schema.py[DEBUG]: Ignoring schema validation. python-jsonschema is not present 2017-10-25 21:55:45,866 - schema.py[DEBUG]: Ignoring schema validation. python-jsonschema is not present 2017-10-25 21:55:48,668 - schema.py[DEBUG]: Ignoring schema validation. python-jsonschema is not present zesty START -------------- Creating zesty-proposed-248586300 ... Preparing to unpack .../cloud-init_17.1-25-g17a15f9e-0ubuntu1~17.04.1_all.deb ... Creating test-zesty .......... build_name: server serial: 20171024 2017-10-25 21:57:24,302 - schema.py[DEBUG]: Ignoring schema validation. python-jsonschema is not present 2017-10-25 21:57:24,325 - schema.py[DEBUG]: Ignoring schema validation. python-jsonschema is not present 2017-10-25 21:57:27,818 - schema.py[DEBUG]: Ignoring schema validation. python-jsonschema is not present

artful START -------------- # no schema validation messages Creating artful-proposed-3130329978 ... Get:1 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 cloud-init all 17.1-25-g17a15f9e-0ubuntu1~17.10.1 [333 kB] ... Creating test-artful .................. build_name: server serial: 20171024

=== End Abridged SRU output ===

ubuntu-server-builder commented 1 year ago

Launchpad user Launchpad Janitor(janitor) wrote on 2017-10-26T08:49:10.714791+00:00

This bug was fixed in the package cloud-init - 17.1-25-g17a15f9e-0ubuntu1~17.10.1


cloud-init (17.1-25-g17a15f9e-0ubuntu1~17.10.1) artful-proposed; urgency=medium

ubuntu-server-builder commented 1 year ago

Launchpad user Launchpad Janitor(janitor) wrote on 2017-11-02T17:55:22.957773+00:00

This bug was fixed in the package cloud-init - 17.1-25-g17a15f9e-0ubuntu1~17.10.1


cloud-init (17.1-25-g17a15f9e-0ubuntu1~17.10.1) artful-proposed; urgency=medium

ubuntu-server-builder commented 1 year ago

Launchpad user Brian Murray(brian-murray) wrote on 2017-11-02T17:55:35.390399+00:00

The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

ubuntu-server-builder commented 1 year ago

Launchpad user Łukasz Zemczak(sil2100) wrote on 2017-11-07T17:07:51.882521+00:00

Hello Scott, or anyone else affected,

Accepted cloud-init into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/17.1-27-geb292c18-0ubuntu1~17.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

ubuntu-server-builder commented 1 year ago

Launchpad user Łukasz Zemczak(sil2100) wrote on 2017-11-07T17:18:17.651961+00:00

Hello Scott, or anyone else affected,

Accepted cloud-init into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/17.1-27-geb292c18-0ubuntu1~16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

ubuntu-server-builder commented 1 year ago

Launchpad user Chad Smith(chad.smith) wrote on 2017-11-07T20:18:54.577797+00:00

=== Abridged SRU validation output === $ cat > my.cfg <<EOF

cloud-config

bootcmd:

$ for release in xenial zesty artful; do ref="$release-proposed"; echo "$release START --------------"; lxc-proposed-snapshot -p -P $release $ref; lxc init $ref test-$release; lxc config set test-$release user.user-data - < my.cfg; lxc start test-$release; lxc exec test-$release -- sh -c 'while ! [ -e /run/cloud-init/result.json ]; do echo -n .; sleep 1; done; echo'; lxc exec test-$release -- dpkg-query --show cloud-init; lxc exec test-$release -- grep 'Ignoring schema' /var/log/cloud-init.log; lxc exec test-$release -- dpkg-query --show python3-jsonschema; done

xenial START -------------- Creating xenial-proposed-21323830 -P -- Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 cloud-init all 17.1-27-geb292c18-0ubuntu1~16.04.1 [341 kB] Creating test-xenial ........ cloud-init 17.1-27-geb292c18-0ubuntu1~16.04.1 2017-11-07 20:00:33,875 - schema.py[DEBUG]: Ignoring schema validation. python-jsonschema is not present 2017-11-07 20:00:33,898 - schema.py[DEBUG]: Ignoring schema validation. python-jsonschema is not present 2017-11-07 20:00:36,716 - schema.py[DEBUG]: Ignoring schema validation. python-jsonschema is not present dpkg-query: no packages found matching python3-jsonschema

zesty START -------------- Creating zesty-proposed-103427244 -P -- Get:1 http://archive.ubuntu.com/ubuntu zesty-proposed/main amd64 cloud-init all 17.1-27-geb292c18-0ubuntu1~17.04.1 [339 kB] Creating test-zesty ........... cloud-init 17.1-27-geb292c18-0ubuntu1~17.04.1 2017-11-07 20:02:13,151 - schema.py[DEBUG]: Ignoring schema validation. python-jsonschema is not present 2017-11-07 20:02:13,181 - schema.py[DEBUG]: Ignoring schema validation. python-jsonschema is not present 2017-11-07 20:02:17,111 - schema.py[DEBUG]: Ignoring schema validation. python-jsonschema is not present dpkg-query: no packages found matching python3-jsonschema

artful START -------------- Creating artful-proposed-111528348 -P -- Get:1 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 cloud-init all 17.1-27-geb292c18-0ubuntu1~17.10.1 [332 kB] Creating test-artful ...................

artful START -------------- # Note no warnings because python-jsonschema is installed by pkg deps cloud-init 17.1-27-geb292c18-0ubuntu1~17.10.1 python3-jsonschema 2.5.1-6

=== End Abridged SRU validation output ===

ubuntu-server-builder commented 1 year ago

Launchpad user Launchpad Janitor(janitor) wrote on 2017-11-14T22:23:59.287002+00:00

This bug was fixed in the package cloud-init - 17.1-27-geb292c18-0ubuntu1~17.04.1


cloud-init (17.1-27-geb292c18-0ubuntu1~17.04.1) zesty-proposed; urgency=medium

cloud-init (17.1-25-g17a15f9e-0ubuntu1~17.04.1) zesty-proposed; urgency=medium

cloud-init (17.1-18-gd4f70470-0ubuntu1~17.04.2) zesty-proposed; urgency=medium

cloud-init (17.1-18-gd4f70470-0ubuntu1~17.04.1) zesty-proposed; urgency=medium

ubuntu-server-builder commented 1 year ago

Launchpad user Launchpad Janitor(janitor) wrote on 2017-11-15T01:07:42.077466+00:00

This bug was fixed in the package cloud-init - 17.1-27-geb292c18-0ubuntu1~16.04.1


cloud-init (17.1-27-geb292c18-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

cloud-init (17.1-25-g17a15f9e-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

cloud-init (17.1-18-gd4f70470-0ubuntu1~16.04.2) xenial-proposed; urgency=medium

cloud-init (17.1-18-gd4f70470-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

ubuntu-server-builder commented 1 year ago

Launchpad user Scott Moser(smoser) wrote on 2017-12-14T21:02:33.915488+00:00

This bug is believed to be fixed in cloud-init in 1705804. If this is still a problem for you, please make a comment and set the state back to New

Thank you.