bootstrap fails: A conflicting conditional operation...

Bug #1183571 reported by Marco Ceppi
26
This bug affects 6 people
Affects Status Importance Assigned to Milestone
juju-core
Invalid
Low
Unassigned

Bug Description

Sometimes, I run a bootstrap or destroy-environment, even though nothing is going on with my machine (that I can tell). I'll sometimes get:

error: A conflicting conditional operation is currently in progress against this resource. Please try again.

Could these possibly include WHAT conflicting conditional operation is happening?

Tags: cmdline hours
Tim Penhey (thumper)
Changed in juju-core:
status: New → Triaged
importance: Undecided → Low
tags: added: bitesize cmdline
removed: cli-ui
Curtis Hovey (sinzui)
tags: added: hours
removed: bitesize
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

This happens to me too. I'm using 1.16.5 and trying to bootstrap on us-west-2:

$ juju bootstrap -v --constraints mem=1G
verbose is deprecated with the current meaning, use show-log
2014-01-31 14:01:27 INFO juju.provider.ec2 ec2.go:193 opening environment "andreas-aws"
2014-01-31 14:01:29 INFO juju.environs.tools tools.go:181 filtering tools by released version
2014-01-31 14:01:29 INFO juju.environs.tools tools.go:85 reading tools with major.minor version 1.16
2014-01-31 14:01:29 INFO juju.environs.tools tools.go:96 filtering tools by series: precise
2014-01-31 14:03:43 WARNING juju.environs open.go:258 failed to write bootstrap-verify file: cannot make S3 control bucket: A conflicting conditional operation is currently in progress against this resource. Please try again.
2014-01-31 14:03:43 ERROR juju supercommand.go:282 provider storage is not writable

environments:
  andreas-aws:
    type: ec2
    admin-secret: somesecret
    # globally unique S3 bucket name
    control-bucket: juju-somebucket
    default-series: precise
    # region defaults to us-east-1, override if required
    region: us-west-2
    access-key: some-access
    secret-key: some-secret

If I switch to us-east-1 it works.

summary: - A conflicting conditional operation...
+ bootstrap fails: A conflicting conditional operation...
Revision history for this message
Chad Smith (chad.smith) wrote :

+1 on this issue, could it be that machine-0 instance isn't cleaned up from S3 for a while. I found if I waited 30 mins after a destroy-environment, that error went away.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

I started with a fresh environment. The only thing I have is ~/.juju/environments.yaml, nothing else in ~/.juju. I selected a new control bucket name, random. Then I bootstrap and I get this "conflict" error.

What could be possibly conflicting? What other operation could be happening?

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

The error happens when I try to create a s3 bucket natively, or delete an existing one, without juju. So something is going on with my aws account.

Revision history for this message
Nicolas Thomas (thomnico) wrote :

Affects me on 1.17.2 ..

Got this:
2014-02-17 11:04:18 DEBUG juju.environs.configstore disk.go:63 Making /home/thomas/.juju/environments
2014-02-17 11:04:18 INFO juju.environs open.go:156 environment info already exists; using New not Prepare
2014-02-17 11:04:18 INFO juju.provider.ec2 ec2.go:200 opening environment "aws"
2014-02-17 11:04:19 WARNING juju.environs open.go:258 failed to write bootstrap-verify file: cannot make S3 control bucket: A conflicting conditional operation is currently in progress against this resource. Please try again.
2014-02-17 11:04:19 ERROR juju.cmd supercommand.go:294 provider storage is not writable

Revision history for this message
Dave Cheney (dave-cheney) wrote : Re: [Bug 1183571] Re: bootstrap fails: A conflicting conditional operation...

What is the name of the bucket and the region you are creating it in ?

On Mon, Feb 17, 2014 at 10:33 PM, Nicolas Thomas <<email address hidden>
> wrote:

> Affects me on 1.17.2 ..
>
> Got this:
> 2014-02-17 11:04:18 DEBUG juju.environs.configstore disk.go:63 Making
> /home/thomas/.juju/environments
> 2014-02-17 11:04:18 INFO juju.environs open.go:156 environment info
> already exists; using New not Prepare
> 2014-02-17 11:04:18 INFO juju.provider.ec2 ec2.go:200 opening environment
> "aws"
> 2014-02-17 11:04:19 WARNING juju.environs open.go:258 failed to write
> bootstrap-verify file: cannot make S3 control bucket: A conflicting
> conditional operation is currently in progress against this resource.
> Please try again.
> 2014-02-17 11:04:19 ERROR juju.cmd supercommand.go:294 provider storage is
> not writable
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1183571
>
> Title:
> bootstrap fails: A conflicting conditional operation...
>
> Status in juju-core:
> Triaged
>
> Bug description:
> Sometimes, I run a bootstrap or destroy-environment, even though
> nothing is going on with my machine (that I can tell). I'll sometimes
> get:
>
> error: A conflicting conditional operation is currently in progress
> against this resource. Please try again.
>
> Could these possibly include WHAT conflicting conditional operation is
> happening?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1183571/+subscriptions
>

Revision history for this message
Cheryl Jennings (cherylj) wrote :

We no longer use the S3 control bucket. How we manage storage has changed significantly since the bug was first reported.

Changed in juju-core:
status: Triaged → Invalid
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.