-
Notifications
You must be signed in to change notification settings - Fork 129
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
Unable to add route rules if the targets(All Gateways) are in different compartment using OKIT #452
Comments
@KirankBadiger was the compartment containing the gateway in the query results. Just tried this and can't reproduce if the compartment with the gateway is in the results. If it's not in the result then I get the same empty display but that's not surprising. |
@toxophilist gateways are deployed in different compartment, subnets are in different compartments, checked in OCI console, there I can add route rules if the gateways are in different compartment, but with OKIT it is not possible, OKIT should show the existing route rules right with "query" feature?, but it is doesn't |
@KirankBadiger OKIT knows about what is in the design so if all compartments are in the design then is should show the rules correctly. If the compartment is missing from the design then it will not be present for OKIT to display. |
@toxophilist All Compartments are present in OKIT, but route rules are not getting displayed |
@KirankBadiger just spotted your route table is read only which will stop you adding / modifying data |
@toxophilist Yes I know it is existing read-only route table, used "Query" feature, but it should show the existing route rules right? |
@KirankBadiger If the Network end point is in the design it should be displayed. Can you check the json view and validate the ocid in the rule looks fine. Just trying to work out where the issue is. |
Unable to add the route rules if the targets(All Gateways) are in different compartment using OKIT
Tried to view the existing infrastructure that are deployed in nested compartments even though unable view the route rules
For your reference attached the image below, used OKIT "query" feature to view the existing infrastructure deployed in nested compartments, still unable to view the existing route rules in OKIT
The text was updated successfully, but these errors were encountered: