-
Notifications
You must be signed in to change notification settings - Fork 55
Open
Description
Which topic are you reporting about?
When following the instructions given at https://cloud.ibm.com/docs/vpc?topic=vpc-creating-vpc-resources-with-cli-and-api&interface=cli
one of the steps given to reserve a fip and attach it to a VSI is:
ibmcloud is floating-ip-reserve my-fip --nic $nic
Where nic is the obtained by a step above, which says:
save the ID of the primary network interface (Primary Interface) in a variable so you can use it later, for example:
nic="0738-4d9b3a58-f796-4e6a-b5ac-84f4216e9b68-glhvl"
When I run the fip reserve command I get the error:
FAILED
Error code: bad_field
Error message: The specified target is a network attachment which can not be attached to a floating ip directly.
Error target name: target.id, type: field
Error target value: 7392-058a60d7-3707-4909-8349-c256ebd8bfda
Trace ID: 62fa2a29-bae5-43a9-87ca-46cd020876dd
My primary network details:
primary_network_interface": {
"allow_ip_spoofing": false,
"created_at": "2025-11-08T05:20:57.000Z",
"floating_ips": [],
"href": "https://xxx/v1/instances/xxx/network_interfaces/7392-058a60d7-3707-4909-8349-c256ebd8bfda",
"id": "7392-058a60d7-3707-4909-8349-c256ebd8bfda",
"name": "ultra-aisle-goodness-trapdoor",
"port_speed": 3000,
"primary_ip": {
"address": "10.240.128.4",
"href": "https://xxx/v1/subnets/xxx/reserved_ips/7392-dc4e69e5-fab3-420f-93d7-ab55541cb7a1",
"id": "7392-dc4e69e5-fab3-420f-93d7-ab55541cb7a1",
"name": "watch-shadiness-precise-absolve",
"resource_type": "subnet_reserved_ip"
},
"resource_type": "network_interface",
"security_groups": [
{
"crn": "crn:v1:staging:public:is:us-south:a/xxx::security-group:r134-dbc3c74a-fad1-4d0e-bfaa-b92284da05c7",
"href": "https://xxx/v1/security_groups/r134-dbc3c74a-fad1-4d0e-bfaa-b92284da05c7",
"id": "r134-dbc3c74a-fad1-4d0e-bfaa-b92284da05c7",
"name": "trapdoor-moonstone-wind-cordovan"
}
],
"status": "available",
"subnet": {
"crn": "crn:v1:staging:public:is:us-south-3:a/xxx::subnet:7392-2bbcf6ed-8812-4aad-91ce-46d3522cf7e5",
"href": "https://xxx/v1/subnets/7392-2bbcf6ed-8812-4aad-91ce-46d3522cf7e5",
"id": "7392-2bbcf6ed-8812-4aad-91ce-46d3522cf7e5",
"name": "xxx",
"resource_type": "subnet"
},
"type": "primary"
},
What do you think needs to be updated?
The instruction to create the fip for a VSI is not working and needs to be corrected.
In addition, an example output should be given on how to extract the nic id to make it clear to the customers.
Anything else?
No response
Metadata
Metadata
Assignees
Labels
No labels