Can't install wordpress on local provider with trusty host

Bug #1317644 reported by Nate Finch
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wordpress (Juju Charms Collection)
Fix Released
High
Charles Butler

Bug Description

Deploying wordpress to the local provider on trusty deploys the precise version of wordpress (the only version available), which hits this bug during the install hook: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/969299

The key line is this error from the install hook's output:
failed to fstat previous diversions file: No such file or directory

Revision history for this message
Curtis Hovey (sinzui) wrote :

I cannot reproduce this under my conditions, and there are a lot:
    localhost: trusty updated this morning
    juju: 1.19.1
    juju-local: 1.19.1
    default-series: trusty

I deployed 3 wordpress charms from different sources:
    local trusty:
        juju deploy --repository=/home/curtis/Work/juju-charms local:trusty/wordpress fat-wp
    store precise:
        juju deploy cs:precise/wordpress cs-wp
    local precise
        juju deploy --repository=/home/curtis/Work/juju-charms local:precise/wordpress lc-wp

The store is on 96, my forks are at 93. My forks are series agnostic.

$ juju status
environment: local
machines:
  "0":
    agent-state: started
    agent-version: 1.19.1.1
    dns-name: localhost
    instance-id: localhost
    series: trusty
    state-server-member-status: has-vote
  "1":
    agent-state: started
    agent-version: 1.19.1.1
    dns-name: 10.0.3.175
    instance-id: curtis-local-machine-1
    series: trusty
    hardware: arch=amd64
  "2":
    agent-state: started
    agent-version: 1.19.1.1
    dns-name: 10.0.3.96
    instance-id: curtis-local-machine-2
    series: precise
    hardware: arch=amd64
  "3":
    agent-state: started
    agent-version: 1.19.1.1
    dns-name: 10.0.3.93
    instance-id: curtis-local-machine-3
    series: precise
    hardware: arch=amd64
services:
  cs-wp:
    charm: cs:precise/wordpress-21
    exposed: false
    relations:
      loadbalancer:
      - cs-wp
    units:
      cs-wp/0:
        agent-state: started
        agent-version: 1.19.1.1
        machine: "2"
        open-ports:
        - 80/tcp
        public-address: 10.0.3.96
  fat-wp:
    charm: local:trusty/wordpress-96
    exposed: false
    relations:
      loadbalancer:
      - fat-wp
    units:
      fat-wp/0:
        agent-state: started
        agent-version: 1.19.1.1
        machine: "1"
        open-ports:
        - 80/tcp
        public-address: 10.0.3.175
  lc-wp:
    charm: local:precise/wordpress-93
    exposed: false
    relations:
      loadbalancer:
      - lc-wp
    units:
      lc-wp/0:
        agent-state: started
        agent-version: 1.19.1.1
        machine: "3"
        open-ports:
        - 80/tcp
        public-address: 10.0.3.93

Changed in wordpress (Juju Charms Collection):
status: New → In Progress
assignee: nobody → Charles Butler (lazypower)
importance: Undecided → High
Revision history for this message
Charles Butler (lazypower) wrote :

I'm not seeing the same behavior. I've found other odd behavior, but have been unable to reproduce the OP report.

What i've tried is very similar to Curtis's findings, i've deployed from the store, local, local re-series branded to trusty.

Everything appears to be in order on my runs.

Can you reproduce and provide further insight into the specific conditions that triggered this? Charm revision, juju version, and host series?

Changed in wordpress (Juju Charms Collection):
status: In Progress → Incomplete
Revision history for this message
Matthew Ruffell (mruffell) wrote :

This bug has been fixed in the major maintenance performed on the wordpress charm, now known as cs:wordpress-0.

Precise and Trusty has been dropped from supported series, and Xenial, Bionic and soon Focal are supported.

For more information, see Bug 1827164.

Changed in wordpress (Juju Charms Collection):
status: Incomplete → Fix Released
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.