-
Notifications
You must be signed in to change notification settings - Fork 820
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
handlers.py WARNING failed posting event finish SUCCESS #2786
Comments
Launchpad user mahmoh(mahmoh) wrote on 2016-12-14T16:38:23.114199+00:00 Launchpad attachments: maas-failed-posting.tgz |
Launchpad user Andres Rodriguez(andreserl) wrote on 2016-12-14T16:44:16.176966+00:00 I believe we discussed it last week. If for whatever reason cloud-init fails to post events because MAAS may not accept them or similar, cloud-init shouldn't be failing and posting a failed event. |
Launchpad user mahmoh(mahmoh) wrote on 2016-12-14T16:45:21.109486+00:00 I've seen a couple of bugs with this same symptom but this doesn't appear to be match any of those that I could tell. These systems are setup with two networks, a public 10... and private 192.168.1.1/24, where the maas server is setup as the masquerading router gateway. The rack and region controller are configured to work via the router IP 192.168.1.1, DNS/DHCP on 192.168.1.1 with the same gateway specified on the untagged vlan. This is not a network that I control so there is a bit of uncertainty but it is odd that the systems (three in total) commission fine sometimes and deploy fine sometimes but not always. Any help to confirm this is not a MAAS problem would be appreciated. |
Launchpad user mahmoh(mahmoh) wrote on 2016-12-14T17:06:47.175641+00:00 Launchpad attachments: maas-dhcp.tgz |
Launchpad user mahmoh(mahmoh) wrote on 2016-12-14T17:12:46.131783+00:00 Launchpad attachments: maas-dhcp-journalctl.log |
Launchpad user mahmoh(mahmoh) wrote on 2016-12-14T17:20:40.957765+00:00 Verified no other DHCP server running on the private interface. |
Launchpad user mahmoh(mahmoh) wrote on 2016-12-14T17:58:18.956360+00:00 New bootstrap, IP's match up but I'm seeing a few odd things: NEW BOOTSTRAP: that appeared to work until I saw this: ubuntu login: [ 213.885990] cloud-init[2045]: Can not apply stage final, no datasource found! Likely bad things to come! |
Launchpad user mahmoh(mahmoh) wrote on 2016-12-14T18:00:00.821946+00:00 MAAS Server: $ ip a Why is it offering a Private IP to a MAC on the Public network?! ... |
Launchpad user mahmoh(mahmoh) wrote on 2016-12-14T19:07:30.824377+00:00 rackd — Missing connections to 1 region controller(s). Launchpad attachments: maas-rackd-problem.tgz |
Launchpad user mahmoh(mahmoh) wrote on 2016-12-14T19:07:52.074665+00:00 Launchpad attachments: maas-journalctl.log |
Launchpad user Dan Watkins(oddbloke) wrote on 2019-02-22T10:17:26.599808+00:00 Hi mahmoh, Thanks for filing this bug! Is this still an issue you are seeing with more recent versions of cloud-init? If it is, please do give us steps to reproduce and set it back to New. Thanks! Dan |
Launchpad user Launchpad Janitor(janitor) wrote on 2019-04-24T04:17:30.292429+00:00 [Expired for cloud-init because there has been no activity for 60 days.] |
Launchpad user Rudy LEONARD(rudyl) wrote on 2019-11-05T09:44:48.044559+00:00 Hello same issue (impossible to connect via ssh after deployment) with my config : MAAS 2.4.2 to reproduce the issue :
with these steps all is fine :
|
This bug was originally filed in Launchpad as LP: #1649951
Launchpad details
Launchpad user mahmoh(mahmoh) wrote on 2016-12-14T16:38:23.114199+00:00
I'm trying to [MAAS 2.1.2] deploy and am hitting intermittent problems, any help would be appreciated. The system below commissioned fine and was chosen to bootstrap Juju (2.0.2) but is now failing. I can't login or ssh in, so the network interface isn't getting provisioned properly even though it claims it is. Oddly, MAAS thinks the node should have a different IP [" ... 192.168.1.2 (Auto assign)"].
...
[ OK ] Reached target Network.
[ 58.581413] cloud-init[3350]: Cloud-init v. 0.7.8 running 'init' at Wed, 14 Dec 2016 16:20:18 +0000. Up 55.14 seconds.
[ 58.596442] cloud-init[3350]: ci-info: +++++++++++++++++++++++++++++++++++++++++Net device info++++++++++++++++++++++++++++++++++++++++++
[ 58.612404] cloud-init[3350]: ci-info: +---------------+------+-----------------------------+---------------+-------+-------------------+
[ 58.628393] cloud-init[3350]: ci-info: | Device | Up | Address | Mask | Scope | Hw-Address |
[ 58.644389] cloud-init[3350]: ci-info: +---------------+------+-----------------------------+---------------+-------+-------------------+
[ 58.660400] cloud-init[3350]: ci-info: | br-enP2p1s0f1 | True | 192.168.1.7 | 255.255.255.0 | . | 1c:1b:0d:01:d8:00 |
[ 58.676396] cloud-init[3350]: ci-info: | lo | True | 127.0.0.1 | 255.0.0.0 | . | . |
[ 58.692389] cloud-init[3350]: ci-info: | lo | True | ::1/128 | . | host | . |
[ 58.708390] cloud-init[3350]: ci-info: | enP2p1s0f2 | True | . | . | . | 1c:1b:0d:01:d8:01 |
[ 58.724391] cloud-init[3350]: ci-info: | enP2p1s0f2 | True | fe80::1e1b:dff:fe01:d801/64 | . | link | 1c:1b:0d:01:d8:01 |
[ 58.740392] cloud-init[3350]: ci-info: | enP2p1s0f1 | True | . | . | . | 1c:1b:0d:01:d8:00 |
[ 58.756396] cloud-init[3350]: ci-info: +---------------+------+-----------------------------+---------------+-------+-------------------+
[ 58.772389] cloud-init[3350]: ci-info: +++++++++++++++++++++++++++++++Route IPv4 info+++++++++++++++++++++++++++++++
[ 58.788390] cloud-init[3350]: ci-info: +-------+-------------+-------------+---------------+---------------+-------+
[ 58.804393] cloud-init[3350]: ci-info: | Route | Destination | Gateway | Genmask | Interface | Flags |
[ 58.820398] cloud-init[3350]: ci-info: +-------+-------------+-------------+---------------+---------------+-------+
[ 58.836392] cloud-init[3350]: ci-info: | 0 | 0.0.0.0 | 192.168.1.1 | 0.0.0.0 | br-enP2p1s0f1 | UG |
[ 58.852391] cloud-init[3350]: ci-info: | 1 | 192.168.1.0 | 0.0.0.0 | 255.255.255.0 | br-enP2p1s0f1 | U |
[ 58.868391] cloud-init[3350]: ci-info: +-------+-------------+-------------+---------------+---------------+-------+
[ 58.884390] cloud-init[3350]: 2016-12-14 16:20:22,403 - handlers.py[WARNING]: failed posting event: start: init-network/check-cache: attempting to read from cache [trust]
...
...
[ 265.585458] cloud-init[3913]: 2016-12-14 16:23:49,407 - handlers.py[WARNING]: failed posting event: finish: modules-final/config-package-update-upgrade-install: SUCCESS: config-package-update-upgrade-install previously ran
[ 268.585382] cloud-init[3913]: 2016-12-14 16:23:52,407 - handlers.py[WARNING]: failed posting event: start: modules-final/config-fan: running config-fan with frequency once-per-instance
[ 271.585995] cloud-init[3913]: 2016-12-14 16:23:55,408 - handlers.py[WARNING]: failed posting event: finish: modules-final/config-fan: SUCCESS: config-fan previously ran
[ 274.585181] cloud-init[3913]: 2016-12-14 16:23:58,407 - handlers.py[WARNING]: failed posting event: start: modules-final/config-landscape: running config-landscape with frequency once-per-instance
[ 277.585243] cloud-init[3913]: 2016-12-14 16:24:01,407 - handlers.py[WARNING]: failed posting event: finish: modules-final/config-landscape: SUCCESS: config-landscape previously ran
[ 280.586888] cloud-init[3913]: 2016-12-14 16:24:04,408 - handlers.py[WARNING]: failed posting event: start: modules-final/config-lxd: running config-lxd with frequency once-per-instance
[ 283.586615] cloud-init[3913]: 2016-12-14 16:24:07,408 - handlers.py[WARNING]: failed posting event: finish: modules-final/config-lxd: SUCCESS: config-lxd previously ran
[ 286.585808] cloud-init[3913]: 2016-12-14 16:24:10,407 - handlers.py[WARNING]: failed posting event: start: modules-final/config-puppet: running config-puppet with frequency once-per-instance
[ 289.585863] cloud-init[3913]: 2016-12-14 16:24:13,407 - handlers.py[WARNING]: failed posting event: finish: modules-final/config-puppet: SUCCESS: config-puppet previously ran
[ 292.585137] cloud-init[3913]: 2016-12-14 16:24:16,407 - handlers.py[WARNING]: failed posting event: start: modules-final/config-chef: running config-chef with frequency once-per-instance
[ 295.585322] cloud-init[3913]: 2016-12-14 16:24:19,407 - handlers.py[WARNING]: failed posting event: finish: modules-final/config-chef: SUCCESS: config-chef previously ran
[ 298.586097] cloud-init[3913]: 2016-12-14 16:24:22,408 - handlers.py[WARNING]: failed posting event: start: modules-final/config-salt-minion: running config-salt-minion with frequency once-per-instance
[ 301.586092] cloud-init[3913]: 2016-12-14 16:24:25,408 - handlers.py[WARNING]: failed posting event: finish: modules-final/config-salt-minion: SUCCESS: config-salt-minion previously ran
[ 304.585439] cloud-init[3913]: 2016-12-14 16:24:28,407 - handlers.py[WARNING]: failed posting event: start: modules-final/config-mcollective: running config-mcollective with frequency once-per-instance
[ 307.585243] cloud-init[3913]: 2016-12-14 16:24:31,407 - handlers.py[WARNING]: failed posting event: finish: modules-final/config-mcollective: SUCCESS: config-mcollective previously ran
[ 310.586398] cloud-init[3913]: 2016-12-14 16:24:34,408 - handlers.py[WARNING]: failed posting event: start: modules-final/config-rightscale_userdata: running config-rightscale_userdata with frequency once-per-instance
[ 313.585653] cloud-init[3913]: 2016-12-14 16:24:37,407 - handlers.py[WARNING]: failed posting event: finish: modules-final/config-rightscale_userdata: SUCCESS: config-rightscale_userdata previously ran
[ 316.586447] cloud-init[3913]: 2016-12-14 16:24:40,408 - handlers.py[WARNING]: failed posting event: start: modules-final/config-scripts-vendor: running config-scripts-vendor with frequency once-per-instance
[ 319.586427] cloud-init[3913]: 2016-12-14 16:24:43,408 - handlers.py[WARNING]: failed posting event: finish: modules-final/config-scripts-vendor: SUCCESS: config-scripts-vendor previously ran
[ 322.585346] cloud-init[3913]: 2016-12-14 16:24:46,407 - handlers.py[WARNING]: failed posting event: start: modules-final/config-scripts-per-once: running config-scripts-per-once with frequency once
...
The text was updated successfully, but these errors were encountered: