Bug 1809521
Summary: | [Azure] Creating machineset with "publicIP: true" results in panic | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Alberto <agarcial> |
Component: | Cloud Compute | Assignee: | Alberto <agarcial> |
Cloud Compute sub component: | Other Providers | QA Contact: | Jianwei Hou <jhou> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | ademicev, agarcial, kgarriso, mimccune, zhsun |
Version: | 4.4 | ||
Target Milestone: | --- | ||
Target Release: | 4.4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1809001 | Environment: | |
Last Closed: | 2020-05-04 11:44:14 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1809001 | ||
Bug Blocks: |
Description
Alberto
2020-03-03 10:17:16 UTC
Marking manually as modified - the associated PR has merged. verified clusterversion: 4.4.0-0.nightly-2020-04-23-014745 machine could be created successful and join the cluster I0423 06:00:02.140549 1 actuator.go:163] Updating machine zhsun423azure-69h4j-worker-invalid-l4lrt I0423 06:00:02.624210 1 machine_scope.go:170] zhsun423azure-69h4j-worker-invalid-l4lrt: status unchanged I0423 06:00:02.624269 1 machine_scope.go:170] zhsun423azure-69h4j-worker-invalid-l4lrt: status unchanged I0423 06:00:02.624274 1 machine_scope.go:190] zhsun423azure-69h4j-worker-invalid-l4lrt: patching machine I0423 06:00:02.640458 1 controller.go:419] zhsun423azure-69h4j-worker-invalid-l4lrt: going into phase "Running" I0423 06:00:02.658052 1 controller.go:163] zhsun423azure-69h4j-worker-invalid-l4lrt: reconciling Machine I0423 06:00:02.658088 1 actuator.go:196] Checking if machine zhsun423azure-69h4j-worker-invalid-l4lrt exists I0423 06:00:02.994334 1 reconciler.go:352] Found vm for machine zhsun423azure-69h4j-worker-invalid-l4lrt I0423 06:00:02.994359 1 reconciler.go:372] Machine 626c52c2-1bf1-493d-811a-0d16eee6d2a4 is running I0423 06:00:02.994369 1 controller.go:271] zhsun423azure-69h4j-worker-invalid-l4lrt: reconciling machine triggers idempotent update I0423 06:00:02.994374 1 actuator.go:163] Updating machine zhsun423azure-69h4j-worker-invalid-l4lrt I0423 06:00:03.449448 1 machine_scope.go:170] zhsun423azure-69h4j-worker-invalid-l4lrt: status unchanged I0423 06:00:03.449551 1 machine_scope.go:170] zhsun423azure-69h4j-worker-invalid-l4lrt: status unchanged I0423 06:00:03.449559 1 machine_scope.go:190] zhsun423azure-69h4j-worker-invalid-l4lrt: patching machine I0423 06:00:31.142824 1 controller.go:163] zhsun423azure-69h4j-worker-invalid-l4lrt: reconciling Machine I0423 06:00:31.142850 1 actuator.go:196] Checking if machine zhsun423azure-69h4j-worker-invalid-l4lrt exists I0423 06:00:31.472096 1 reconciler.go:352] Found vm for machine zhsun423azure-69h4j-worker-invalid-l4lrt I0423 06:00:31.472138 1 reconciler.go:372] Machine 626c52c2-1bf1-493d-811a-0d16eee6d2a4 is running I0423 06:00:31.472150 1 controller.go:271] zhsun423azure-69h4j-worker-invalid-l4lrt: reconciling machine triggers idempotent update I0423 06:00:31.472173 1 actuator.go:163] Updating machine zhsun423azure-69h4j-worker-invalid-l4lrt I0423 06:00:32.068237 1 machine_scope.go:170] zhsun423azure-69h4j-worker-invalid-l4lrt: status unchanged I0423 06:00:32.068278 1 machine_scope.go:170] zhsun423azure-69h4j-worker-invalid-l4lrt: status unchanged I0423 06:00:32.068283 1 machine_scope.go:190] zhsun423azure-69h4j-worker-invalid-l4lrt: patching machine I0423 06:01:32.170835 1 controller.go:163] zhsun423azure-69h4j-worker-invalid-l4lrt: reconciling Machine I0423 06:01:32.170894 1 actuator.go:196] Checking if machine zhsun423azure-69h4j-worker-invalid-l4lrt exists I0423 06:01:32.693407 1 reconciler.go:352] Found vm for machine zhsun423azure-69h4j-worker-invalid-l4lrt I0423 06:01:32.693429 1 reconciler.go:372] Machine 626c52c2-1bf1-493d-811a-0d16eee6d2a4 is running I0423 06:01:32.693437 1 controller.go:271] zhsun423azure-69h4j-worker-invalid-l4lrt: reconciling machine triggers idempotent update I0423 06:01:32.693442 1 actuator.go:163] Updating machine zhsun423azure-69h4j-worker-invalid-l4lrt I0423 06:01:33.165315 1 machine_scope.go:170] zhsun423azure-69h4j-worker-invalid-l4lrt: status unchanged I0423 06:01:33.165385 1 machine_scope.go:170] zhsun423azure-69h4j-worker-invalid-l4lrt: status unchanged I0423 06:01:33.165392 1 machine_scope.go:190] zhsun423azure-69h4j-worker-invalid-l4lrt: patching machine Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0581 |