Skip to content
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

Bug 1882490: data/azure/master: Add dash to nic name #5082

Merged
merged 1 commit into from Jul 28, 2021

Conversation

mtnbikenc
Copy link
Member

Fix code consistency issue of missing dash in nic name.

> $ git grep '${var.cluster_id}-master-${count.index}' | wc -l
21

> $ git grep '${var.cluster_id}-master${count.index}' | wc -l 
1

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 14, 2021

@mtnbikenc: This pull request references Bugzilla bug 1882490, which is invalid:

  • expected the bug to target the "4.9.0" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1882490: data/azure/master: Add dash to nic name

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot added bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Jul 14, 2021
@mtnbikenc
Copy link
Member Author

/bugzilla refresh

@openshift-ci openshift-ci bot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Jul 14, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 14, 2021

@mtnbikenc: This pull request references Bugzilla bug 1882490, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.9.0) matches configured target release for branch (4.9.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (tsze@redhat.com), skipping review request.

In response to this:

/bugzilla refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Jul 14, 2021
@rna-afk
Copy link
Contributor

rna-afk commented Jul 14, 2021

/test e2e-azure

@jhixson74
Copy link
Member

/approve
/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 15, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jhixson74

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jul 15, 2021
@mjudeikis
Copy link
Contributor

Appreciate the change but before we go this path I want to understand how this is aligned with other teams involved:

  1. What is the plan to align existing clusters to this change?
  2. How do we track which cluster "architecture" it is in the cluster itself? ARO has a metadata internally but this now makes it 3rd iteration of "Infrastructure changes".
  3. How this will play in the long run when you have 2 types of NICs out there and you need to manage loadbalancers memberships? How this is aligned to MachineAPI as they potentially now will have to deal with 3 Azure architectures in the wild:
    3.1 Single and multiple NGS (change done long ago)
    3.2 Nic names prior this PR
    3.3 Nic names after this PR

Basically blind changes like this creates much more complex work for downstream components and it would be good to align this in some way.

cc @JoelSpeed

@mtnbikenc
Copy link
Member Author

I will bring this up with the team.
/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 15, 2021
@sdodson
Copy link
Member

sdodson commented Jul 16, 2021

@mjudeikis What specifically would you like for the Installer to do with your bug then? Your concern is that we're not coordinating with the cloud infra team to ensure that these remain stable from this point forward? The installer has zero post install responsibilities so I don't think there's any room for the Installer to alter existing clusters, you could certainly roll through each cluster and replace masters until everything converges and you'd never have to know the existing nic naming scheme in order to do that.

@sdodson
Copy link
Member

sdodson commented Jul 16, 2021

/lgtm cancel
/approve cancel
Clearing these so someone doesn't inadvertently let this merge by clearing the hold only.

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 16, 2021
@JoelSpeed
Copy link
Contributor

AFAIK this should be safe with respect to MAPI. We only care about the NicName during VM creation, in which case we generate it with https://github.com/openshift/cluster-api-provider-azure/blob/master/pkg/cloud/azure/defaults.go#L128-L130.

When we are updating or deleting VMs, we look up the NIC that is attached to the VM, we don't guess its name based on a pattern or anything.

LGTM from me on this front at least

@mjudeikis
Copy link
Contributor

@sdodson My general worry is just about the fact that installer does not have any responsibilities day 2. We already seen multiple cases where now we have 4-5 different flavors of clusters out in the wild, and this would be adding one more.

In general this is a problem which is being pushed down the queue to the last standing person in the line. In most cases its CEE, customer or SRE's.
At some point we need to stop doing this and start tracking changes in some architecture version per components so at any point in time any component interacting with other component would know which version of resource it need to talk to and how to interact with.

@sdodson
Copy link
Member

sdodson commented Jul 22, 2021

@mjudeikis I think that's a worthwhile gap to identify but I don't think it will be addressed within the scope of a bug or a PR, or even by the Installre team. So need a decision on whether we close this PR and the BZ or we merge this and fix the bug. That decision shouldn't be influenced by whether or not we decide to start tracking and remediating architectural drift.

@mjudeikis
Copy link
Contributor

@sdodson I say merge, but all this is creating quite a tech dept for teams outside AOS... just saying...

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 23, 2021
@mtnbikenc
Copy link
Member Author

@sdodson @mjudeikis , Where do we stand on this PR? I'm happy to move forward or close this and the bug as WONTFIX. I'll rebase this in the meantime.

Fix code consistency issue of missing dash in nic name.
@openshift-ci openshift-ci bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 27, 2021
@sdodson
Copy link
Member

sdodson commented Jul 27, 2021

We'll move forward with the change.
/lgtm
/hold cancel

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Jul 27, 2021
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@sdodson
Copy link
Member

sdodson commented Jul 27, 2021

/test e2e-azure

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@sdodson
Copy link
Member

sdodson commented Jul 27, 2021

/test e2e-azure

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

4 similar comments
@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 27, 2021

@mtnbikenc: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws-fips 9268ffe link /test e2e-aws-fips
ci/prow/e2e-crc 9268ffe link /test e2e-crc
ci/prow/e2e-libvirt 9268ffe link /test e2e-libvirt
ci/prow/e2e-openstack-kuryr 9268ffe link /test e2e-openstack-kuryr
ci/prow/e2e-aws-workers-rhel7 9268ffe link /test e2e-aws-workers-rhel7
ci/prow/e2e-aws-single-node 9268ffe link /test e2e-aws-single-node

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-bot
Copy link
Contributor

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@sdodson
Copy link
Member

sdodson commented Jul 28, 2021

/override ci/prow/e2e-aws-upgrade
This only affects azure

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 28, 2021

@sdodson: Overrode contexts on behalf of sdodson: ci/prow/e2e-aws-upgrade

In response to this:

/override ci/prow/e2e-aws-upgrade
This only affects azure

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-merge-robot openshift-merge-robot merged commit a33697d into openshift:master Jul 28, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 28, 2021

@mtnbikenc: All pull requests linked via external trackers have merged:

Bugzilla bug 1882490 has been moved to the MODIFIED state.

In response to this:

Bug 1882490: data/azure/master: Add dash to nic name

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@mtnbikenc mtnbikenc deleted the fix-1882490 branch July 28, 2021 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants