-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Server (and possibly others) do accidental substring match on name during adoption #250
Comments
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 11, 2025
Create one server named 'create-adoption'. Create another server with the substring of the first - 'adoption' Test that the resource name of the second server is 'adoption'. Reference: k-orc#250
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 11, 2025
Create one server named 'create-adoption'. Create another server with the substring of the first - 'adoption' Test that the resource name of the second server is 'adoption'. Reference: k-orc#250
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 11, 2025
In adoption use a regular expression to get a specific server instead of using the name as it is which can lead to getting servers that contain the server name in their names Example: We look for 'foo' where there is a server 'foobar' Also added a test for server adoption - Create one server named 'create-adoption'. - Create another server with the substring of the first - 'adoption' - Test that the resource name of the second server is 'adoption'. Fixes k-orc#250
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 11, 2025
In adoption use a regular expression to get a specific server instead of using the name as it is which can lead to getting servers that contain the server name in their names Example: We look for 'foo' where there is a server 'foobar' Also added a test for server adoption - Create one server named 'create-adoption'. - Create another server with the substring of the first - 'adoption' - Test that the resource name of the second server is 'adoption'. Fixes k-orc#250
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 13, 2025
In adoption use a regular expression to get a specific server instead of using the name as it is which can lead to getting servers that contain the server name in their names Example: We look for 'foo' where there is a server 'foobar' Also added a test for server adoption - Create one server named 'create-adoption'. - Create another server with the substring of the first - 'adoption' - Test that the resource name of the second server is 'adoption'. Done the same for import - same fix and added a test Fixes k-orc#250
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 13, 2025
In adoption use a regular expression to get a specific server instead of using the name as it is which can lead to getting servers that contain the server name in their names Example: We look for 'foo' where there is a server 'foobar' Also added a test for server adoption - Create one server named 'create-adoption'. - Create another server with the substring of the first - 'adoption' - Test that the resource name of the second server is 'adoption'. Done the same for import - same fix and added a test Fixes k-orc#250
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 13, 2025
In adoption use a regular expression to get a specific server instead of using the name as it is which can lead to getting servers that contain the server name in their names Example: We look for 'foo' where there is a server 'foobar' Also added a test for server adoption - Create one server named 'create-adoption'. - Create another server with the substring of the first - 'adoption' - Test that the resource name of the second server is 'adoption'. Done the same for import - same fix and added a test Fixes k-orc#250
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 16, 2025
In adoption use a regular expression to get a specific server instead of using the name as it is which can lead to getting servers that contain the server name in their names Example: We look for 'foo' where there is a server 'foobar' Also added a test for server adoption - Create one server named 'create-adoption'. - Create another server with the substring of the first - 'adoption' - Test that the resource name of the second server is 'adoption'. Done the same for import - same fix and added a test Fixes k-orc#250
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 16, 2025
In adoption use a regular expression to get a specific server instead of using the name as it is which can lead to getting servers that contain the server name in their names Example: We look for 'foo' where there is a server 'foobar' Also added a test for server adoption - Create one server named 'create-adoption'. - Create another server with the substring of the first - 'adoption' - Test that the resource name of the second server is 'adoption'. Done the same for import - same fix and added a test Fixes k-orc#250
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 16, 2025
In adoption use a regular expression to get a specific server instead of using the name as it is which can lead to getting servers that contain the server name in their names Example: We look for 'foo' where there is a server 'foobar' Also added a test for server adoption - Create one server named 'create-adoption'. - Create another server with the substring of the first - 'adoption' - Test that the resource name of the second server is 'adoption'. Done the same for import - same fix and added a test Fixes k-orc#250
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 16, 2025
In adoption use a regular expression to get a specific server instead of using the name as it is which can lead to getting servers that contain the server name in their names Example: We look for 'foo' where there is a server 'foobar' Also added a test for server adoption - Create one server named 'create-adoption'. - Create another server with the substring of the first - 'adoption' - Test that the resource name of the second server is 'adoption'. Done the same for import - same fix and added a test Fixes k-orc#250
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 16, 2025
In adoption use a regular expression to get a specific server instead of using the name as it is which can lead to getting servers that contain the server name in their names Example: We look for 'foo' where there is a server 'foobar' Also added a test for server adoption - Create one server named 'create-adoption'. - Create another server with the substring of the first - 'adoption' - Test that the resource name of the second server is 'adoption'. Done the same for import - same fix and added a test Fixes k-orc#250
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 16, 2025
In adoption use a regular expression to get a specific server instead of using the name as it is which can lead to getting servers that contain the server name in their names Example: We look for 'foo' where there is a server 'foobar' Also added a test for server adoption - Create one server named 'create-adoption'. - Create another server with the substring of the first - 'adoption' - Test that the resource name of the second server is 'adoption'. Done the same for import - same fix and added a test Fixes k-orc#250
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 17, 2025
In adoption use a regular expression to get a specific server instead of using the name as it is which can lead to getting servers that contain the server name in their names Example: We look for 'foo' where there is a server 'foobar' Also added a test for server adoption - Create one server named 'create-adoption'. - Create another server with the substring of the first - 'adoption' - Test that the resource name of the second server is 'adoption'. Done the same for import - same fix and added a test Fixes k-orc#250
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 20, 2025
In adoption use a regular expression to get a specific server instead of using the name as it is which can lead to getting servers that contain the server name in their names Example: We look for 'foo' where there is a server 'foobar' Also added a test for server adoption - Create one server named 'create-adoption'. - Create another server with the substring of the first - 'adoption' - Test that the resource name of the second server is 'adoption'. Done the same for import - same fix and added a test Fixes k-orc#250
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 20, 2025
In adoption use a regular expression to get a specific server instead of using the name as it is which can lead to getting servers that contain the server name in their names Example: We look for 'foo' where there is a server 'foobar' Also added a test for server adoption - Create one server named 'create-adoption'. - Create another server with the substring of the first - 'adoption' - Test that the resource name of the second server is 'adoption'. Done the same for import - same fix and added a test Fixes k-orc#250
itzikb-redhat
added a commit
to itzikb-redhat/openstack-resource-controller
that referenced
this issue
Feb 24, 2025
In adoption use a regular expression to get a specific server instead of using the name as it is which can lead to getting servers that contain the server name in their names Example: We look for 'foo' where there is a server 'foobar' Also added a test for server adoption - Create one server named 'create-adoption'. - Create another server with the substring of the first - 'adoption' - Test that the resource name of the second server is 'adoption'. Done the same for import - same fix and added a test Fixes k-orc#250
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I created a server called
bastion
and it imported an existing server calledfoo-bastion
. Server should obviously be doing more robust adoption than just a name match, but in any case we should be matching the whole string not just a substring.The text was updated successfully, but these errors were encountered: