{"action":"opened","issue":{"url":"https://api.github.com/repos/openshift/origin/issues/13468","repository_url":"https://api.github.com/repos/openshift/origin","labels_url":"https://api.github.com/repos/openshift/origin/issues/13468/labels{/name}","comments_url":"https://api.github.com/repos/openshift/origin/issues/13468/comments","events_url":"https://api.github.com/repos/openshift/origin/issues/13468/events","html_url":"https://github.com/openshift/origin/issues/13468","id":215506958,"number":13468,"title":"Try It Out v2 Example fails","user":{"login":"chenrygithub","id":2184511,"avatar_url":"https://avatars3.githubusercontent.com/u/2184511?v=3","gravatar_id":"","url":"https://api.github.com/users/chenrygithub","html_url":"https://github.com/chenrygithub","followers_url":"https://api.github.com/users/chenrygithub/followers","following_url":"https://api.github.com/users/chenrygithub/following{/other_user}","gists_url":"https://api.github.com/users/chenrygithub/gists{/gist_id}","starred_url":"https://api.github.com/users/chenrygithub/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chenrygithub/subscriptions","organizations_url":"https://api.github.com/users/chenrygithub/orgs","repos_url":"https://api.github.com/users/chenrygithub/repos","events_url":"https://api.github.com/users/chenrygithub/events{/privacy}","received_events_url":"https://api.github.com/users/chenrygithub/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-03-20T18:04:01Z","updated_at":"2017-03-20T18:04:01Z","closed_at":null,"body":"I've just started with OpenShift and have started a cluster using the containerised method. I can log into the web gui remotely and all that seems working OK. \r\n\r\nI do the Try It Out example, oc login, oc new-project, oc oc new-app openshift/deployment-example and curl which all works fine. I go to the 'oc tag deployment-example:v2 deployment-example:latest' bit and get the following error:\r\n\r\n`oc tag deployment-example:v2 deployment-example:latest\r\nerror: \"deployment-example:v2\" is not currently pointing to an image, cannot use it as the source of a tag`\r\n\r\n##### Version\r\noc v1.5.0-alpha.3+87ca44f-314\r\nkubernetes v1.5.2+43a9be4\r\nfeatures: Basic-Auth GSSAPI Kerberos SPNEGO\r\n\r\nServer https://192.168.0.158:8443\r\nopenshift v1.5.0-alpha.3+87ca44f-314\r\nkubernetes v1.5.2+43a9be4\r\n\r\n\r\n##### Steps To Reproduce\r\n1. Run through 'Method 1: Running in a container'\r\n2. Go through 'Try It Out Steps 1 to 5\r\n3. Run 'oc tag deployment-example:v2 deployment-example:latest' as instructed.\r\n\r\n##### Current Result\r\nCommand returns:\r\n\r\n`oc tag deployment-example:v2 deployment-example:latest\r\nerror: \"deployment-example:v2\" is not currently pointing to an image, cannot use it as the source of a tag`\r\n\r\n##### Expected Result\r\nThe curl command should return a document with v2 in it instead of v1 from the previous example.\r\n\r\n##### Additional Information\r\n`# oadm diagnostics\r\n[Note] Determining if client configuration exists for client/cluster diagnostics\r\nInfo:  Successfully read a client config file at '/var/lib/origin/openshift.local.config/master/admin.kubeconfig'\r\nInfo:  Using context for cluster-admin access: 'default/192-168-0-158:8443/system:admin'\r\n\r\n[Note] Running diagnostic: ConfigContexts[default/192-168-0-158:8443/system:admin]\r\n       Description: Validate client config context is complete and has connectivity\r\n       \r\nInfo:  The current client config context is 'default/192-168-0-158:8443/system:admin':\r\n       The server URL is 'https://192.168.0.158:8443'\r\n       The user authentication is 'system:admin/192-168-0-158:8443'\r\n       The current project is 'default'\r\n       Successfully requested project list; has access to project(s):\r\n         [default kube-system openshift openshift-infra test]\r\n       \r\n[Note] Running diagnostic: DiagnosticPod\r\n       Description: Create a pod to run diagnostics from the application standpoint\r\n       \r\nERROR: [DCli2012 from diagnostic DiagnosticPod@openshift/origin/pkg/diagnostics/client/run_diagnostics_pod.go:155]\r\n       See the errors below in the output from the diagnostic pod:\r\n       [Note] Running diagnostic: PodCheckAuth\r\n              Description: Check that service account credentials authenticate as expected\r\n              \r\n       ERROR: [DP1003 from diagnostic PodCheckAuth@openshift/origin/pkg/diagnostics/pod/auth.go:88]\r\n              Could not authenticate to the master with the service account credentials: Get https://kubernetes.default.svc.cluster.local:443/oapi/v1/users/~: dial tcp: lookup kubernetes.default.svc.cluster.local: no such host\r\n              \r\n       ERROR: [DP1016 from diagnostic PodCheckAuth@openshift/origin/pkg/diagnostics/pod/auth.go:113]\r\n              DNS resolution for registry address docker-registry.default.svc.cluster.local returned an error; container DNS is likely incorrect. The error was: read udp 172.17.0.2:57007->192.168.0.158:53: read: no route to host\r\n              \r\n       [Note] Running diagnostic: PodCheckDns\r\n              Description: Check that DNS within a pod works as expected\r\n              \r\n       ERROR: [DP2003 from diagnostic PodCheckDns@openshift/origin/pkg/diagnostics/pod/dns.go:72]\r\n              The first /etc/resolv.conf nameserver 192.168.0.158\r\n              could not resolve kubernetes.default.svc.cluster.local.\r\n              Error: read udp 172.17.0.2:51461->192.168.0.158:53: read: no route to host\r\n              This nameserver points to the master's SkyDNS which is critical for\r\n              resolving cluster names, e.g. for Services.\r\n              \r\n       WARN:  [DP2014 from diagnostic PodCheckDns@openshift/origin/pkg/diagnostics/pod/dns.go:119]\r\n              A request to the nameserver 192.168.0.158 timed out.\r\n              This could be temporary but could also indicate network or DNS problems.\r\n              \r\n       WARN:  [DP2015 from diagnostic PodCheckDns@openshift/origin/pkg/diagnostics/pod/dns.go:124]\r\n              Error querying nameserver 192.168.0.158:\r\n                read udp 172.17.0.2:44169->192.168.0.158:53: read: no route to host\r\n              This may indicate a problem with DNS.\r\n              \r\n       [Note] Summary of diagnostics execution (version v1.5.0-alpha.3+cf7e336):\r\n       [Note] Warnings seen: 2\r\n       [Note] Errors seen: 3\r\n       \r\n```\r\n[Note] Running diagnostic: NetworkCheck\r\n       Description: Create a pod on all schedulable nodes and run network diagnostics from the application standpoint\r\n       \r\nWARN:  [DNet2002 from diagnostic NetworkCheck@openshift/origin/pkg/diagnostics/network/run_pod.go:81]\r\n       Skipping network diagnostics check. Reason: Not using openshift network plugin.\r\n       \r\n[Note] Skipping diagnostic: AggregatedLogging\r\n       Description: Check aggregated logging integration for proper configuration\r\n       Because: No master config file was provided\r\n       \r\n[Note] Running diagnostic: ClusterRegistry\r\n       Description: Check that there is a working Docker registry\r\n       \r\nWARN:  [DClu1002 from diagnostic ClusterRegistry@openshift/origin/pkg/diagnostics/cluster/registry.go:192]\r\n       There is no \"docker-registry\" service in project \"default\". This is not strictly required to\r\n       be present; however, it is required for builds, and its absence probably\r\n       indicates an incomplete installation.\r\n       \r\n       Please consult the documentation and use the 'oadm registry' command\r\n       to create a Docker registry.\r\n       \r\n[Note] Running diagnostic: ClusterRoleBindings\r\n       Description: Check that the default ClusterRoleBindings are present and contain the expected subjects\r\n       \r\n[Note] Running diagnostic: ClusterRoles\r\n       Description: Check that the default ClusterRoles are present and contain the expected permissions\r\n       \r\n[Note] Running diagnostic: ClusterRouterName\r\n       Description: Check there is a working router\r\n       \r\nWARN:  [DClu2001 from diagnostic ClusterRouter@openshift/origin/pkg/diagnostics/cluster/router.go:129]\r\n       There is no \"router\" DeploymentConfig. The router may have been named\r\n       something different, in which case this warning may be ignored.\r\n       \r\n       A router is not strictly required; however it is needed for accessing\r\n       pods from external networks and its absence likely indicates an incomplete\r\n       installation of the cluster.\r\n       \r\n       Use the 'oadm router' command to create a router.\r\n       \r\n[Note] Running diagnostic: MasterNode\r\n       Description: Check if master is also running node (for Open vSwitch)\r\n       \r\nInfo:  Found a node with same IP as master: origin.colinhenry.co.uk\r\n\r\n[Note] Skipping diagnostic: MetricsApiProxy\r\n       Description: Check the integrated heapster metrics can be reached via the API proxy\r\n       Because: The heapster service does not exist in the openshift-infra project at this time,\r\n       so it is not available for the Horizontal Pod Autoscaler to use as a source of metrics.\r\n       \r\n[Note] Running diagnostic: NodeDefinitions\r\n       Description: Check node records on master\r\n       \r\n[Note] Skipping diagnostic: ServiceExternalIPs\r\n       Description: Check for existing services with ExternalIPs that are disallowed by master config\r\n       Because: No master config file was detected\r\n       \r\n[Note] Summary of diagnostics execution (version v1.5.0-alpha.3+87ca44f-314):\r\n[Note] Warnings seen: 3\r\n[Note] Errors seen: 1\r\n```\r\n\r\n"}}
{"actor":{"display_login":"chenrygithub"}}