Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #947

/assign candita

/cherrypick release-4.12

Set spec.template.spec.containers[*].ports[*].hostPort on a router
deployment if the deployment sets spec.template.spec.hostNetwork to true.

Before this commit, the operator left the hostPort field unspecified. As a
result, the API set a default value for hostPort.  The operator detected
this as an external update and attempted to revert it.  This commit
prevents the operator from making these spurious updates in response to API
defaulting.

This commit fixes OCPBUGS-14995.

https://issues.redhat.com/browse/OCPBUGS-14995

* pkg/operator/controller/ingress/deployment.go (desiredRouterDeployment):
Set each container port's HostPort to the port's ContainerPort value when
HostNetwork is enabled for the deployment.
* pkg/operator/controller/ingress/deployment_test.go (checkContainerPort):
Verify that HostPort is set to ContainerPort if HostNetwork is enabled.
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-14995 has been cloned as Jira Issue OCPBUGS-34409. Will retitle bug to link to clone.
/retitle [release-4.13] OCPBUGS-34409: desiredRouterDeployment: Set HostPort if needed

Details

In response to this:

This is an automated cherry-pick of #947

/assign candita

/cherrypick release-4.12

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot changed the title [release-4.13] OCPBUGS-14995: desiredRouterDeployment: Set HostPort if needed [release-4.13] OCPBUGS-34409: desiredRouterDeployment: Set HostPort if needed May 23, 2024
@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 23, 2024
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-34409, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required"

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

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #947

/assign candita

/cherrypick release-4.12

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from Miciah and frobware May 23, 2024 21:55
@candita
Copy link
Contributor

candita commented May 24, 2024

Exotic e2e-gcp-ovn failures:

level=error msg=StaticPodsDegraded: E0523 22:28:03.723788 1 reflector.go:140] k8s.io/[email protected]/tools/cache/reflector.go:169: Failed to watch *v1.Secret: failed to list *v1.Secret: Get "https://localhost:6443/api/v1/namespaces/openshift-kube-controller-manager/secrets?limit=500&resourceVersion=0": x509: certificate signed by unknown authority
level=error msg=StaticPodsDegraded:
level=error msg=StaticPodsDegraded: pod/kube-controller-manager-ci-op-r30d7ml7-cae21-cx6kb-master-0 container "kube-controller-manager-recovery-controller" is terminated: Completed:

/test e2e-gcp-ovn

e2e-aws-operator is blocked by #1037 backport #1061.

@lihongan
Copy link
Contributor

/jira refresh
/retest

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 27, 2024
@openshift-ci-robot
Copy link
Contributor

