[Solved] Install on OCI and received 404 BucketNotFound

[NanoCode012]

Hello, I would like to thank you for this project. It is well documented and very simple to follow.

I followed the instructions and when I ran terraform apply -var-file="oci.tfvars", it works till it hits a 404 BucketNotFound error.

I ran the code twice (first time apply, then delete, then re-run apply), and the error occurs at the same location. The VM can be seen created (and ssh-able) and the Bucket does exist in the Oracle cloud but empty.

When I hit this error, I tried to run terraform apply -var-file="oci.tfvars" and it does run successfully, but nothing seems to be installed inside the VM and the Bucket does not consist of any configs.

Logs:

oci_kms_key.ph-kms-storage-key: Still creating... [40s elapsed]
oci_kms_key.ph-kms-storage-key: Still creating... [50s elapsed]
oci_kms_key.ph-kms-storage-key: Still creating... [1m0s elapsed]
oci_kms_key.ph-kms-storage-key: Still creating... [1m10s elapsed]
oci_kms_key.ph-kms-storage-key: Creation complete after 1m18s [id=redacted]
oci_kms_encrypted_data.ph-kms-ph-secret: Creating...
oci_objectstorage_bucket.ph-bucket: Creating...
oci_kms_encrypted_data.ph-kms-ph-secret: Creation complete after 1s [id=redacted]
data.template_file.ph-user-data: Reading...
data.template_file.ph-user-data: Read complete after 0s [id=redacted]
oci_core_instance.ph-instance: Creating...
oci_objectstorage_bucket.ph-bucket: Creation complete after 1s [id=n/redacted/b/cloudblock-bucket]
oci_core_instance.ph-instance: Still creating... [10s elapsed]
oci_core_instance.ph-instance: Still creating... [20s elapsed]
oci_core_instance.ph-instance: Still creating... [30s elapsed]
oci_core_instance.ph-instance: Still creating... [40s elapsed]
oci_core_instance.ph-instance: Creation complete after 49s [id=redacted]
╷
│ Error: 404-BucketNotFound
│ Provider version: 4.62.0, released on 2022-02-03.
│ Service: Object Storage Lifecycle Policy
│ Error Message: Either the bucket named 'cloudblock-bucket' does not exist in the namespace 'redacted' or you are not authorized to access it
│ OPC request ID: redacted
│ Suggestion: Either the resource has been deleted or service Object Storage Lifecycle Policy need policy to access this resource. Policy reference: https://docs.oracle.com/en-us/iaas/Content/Identity/Reference/policyreference.htm
│
│
│   with oci_objectstorage_object_lifecycle_policy.ph-bucket-lifecycle,
│   on oci-storage.tf line 15, in resource "oci_objectstorage_object_lifecycle_policy" "ph-bucket-lifecycle":
│   15: resource "oci_objectstorage_object_lifecycle_policy" "ph-bucket-lifecycle" 

[NanoCode012]

Update: After Ansible ran, I think the configurations were successfully created and I can connect via Wireguard and see the pi.hole information via the IP. But this bug remains during the running process.

[chadgeary]

Fixed via a7bca01 with a lifecycle dependency on the bucket - thanks! The lifecycle policy helps clean up old backups of cloudblock after 30 days to prevent reaching the free limit.

I suggest pulling this fix and re-running terraform. You may need to move your tfvars file out of the way to pull, e.g.:

cd cloudblock/oci
mv oci.tfvars pvars.tfvars
git pull
mv pvars.tfvars oci.tfvars
terraform apply -var-file="oci.tfvars"

[NanoCode012]

Hello @chadgeary ! Thank you very much for the quick response. May I ask if I would need to destroy the previous VM?

The logs from running the provided code on a currently running and working VM. Please do tell me if this is the expected output?

random_string.ph-random: Refreshing state... [id=2mses]
oci_identity_compartment.ph-compartment: Refreshing state... [id=redacted]
oci_core_vcn.ph-vcn: Refreshing state... [id=redacted]
oci_kms_vault.ph-kms-disk-vault: Refreshing state... [id=redacted]
oci_identity_dynamic_group.ph-id-dynamic-group: Refreshing state... [id=redacted]
oci_kms_vault.ph-kms-storage-vault: Refreshing state... [id=redacted]
oci_core_network_security_group.ph-network-security-group: Refreshing state... [id=redacted]
oci_core_internet_gateway.ph-internet-gateway: Refreshing state... [id=redacted]
oci_core_subnet.ph-subnet: Refreshing state... [id=redacted]
oci_core_default_security_list.ph-security-list-directdns[0]: Refreshing state... [id=redacted]
oci_core_default_route_table.ph-route-table: Refreshing state... [id=redacted]
oci_core_route_table_attachment.ph-route-table-attach: Refreshing state... [id=redacted]
oci_identity_policy.ph-id-storageobject-policy: Refreshing state... [id=redacted]
oci_identity_policy.ph-id-storage-policy: Refreshing state... [id=redacted]
oci_kms_key.ph-kms-storage-key: Refreshing state... [id=redacted]
oci_identity_policy.ph-id-disk-policy: Refreshing state... [id=redacted]
oci_kms_key.ph-kms-disk-key: Refreshing state... [id=redacted]
oci_kms_encrypted_data.ph-kms-ph-secret: Refreshing state... [id=redacted]
oci_objectstorage_bucket.ph-bucket: Refreshing state... [id=n/redacted/b/cloudblock-bucket]
oci_core_instance.ph-instance: Refreshing state... [id=redacted]
oci_objectstorage_object_lifecycle_policy.ph-bucket-lifecycle: Refreshing state... [id=n/redacted/b/cloudblock-bucket/l]

Terraform detected the following changes made outside of Terraform since the last "terraform apply":

  # oci_objectstorage_bucket.ph-bucket has changed
  ~ resource "oci_objectstorage_bucket" "ph-bucket" {
      ~ approximate_count            = "0" -> "redacted"
      ~ approximate_size             = "0" -> "redacted"
      ~ etag                         = "redacted" -> "redacted"
        id                           = "n/redacted/b/cloudblock-bucket"
        name                         = "cloudblock-bucket"
      + object_lifecycle_policy_etag = "redacted"
        # (16 unchanged attributes hidden)
    }


Unless you have made equivalent changes to your configuration, or ignored the relevant attributes using ignore_changes, the following plan may include actions to undo or respond to these
changes.

────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

No changes. Your infrastructure matches the configuration.

Your configuration already matches the changes detected above. If you'd like to update the Terraform state to match, create and apply a refresh-only plan:
  terraform apply -refresh-only

Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

[chadgeary]

Destroy is not needed, that looks fine. No changes were needed because (likely) you ran terraform apply previously more than once (before the fix) and that lifecycle was successfully created. All good! The original error was because the lifecycle attempted to be created before the bucket.

[NanoCode012]

Thank you very much! I am very interested in Terraform and Ansible now after hearing about it for a while. This is the first time I am able to do something hands on, so thanks for introducing me as well :)