bootstrap tries to write to /var/lib/juju on local machine

Bug #1542988 reported by Dave Cheney
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
Medium
Unassigned

Bug Description

2016-02-08 06:20:42 DEBUG juju.provider.common bootstrap.go:318 connection attempt for 54.79.164.245 failed: Warning: Permanently added '54.79.164.245' (ECDSA) to the list of known hosts.
/var/lib/juju/nonce.txt does not exist
2016-02-08 06:20:48 DEBUG juju.provider.common bootstrap.go:318 connection attempt for 54.79.164.245 failed: /var/lib/juju/nonce.txt does not exist

^ this will never work, my user does not own those paths.

Revision history for this message
Dave Cheney (dave-cheney) wrote :

This message may be coming from the ssh child process.

description: updated
Changed in juju-core:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Matt Bruzek (mbruzek) wrote :

I encountered this same error when working on trying to bootstrap xenial machine on Amazon today.

1.26-alpha3-vivid-amd64

2016-02-10 16:29:43 DEBUG juju.provider.common bootstrap.go:298 connection attempt for 54.174.246.24
4 failed: Warning: Permanently added '54.174.246.244' (ECDSA) to the list of known hosts.
/var/lib/juju/nonce.txt does not exist
2016-02-10 16:29:50 DEBUG juju.provider.common bootstrap.go:298 connection attempt for 54.174.246.24
4 failed: /var/lib/juju/nonce.txt does not exist
2016-02-10 16:29:56 DEBUG juju.provider.common bootstrap.go:298 connection attempt for 54.174.246.24
4 failed: /var/lib/juju/nonce.txt does not exist
2016-02-10 16:30:03 DEBUG juju.provider.common bootstrap.go:298 connection attempt for 54.174.246.24
4 failed: /var/lib/juju/nonce.txt does not exist

I saw this error with the remote machine's ip addresses so thought Juju was looking for the file on the remote machine.

Can you clarify if this is on the host machine or the bootstrap node?

tags: added: 2.0-count
affects: juju-core → juju
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.

Changed in juju:
status: Triaged → Expired
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.