@lihongan: This pull request references Jira Issue OCPBUGS-34409, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.13.z) matches configured target version for branch (4.13.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-14995 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-14995 targets the "4.14.0" version, which is one of the valid target versions: 4.14.0, 4.14.z
  • bug has dependents

Requesting review from QA contact:
/cc @ShudiLi

Details

In response to this:

/jira refresh
/retest

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from ShudiLi May 27, 2024 02:58
@ShudiLi
Copy link
Member

ShudiLi commented May 27, 2024

/retest-required

@ShudiLi
Copy link
Member

ShudiLi commented May 27, 2024

/label qe-approved

tested it with 4.13.0-0.ci.test-2024-05-27-090305-ci-ln-v60hbzb-latest

1.
% oc get clusterversion
NAME      VERSION                                                   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.13.0-0.ci.test-2024-05-27-090305-ci-ln-v60hbzb-latest   True        False         56m     Cluster version is 4.13.0-0.ci.test-2024-05-27-090305-ci-ln-v60hbzb-latest

2. created two HostNetwork type ingress-controller
3.
% oc -n openshift-ingress-operator get ingresscontroller  cus1 -oyaml | grep -A13 spec:
spec:
  clientTLS:
    clientCA:
      name: ""
    clientCertificatePolicy: ""
  domain: cus1.ci-ln-v60hbzb-c1627.vmc-ci.devcluster.openshift.com
  endpointPublishingStrategy:
    type: HostNetwork
  httpCompression: {}
  httpEmptyRequestsPolicy: Respond
  httpErrorCodePages:
    name: ""
  tuningOptions:
    reloadInterval: 0s

4.
% oc -n openshift-ingress get deployment router-cus2 -oyaml | grep -i Port
        - name: ROUTER_SERVICE_HTTPS_PORT
        - name: ROUTER_SERVICE_HTTP_PORT
        - name: STATS_PORT
            port: 11939
        ports:
        - containerPort: 1080
          hostPort: 1080
        - containerPort: 10443
          hostPort: 10443
        - containerPort: 11939
          hostPort: 11939
            port: 11939
            port: 11939

5.
% oc -n openshift-ingress-operator logs -c ingress-operator deployments/ingress-operator | grep "updated router deployment"
%

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label May 27, 2024
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-34409, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.13.z) matches configured target version for branch (4.13.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-14995 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-14995 targets the "4.14.0" version, which is one of the valid target versions: 4.14.0, 4.14.z
  • bug has dependents

Requesting review from QA contact:
/cc @ShudiLi

Details

In response to this:

This is an automated cherry-pick of #947

/assign candita

/cherrypick release-4.12

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 openshift-eng/jira-lifecycle-plugin repository.

@ShudiLi
Copy link
Member

ShudiLi commented May 27, 2024

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label May 27, 2024
@ShudiLi
Copy link
Member

ShudiLi commented May 28, 2024

/retest

@candita
Copy link
Contributor

candita commented May 29, 2024

/assign @alebedev87

@candita
Copy link
Contributor

candita commented May 29, 2024

e2e tests should pass now that #1065 has merged.

/test e2e-aws-operator

@candita
Copy link
Contributor

candita commented May 30, 2024

Test failure in TestManagedDNSToUnmanagedDNSIngressController doesn't seem related to this change:

=== CONT TestAll/parallel/TestManagedDNSToUnmanagedDNSIngressController
unmanaged_dns_test.go:148: Updating ingresscontroller managed-migrated to dnsManagementPolicy=Unmanaged
unmanaged_dns_test.go:161: Waiting for stable conditions on ingresscontroller managed-migrated after dnsManagementPolicy=Unmanaged
...
=== CONT TestAll/parallel/TestManagedDNSToUnmanagedDNSIngressController
unmanaged_dns_test.go:177: verifying conditions on DNSRecord zone {ID: Tags:map[Name:ci-op-fb5dbsdx-08f48-t5zpz-int kubernetes.io/cluster/ci-op-fb5dbsdx-08f48-t5zpz:owned]}
unmanaged_dns_test.go:177: DNSRecord zone expected to have status=Unknown but got status=True

/test e2e-aws-operator

@knobunc knobunc added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label May 31, 2024
@knobunc
Copy link

knobunc commented May 31, 2024

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 31, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: knobunc

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

The pull request process is described here

Details 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 the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 31, 2024
@rfredette
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 31, 2024
@candita
Copy link
Contributor

candita commented May 31, 2024

Investigating repeated issue in E2E for TestManagedDNSToUnmanagedDNSIngressController:

=== CONT TestAll/parallel/TestManagedDNSToUnmanagedDNSIngressController
util_test.go:520: verified connectivity with workload with req http://af8e49e53a09d421c9e1454b28523513-1221592295.us-west-2.elb.amazonaws.com and response 200
...
=== CONT TestAll/parallel/TestManagedDNSToUnmanagedDNSIngressController
unmanaged_dns_test.go:148: Updating ingresscontroller managed-migrated to dnsManagementPolicy=Unmanaged
unmanaged_dns_test.go:161: Waiting for stable conditions on ingresscontroller managed-migrated after dnsManagementPolicy=Unmanaged
unmanaged_dns_test.go:177: verifying conditions on DNSRecord zone {ID: Tags:map[Name:ci-op-2g4fb3bw-08f48-5w9cz-int kubernetes.io/cluster/ci-op-2g4fb3bw-08f48-5w9cz:owned]}
unmanaged_dns_test.go:177: DNSRecord zone expected to have status=Unknown but got status=True

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD df0e401 and 2 for PR HEAD c97150e in total

@candita
Copy link
Contributor

candita commented May 31, 2024

Need 2 others to merge first.
/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 May 31, 2024
@candita
Copy link
Contributor

candita commented May 31, 2024

/cancel hold

@candita
Copy link
Contributor

candita commented May 31, 2024

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 31, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 1, 2024

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot bot merged commit 82aefc4 into openshift:release-4.13 Jun 1, 2024
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-34409: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-34409 has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #947

/assign candita

/cherrypick release-4.12

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-ingress-operator-container-v4.13.0-202406010109.p0.g82aefc4.assembly.stream.el8 for distgit ose-cluster-ingress-operator.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.13.0-0.nightly-2024-06-01-031656

@candita
Copy link
Contributor

candita commented Jun 4, 2024

/cherry-pick release-4.12

@openshift-cherrypick-robot
Copy link
Author

@candita: new pull request created: #1076

Details

In response to this:

/cherry-pick release-4.12

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-sigs/prow repository.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.