Deployment failed to report final status (GHES) about deploy-pages HOT 9 CLOSED

The issue concerns the GitHub enterprise appliance and nothing with this deploy-pages action, they are working on the fix and will soon patch with the release.
keep an eye on https://enterprise.github.com/releases/ for the next release

from deploy-pages.

Can you confirm GitHub Pages is enabled for the repository?

from deploy-pages.

@yoannchaudet thanks for your reply.
yes github pages is enabled for the repository and i have noticed the action fails in the following method

async function getPagesDeploymentStatus({ githubToken, deploymentId }) {
  const octokit = github.getOctokit(githubToken)
  core.info('Getting Pages deployment status...')
  try {
    const response = await octokit.request('GET /repos/{owner}/{repo}/pages/deployment/status/{deploymentId}', {
      owner: github.context.repo.owner,
      repo: github.context.repo.repo,
      deploymentId
    })

    return response.data
  } catch (error) {
    core.error('Getting Pages deployment status failed', error)
    throw error
  }
}

I assume the rest endpoint being called here is incorrect. See the docs for GHES v3.8 GitHub Pages deployment

from deploy-pages.

Also seeing this for GHES 3.8

from deploy-pages.

I have tried using postman to call the following endpoint
/repos/{owner}/{repo}/pages/deployment/status/{deploymentId}
and i get the following response.

  {
      "status": "deployment_lost"
  }

The deployment creation works fine but somehow the pipeline fails to fetch the deployment status

from deploy-pages.

I have the same issue with GitHub Enterprise Server 3.7.8
how could this be solved? Any suggestion?

from deploy-pages.

I wonder if this is related to #168 as we have this error with the v1 and the error mentioned in #168 with v2.
Github pages is enabled. We used v1 up until this point, but it started failing around the 23rd of March for us.

from deploy-pages.

The fix is released https://docs.github.com/en/[email protected]/admin/release-notes

from deploy-pages.

That's correct, GHES release 3.8.3 contains a bug fix for the deployment_lost scenario (which was an issue from beyond this action's boundaries).

from deploy-pages.