Storage remains in pending state

Marking as Wont' Fix for 2.0 and 2.1 since we are not planning to release another versions in these series.

We cannot tell anything from these logs. The MAAS logs don't include the /machines/?op=allocate request, and the controller logs don't contain the storage provisioner actions. Can you please provide the full logs?

@axw I just send you some extra logs from another installation that is experiencing the same issue reported here.

- Aren't you able to reproduce the issue with the steps exposed on this bug? If not,
please let me know to clarify any step, as I am able to reproduce this all the time.

Jorge, I do not have a readily available MAAS to test this on. As you can easily reproduce the issue, I'm asking you for the information to diagnose.

Re extra logs, I am unable to access the system that you sent me the link to. If the contents are sensitive, please put them on private-fileshare.

@axwalk, I sent you a couple of extra logs via private-fileshare for you to review.

Jorge, this sounds suspiciously like lp:1674148. Unfortunately the logs don't have the detail required, as the logging config was not set on the controller model. To confirm that this is the same problem, please do the following:

    juju model-config -m controller logging-config='<root>=DEBUG;unit=TRACE;maas=TRACE'

(setting <root>=TRACE would be so overwhelming as to be unhelpful)

@axw

Hello, I just reproduced this bug with a new installation, same behavior as expressed on this bug description.

Attached you can find the Juju controller logs in TRACE level, as well
as the MAAS logs.

Please let me know if all the important information is contained on the
attached files.

Thanks.

Additional information that might be relevant.

ubuntu@maas-master:~$ sudo lsblk --exclude 1,2,7 -d -P -o NAME,RO,RM,MODEL,ROTA,MAJ:MIN,SERIAL -x MAJ:MIN
NAME="vda" RO="0" RM="0" MODEL="" ROTA="1" MAJ:MIN="253:0" SERIAL=""
NAME="vdb" RO="0" RM="0" MODEL="" ROTA="1" MAJ:MIN="253:16" SERIAL=""

maas machine get-curtin-config : https://pastebin.canonical.com/185301/

From the log output, it looks like it's not the same issue.

I think the issue is that the block device path reported by MAAS is not seen by Juju on the machine. From the logsink.log, I see:

647f1619-dab3-4347-8a9c-0418a009e664 machine-0: 2017-03-17 18:54:49 INFO juju.provisioner provisioner_task.go:758 started machine 32 as instance 4y3mp7 with hardware "arch=amd64 cores=32 mem=257859M tags=ceph-osd,gluster availability-zone=default", network config [{DeviceIndex:0 MACAddress:0c:c4:7a:8e:ee:1b CIDR: MTU:0 ProviderId:3936 ProviderSubnetId: ProviderSpaceId: ProviderAddressId: ProviderVLANId: VLANTag:0 InterfaceName:enp4s0f3 ParentInterfaceName:bond1 InterfaceType:ethernet Disabled:false NoAutoStart:false ConfigType: Address: DNSServers:[] DNSSearchDomains:[] GatewayAddress:} {DeviceIndex:1 MACAddress:0c:c4:7a:8e:ee:19 CIDR: MTU:0 ProviderId:3933 ProviderSubnetId: ProviderSpaceId: ProviderAddressId: ProviderVLANId: VLANTag:0 InterfaceName:enp4s0f1 ParentInterfaceName:bond0 InterfaceType:ethernet Disabled:false NoAutoStart:false ConfigType: Address: DNSServers:[] DNSSearchDomains:[] GatewayAddress:} {DeviceIndex:2 MACAddress:0c:c4:7a:8e:ee:1a CIDR: MTU:0 ProviderId:3935 ProviderSubnetId: ProviderSpaceId: ProviderAddressId: ProviderVLANId: VLANTag:0 InterfaceName:enp4s0f2 ParentInterfaceName:bond1 InterfaceType:ethernet Disabled:false NoAutoStart:false ConfigType: Address: DNSServers:[] DNSSearchDomains:[] GatewayAddress:} {DeviceIndex:3 MACAddress:0c:c4:7a:35:2d:3a CIDR:10.189.69.0/25 MTU:1500 ProviderId:3931 ProviderSubnetId:2 ProviderSpaceId:0 ProviderAddressId:23039 ProviderVLANId:5004 VLANTag:0 InterfaceName:enp5s0f0 ParentInterfaceName: InterfaceType:ethernet Disabled:false NoAutoStart:false ConfigType:static Address: DNSServers:[10.189.69.5] DNSSearchDomains:[] GatewayAddress:10.189.69.1} {DeviceIndex:4 MACAddress:0c:c4:7a:8e:ed:1c CIDR: MTU:0 ProviderId:3937 ProviderSubnetId: ProviderSpaceId: ProviderAddressId: ProviderVLANId: VLANTag:0 InterfaceName:enp133s0f0 ParentInterfaceName:bond0 InterfaceType:ethernet Disabled:false NoAutoStart:false ConfigType: Address: DNSServers:[] DNSSearchDomains:[] GatewayAddress:} {DeviceIndex:5 MACAddress:0c:c4:7a:8e:ed:1d CIDR: MTU:0 ProviderId:3938 ProviderSubnetId: ProviderSpaceId: ProviderAddressId: ProviderVLANId: VLANTag:0 InterfaceName:enp133s0f1 ParentInterfaceName:bond0 InterfaceType:ethernet Disabled:false NoAutoStart:false ConfigType: Address: DNSServers:[] DNSSearchDomains:[] GatewayAddress:} {DeviceIndex:6 MACAddress:0c:c4:7a:8e:ed:1e CIDR: MTU:0 ProviderId:3939 ProviderSubnetId: ProviderSpaceId: ProviderAddressId: ProviderVLANId: VLANTag:0 InterfaceName:enp133s0f2 ParentInterfaceName:bond1 InterfaceType:ethernet Disabled:false NoAutoStart:false ConfigType: Address: DNSServers:[] DNSSearchDomains:[] GatewayAddress:} {DeviceIndex:7 MACAddress:0c:c4:7a:8e:ed:1f CIDR: MTU:0 ProviderId:3940 ProviderSubnetId: ProviderSpaceId: ProviderAddressId: ProviderVLANId: VLANTag:0 InterfaceName:enp133s0f3 ParentInterfaceName:bond1 InterfaceType:ethernet Disabled:false NoAutoStart:false ConfigType: Address: DNSServers:[] DNSSearchDomains:[] GatewayAddress:} {DeviceIndex:8 MACAddress:0c:c4:7a:35:2d:3b CIDR: MTU:0 ProviderId:3934 ProviderSubnetId: ProviderSpaceId: Provid...

I can reproduce the issue on finfolk-vmaas.

https://github.com/juju/juju/pull/7247

I can stil reproduce this with MAAS 2.2rc3 and juju2.2b3.

Ante, I'll need to get access to your CPE lab environment again then. Please let me know when I can test there.

MAAS is reporting the WWN path, and we're expecting the vendor+model+serial. I'll have to add WWN to the list of block device properties we record.

https://github.com/juju/juju/pull/7303

I can confirm this is fixed in 2.2b4.