Bug 1827378
| Summary: | Unable to load graphs in disconnected upgrade | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jaspreet Kaur <jkaur> |
| Component: | Documentation | Assignee: | Latha S <lmurthy> |
| Status: | CLOSED WONTFIX | QA Contact: | liujia <jiajliu> |
| Severity: | medium | Docs Contact: | Latha S <lmurthy> |
| Priority: | medium | ||
| Version: | 4.3.z | CC: | aos-bugs, eparis, jiajliu, lmohanty, lmurthy, scuppett, wking, yanyang |
| Target Milestone: | --- | Keywords: | UpcomingSprint, Upgrades |
| Target Release: | 4.5.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-22 13:04:34 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Setting target release to current development version (4.5) for investigation. Where fixes (if any) are required/requested for prior versions, cloned BZs will be created when appropriate. So sadly, it seems that the CVO has been falling back to a default URI when the ClusterVersion upstream is empty since way back [1,2], and that this behavior is enshrined in the API [3]. I guess try clearing the channel. Although the channel docs also talk about defaults [4] and the only channel defaulting in the CVO is when creating a ClusterVersion object after the in-cluster copy was (accidentally?) deleted [4]. So maybe we could talk folks into adjusting the CVO logic to return NoUpstream in the empty-upstream case... Will see what the API folks think... [1]: https://github.com/openshift/cluster-version-operator/blame/2c4931dc283c551938be1a00fee290de0b79d99c/pkg/cvo/availableupdates.go#L27-L31 [2]: https://github.com/openshift/cluster-version-operator/commit/ab4d84a021c38fea5e5973287e1f5580928907c1#diff-78f2af341fa49292dd6930f378018867R24 [3]: https://github.com/openshift/api/blame/0422dc17083e9e8df18d029f3f34322e96e9c326/config/v1/types_cluster_version.go#L56-L57 [4]: https://github.com/openshift/api/blame/0422dc17083e9e8df18d029f3f34322e96e9c326/config/v1/types_cluster_version.go#L62-L63 This issue does not reduce the cluster functionality or availability. Can you confirm? Also as Trevor mentioned this is as per design. The upstream can not stay empty with the current design. Also the message is an info log. From the code "pkg/cvo/availableupdates.go: klog.V(2).Infof("Upstream server %s could not return available updates: %v", upstream, err)"
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |
Description of problem: when doing disconnected upgrade it fails to load cincinnati graph. we tried : fter checking on this with Engineering. Can you run below command and check : oc patch clusterversion version --type json -p '[{"op": "remove", "path": "/spec/upstream"}]' But it doesnt help : I0423 16:06:08.755260 1 cvo.go:371] Finished syncing cluster version "openshift-cluster-version/version" (185.748µs) I0423 16:06:08.770516 1 availableupdates.go:155] Upstream server https://api.openshift.com/api/upgrades_info/v1/graph could not return available updates: Get https://api.openshift.com/api/upgrades_info/v1/graph?arch=amd64&channel=stable-4.2&id=ac2cf2a4-ec7b-4115-a266-08c09ca4219d&version=4.2.16: dial tcp: lookup api.openshift.com on 10.2.88.196:53: no such host Version-Release number of the following components: openshift 4.2.4 to 4.2.16 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Unable to upgrade Expected results: should be able to upgrade Additional info: Please attach logs from ansible-playbook with the -vvv flag